-
Notifications
You must be signed in to change notification settings - Fork 29
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
Use client-side timestamps #32
Comments
Most of the statements executed will either be LWTs (for lock etc) or schema changes, neither of which use client side timestamps. Are there other statements you think will benefit from this? |
@chbatey: Yes. Sometimes, in addition to DDL schema changes, you may want make DML changes e.g. to insert / update "provisioned" data - as distinct from data generated by the running of your application - and I can imagine a scenario where one older CQL file performs action X on a row, and a later CQL file performs action Y on the same row, and we would want action Y to be the "last write" that persists. This is perhaps relatively unlikely, but given that |
Although #29 is still needed for DDL changes, I believe we can and should ensure greater robustness of DML changes by using client-side timestamps (as described in http://www.datastax.com/dev/blog/java-driver-2-1-2-native-protocol-v3) for the CQL statements invoked by cqlmigrate.
Any thoughts / counter-opinions? If not, I'll raise a PR to cover this.
The text was updated successfully, but these errors were encountered: