[ https://issues.apache.org/jira/browse/CASSANDRA-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943300#comment-15943300 ]
Sylvain Lebresne commented on CASSANDRA-13274: ---------------------------------------------- +1, but make sure to update NEWS file for trunk with the actual version this is going to make it in. Also, completely a nit, but for the changelog I'd probably rephrase to something like "Fix code to not exchange schema across major versions" as that's more precise and avoid referencing a version that doesn't exists yet. > 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)