[
https://issues.apache.org/jira/browse/CASSANDRA-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945688#comment-15945688
]
Jeff Jirsa commented on CASSANDRA-13384:
----------------------------------------
How strong is your desire to see a dtest? I think it's a reasonable ask, but
it's also a LOT of effort.
The dtest upgrade logic that exists requires a consistent native proto version
through the test. Since 2.0 and 3.0 don't have a common native proto, none of
the existing rolling tests can be used - we'd have to write a new harness that
shuts down the session and reconnects midway through the test, which is
do-able, but a fair amount of effort for something that seems like it's
testable with a unit test.
> 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)
