[
https://issues.apache.org/jira/browse/CASSANDRA-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-6038:
----------------------------------------
Component/s: Distributed Metadata
> Support schema changes in mixed version clusters
> ------------------------------------------------
>
> Key: CASSANDRA-6038
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6038
> Project: Cassandra
> Issue Type: Sub-task
> Components: Distributed Metadata
> Reporter: Aleksey Yeschenko
> Priority: Major
> Labels: client-impacting
> Fix For: 4.x
>
>
> CASSANDRA-5845 made it so that schema changes in a major-mixed cluster are
> not propagated to the minorer-major nodes. This lets us perform
> backwards-incompatible schema changes in major releases safely - like adding
> the schema_triggers table, moving all the aliases to schema_columns, getting
> rid of the deprecated schema columns, etc.
> Even this limitation might be too strict, however, and should be avoided if
> possible (starting with at least versioning schema separately from messaging
> service versioning, and resorting to major->minor schema block only when
> truly necessary and not for every x->y pair).
--
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
