Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CE0718ABE for ; Fri, 4 Sep 2015 15:56:46 +0000 (UTC) Received: (qmail 30464 invoked by uid 500); 4 Sep 2015 15:56:45 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 30424 invoked by uid 500); 4 Sep 2015 15:56:45 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 30409 invoked by uid 99); 4 Sep 2015 15:56:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Sep 2015 15:56:45 +0000 Date: Fri, 4 Sep 2015 15:56:45 +0000 (UTC) From: "Philip Thompson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10269) Run new upgrade tests on supported upgrade paths MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730982#comment-14730982 ] Philip Thompson commented on CASSANDRA-10269: --------------------------------------------- Now that we bucketize, we could easily run them as part of the normal jobs. That would probably be best. The question is, what do we set *old* version to when running on 3.0? > 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)