[
https://issues.apache.org/jira/browse/CASSANDRA-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868291#comment-13868291
]
Aleksey Yeschenko commented on CASSANDRA-6038:
----------------------------------------------
No. You'll just get mismatching schema versions across nodes (all the 2.0 nodes
settling on one version, all the 2.1 nodes settling on another one).
> Make the inter-major schema migration barrier more targeted, and, ideally,
> non-existent
> ---------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6038
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6038
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksey Yeschenko
> Fix For: 2.1
>
>
> 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
(v6.1.5#6160)
