cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10269) Run new upgrade tests on supported upgrade paths
Date Tue, 08 Sep 2015 22:05:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735716#comment-14735716
] 

Jim Witschey commented on CASSANDRA-10269:
------------------------------------------

Filed the changes to the dtests here:

https://github.com/riptano/cassandra-dtest/pull/537

[~iamaleksey] I believe I could add the 2.1->2.2 upgrade test as a job here:

http://cassci.datastax.com/view/Upgrades/

[~rhatch] can you confirm that that would work?

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

Mime
View raw message