feat(core): support for per dataset cassandra keyspace overrides #1653
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amolnayak311
approved these changes
Sep 11, 2023
yu-shipit
approved these changes
Apr 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request checklist
As of now there is a stipulation that all the datasets that are configured in a FiloDB cluster needs to use one Keyspace for raw (actively ingesting) data. With this change, keyspaces can be configured per dataset with the exception of MetaStore (checkpoints).
This is especially useful to merge two clusters for better resource utilization without the need for data migration. With the caveat that checkpoint records need to be migrated from source cluster to target cluster.