[
https://issues.apache.org/jira/browse/CASSANDRA-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-13274:
-------------------------------------
Status: Patch Available (was: Open)
||cassandra-3.0|[branch|https://github.com/apache/cassandra/compare/cassandra-3.0...snazy:13274-rolling-upgrade-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-13274-rolling-upgrade-3.0-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-13274-rolling-upgrade-3.0-dtest/lastSuccessfulBuild/]
||cassandra-3.11|[branch|https://github.com/apache/cassandra/compare/cassandra-3.11...snazy:13274-rolling-upgrade-3.11]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-13274-rolling-upgrade-3.11-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-13274-rolling-upgrade-3.11-dtest/lastSuccessfulBuild/]
||trunk|[branch|https://github.com/apache/cassandra/compare/trunk...snazy:13274-rolling-upgrade-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-13274-rolling-upgrade-trunk-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-13274-rolling-upgrade-trunk-dtest/lastSuccessfulBuild/]
CI triggered.
Also tested a few CQL upgrade tests from "legacy" 3.0 to current trunk (to
verify the upgrade issue locally) and this patch to trunk (to verify the fix).
> Fix rolling upgrade to 4.0+
> ---------------------------
>
> Key: CASSANDRA-13274
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13274
> Project: Cassandra
> Issue Type: Bug
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Critical
> Fix For: 3.0.x, 3.11.x
>
>
> A rolling upgrade from 3.* to 4.0 (messaging version {{11}}) unveils a
> regression caused by CASSANDRA-11128.
> Generally, we store all possible options/attributes including the default
> values in the schema. This causes (expected) schema-version-mismatches during
> rolling upgrades and therefore we prevent schema pulls/pushes in this
> situation, which has been broken by CASSANDRA-11128.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
