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

Migrations and Consitency #10

Closed
algermissen opened this issue May 18, 2014 · 1 comment
Closed

Migrations and Consitency #10

algermissen opened this issue May 18, 2014 · 1 comment

Comments

@algermissen
Copy link

Hi,

I am wondering: given that migrations often involve schema changes and subsequent data inserts of updates (e.g. update on a column just added by 'alter table'), what are your experiences with the fact that C* does not provide a way to control that the schema change actually occurred on all nodes before the update hits the cluster.

Do you have any pointers to discussions with the community that suggests that such migrations are even possible in a predictable fashion?

Jan

@algermissen
Copy link
Author

Found it: use 'describe cluster' to explicitly check for schema propagation to finish:

http://www.datastax.com/support-forums/topic/schema-versions-disagree#post-7055

Cheers,
Jan

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