[
https://issues.apache.org/jira/browse/CASSANDRA-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945598#comment-15945598
]
Jeff Jirsa commented on CASSANDRA-13384:
----------------------------------------
No patch for trunk, we don't expect 2.x -> 4.0 upgrades, they have to go
through 3.0, which will handle the upgrade.
|| branch || utest || dtest ||
| [3.0|https://github.com/jeffjirsa/cassandra/tree/cassandra-3.0-13384] |
[testall|http://cassci.datastax.com/job/jeffjirsa-cassandra-3.0-13384-testall/]
| [dtest|http://cassci.datastax.com/job/jeffjirsa-cassandra-3.0-13384-dtest/] |
| [3.11|https://github.com/jeffjirsa/cassandra/tree/cassandra-3.11-13384] |
[testall|http://cassci.datastax.com/job/jeffjirsa-cassandra-3.11-13384-testall/]
| [dtest|http://cassci.datastax.com/job/jeffjirsa-cassandra-3.11-13384-dtest/]
|
> 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)
