Sebastien Bonnet created CASSANDRA-11874:
--------------------------------------------
Summary: Schema upgrades are not guaranteed to have sequentially
increasing timestamps
Key: CASSANDRA-11874
URL: https://issues.apache.org/jira/browse/CASSANDRA-11874
Project: Cassandra
Issue Type: Bug
Reporter: Sebastien Bonnet
When executing schema upgrades programmatically (e.g. via the cqldriver), there
is no guarantee that the upgrades will be executed in order across the nodes.
This is because cassandra is always using the server generated timestamp when
announcing alter table statements or other DDL changes regardless of whether a
custom timestamp generator is provided when creating the session.
This could lead to failures or unexpected results. For instance
- DDL change #1 creates table A
- DDL change #2 adds a new column to table A, but finds that table A does not
exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
