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

Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/03/28 17:30:42 UTC

[jira] [Updated] (CASSANDRA-13384) Legacy caching options can prevent 3.0 upgrade

     [ https://issues.apache.org/jira/browse/CASSANDRA-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Jirsa updated CASSANDRA-13384:
-----------------------------------
    Status: Patch Available  (was: Open)

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