cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13384) Legacy caching options can prevent 3.0 upgrade
Date Thu, 22 Jun 2017 19:50:02 GMT

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

Joshua McKenzie updated CASSANDRA-13384:
----------------------------------------
    Component/s:     (was: Schema)
                 Distributed Metadata

> 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: Distributed Metadata
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>            Priority: Minor
>             Fix For: 3.0.13, 3.11.0
>
>
> 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message