[
https://issues.apache.org/jira/browse/CASSANDRA-11874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-11874:
-----------------------------------------
Component/s: Distributed Metadata
> 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
> Components: Distributed Metadata
> Reporter: Sebastien Bonnet
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
