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

Modify elasticsearch indices to support multi-tenancy #373

Closed
ansalamdaniel opened this issue Apr 5, 2022 · 0 comments · Fixed by #378
Closed

Modify elasticsearch indices to support multi-tenancy #373

ansalamdaniel opened this issue Apr 5, 2022 · 0 comments · Fixed by #378
Assignees
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned

Comments

@ansalamdaniel
Copy link
Contributor

ansalamdaniel commented Apr 5, 2022

To standalone & multi-tenant based deployments, we need to modify the way other services interacts with elasticsearch.

Approach:

  • Create elasticsearch indices for each customers based on some parameters.
  • If the parameters are not available, then we can assume that it is a standalone deployment and create indices appropriately.

TBU

@ansalamdaniel ansalamdaniel added enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned labels Apr 5, 2022
@ansalamdaniel ansalamdaniel self-assigned this Apr 5, 2022
@shahpratikr shahpratikr changed the title Modify elasticsearch indices to support SaaS platform Modify elasticsearch indices to support multi-tenancy Apr 6, 2022
ramanan-ravi added a commit that referenced this issue Apr 6, 2022
ramanan-ravi added a commit that referenced this issue Apr 19, 2022
Cache topology data in redis #373
ramanan-ravi added a commit that referenced this issue Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant