Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 19 Mar 2015 14:58:38 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12780101.1425656730000.144003.1426777118961@Atlassian.JIRA>
In-Reply-To: <JIRA.12780101.1425656730000@Atlassian.JIRA>
References: <JIRA.12780101.1425656730000@Atlassian.JIRA>
 <JIRA.12780101.1425656730171@arcas>
Subject: [jira] [Resolved] (CASSANDRA-8928) Add downgradesstables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-8928.
---------------------------------------
    Resolution: Later

Given that we're already signing up for a big testing effort around 3.0+, let's take this off the table for now.

> Add downgradesstables
> ---------------------
>
>                 Key: CASSANDRA-8928
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8928
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jeremy Hanna
>            Priority: Minor
>
> As mentioned in other places such as CASSANDRA-8047 and in the wild, sometimes you need to go back.  A downgrade sstables utility would be nice for a lot of reasons and I don't know that supporting going back to the previous major version format would be too much code since we already support reading the previous version.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)