[
https://issues.apache.org/jira/browse/CASSANDRA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731044#comment-14731044
]
Robert Stupp commented on CASSANDRA-10269:
------------------------------------------
Don't want to open a can of worms, but we seem to have 2.0 sstable level
compatibility in code code (not in messaging). I mean, do we "officially"
support 2.0 sstable compatibility? If yes, I think that should be tested, too -
if not, it would be better to remove it from the code IMO.
> Run new upgrade tests on supported upgrade paths
> ------------------------------------------------
>
> Key: CASSANDRA-10269
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10269
> Project: Cassandra
> Issue Type: Bug
> Components: Tests
> Reporter: Jim Witschey
> Assignee: Jim Witschey
>
> The upgrade dtests for 8099 backwards compatibility (originally dealt with in
> [this dtest PR|https://github.com/riptano/cassandra-dtest/pull/471] and [this
> JIRA ticket|https://issues.apache.org/jira/browse/CASSANDRA-9893]) need to be
> run with upgrades over the following upgrade paths:
> - 2.1 -> 3.0
> - 2.2 -> 3.0
> - 3.0 -> trunk
> There are a number of ways we could manage this. We could run the tests as
> part of the normal dtest jobs in 2.1, 2.2, and 3.0, and select what version
> to upgrade to based on the version of the test. We could also refactor the
> new upgrade tests to use the upgrade machinery in the existing upgrade tests.
> [~philipthompson] [~rhatch] Do you have opinions? Can you think of other
> options?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
