cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13384) Legacy caching options can prevent 3.0 upgrade
Date Tue, 28 Mar 2017 22:17:41 GMT

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

Jeremiah Jordan commented on CASSANDRA-13384:
---------------------------------------------

Anyway, this code works.  Adding basically dead code to 3.x seems ugly to me, but it is possible
to hit this if you upgrade fast enough, so I guess it may be worth adding it, since we can
drop it on merge to master.

> Legacy caching options can prevent 3.0 upgrade
> ----------------------------------------------
>
>                 Key: CASSANDRA-13384
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13384
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Schema
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>            Priority: Minor
>             Fix For: 3.0.x, 3.11.x
>
>
> In 2.1, we wrote caching options as a JSONified map, but we tolerated raw strings ["ALL",
"KEYS_ONLY", "ROWS_ONLY", and "NONE"|https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/cache/CachingOptions.java#L42].
> If a 2.1 node with any of these strings is upgraded to 3.0, the legacy schema migration
will fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message