-
Notifications
You must be signed in to change notification settings - Fork 120
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
Await schema agreement post migration #106
Comments
So the normal notification flow here isn't enough? Is it just too slow to pick up on that? |
Waiting for keyspace changed events will not work, for instance if you only add data there is not keyspace change. |
Is there any workaround which can be used right now? |
Yes use a single host to run all the migrations. You can check that by issuing describe schema queries to different hosts. |
I'm working on this in #133. Still working out the kinks (gocql test suite is failing for some combinations on Travis, incidentally only those that have auth enabled – weird). |
Kudos for working on it. |
Fixed in #133 |
This requires a patch to gocql. Gocql has a function
awaitSchemaAgreement
to wait for schema to be propagated to all the nodes. We should export that to Session. When done we should call it post each migration.The text was updated successfully, but these errors were encountered: