Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE]: Make redis key space domain customizable #220

Open
maggmanu77 opened this issue Jul 23, 2024 · 1 comment
Open

[FEATURE]: Make redis key space domain customizable #220

maggmanu77 opened this issue Jul 23, 2024 · 1 comment

Comments

@maggmanu77
Copy link

Please read our contributor guide before creating an issue.
Also consider discussing your idea on the discussion forum first.

Describe the Feature Request

Make redis key space domain customizable, there by allowing multi-tenant software to namespace | isolate their data in the same redis db. This primarily applies to the hash bucket keys.

Describe Preferred Solution

In com.netflix.conductor.redis.dao.BaseDynoDAO instead of the domain being a member variable, access from the property instance on demand. A derived bean instance of ConductorProperties (already a member of BaseDynoDAO) will be able to access the customized domain seamlessly.

Describe Alternatives

Considered other fields like stack, however key space domain is the most meaningful customization for tenant isolated hash buckets

@v1r3n
Copy link
Collaborator

v1r3n commented Jul 28, 2024

#221

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants