[
https://issues.apache.org/jira/browse/CASSANDRA-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-13274:
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.11.x)
(was: 3.0.x)
3.11.0
3.0.13
Status: Resolved (was: Patch Available)
Thanks!
Committed as
[6da41ed047ed5ef8a5d11e7a60e73dfeb129a72a|https://github.com/apache/cassandra/commit/6da41ed047ed5ef8a5d11e7a60e73dfeb129a72a]
to [cassandra-3.0|https://github.com/apache/cassandra/tree/cassandra-3.0] and
merged up to trunk.
Trunk commit contains the updated changes in NEWS.txt.
> Fix code to not exchange schema across major versions
> -----------------------------------------------------
>
> 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.13, 3.11.0
>
>
> 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)
