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

Changing Replication details after keyspace is created #27

Open
rickalm opened this issue Nov 15, 2017 · 5 comments
Open

Changing Replication details after keyspace is created #27

rickalm opened this issue Nov 15, 2017 · 5 comments

Comments

@rickalm
Copy link

rickalm commented Nov 15, 2017

Has any thought been given to evaluating the replication defined in the yaml file vs the actual keyspace deployed in cassandra. We discovered its not possible to alter the replication in the yaml file and have it take effect, it only happens if creating the keyspace.

@danielkza
Copy link
Contributor

danielkza commented Nov 15, 2017 via email

@rickalm
Copy link
Author

rickalm commented Nov 15, 2017

In our case the datacenter names are different for each profile, a single migration is problematic.
I know I could "overload" the replication, but between our three "profiles" we share a datacenter and I dont want to start naming DC's env-geo

@danielkza
Copy link
Contributor

danielkza commented Nov 15, 2017 via email

@rickalm
Copy link
Author

rickalm commented Nov 16, 2017

Daniel,
I meant to post yesterday. I understand your limited resources and i'll gladly take a swipe at a PR to add the functionality for you to review when you have a chance

@fernandezjose
Copy link
Contributor

Go for it @rickalm. @danielkza is very compassionate with PRs :)

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

3 participants