You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2017/02/27 14:06:46 UTC

[jira] [Commented] (CASSANDRA-13274) Fix rolling upgrade to 4.0+

    [ https://issues.apache.org/jira/browse/CASSANDRA-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885831#comment-15885831 ] 

Aleksey Yeschenko commented on CASSANDRA-13274:
-----------------------------------------------

Not sure I understand the issue.

Could you please be more clear regarding what is broken, what the expected behaviour is, and what is the behaviour you are observing?

> 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)