Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 31 Jul 2013 18:11:49 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12660765.1375214127397.145962.1375294309270@arcas>
In-Reply-To: <JIRA.12660765.1375214127397@arcas>
References: <JIRA.12660765.1375214127397@arcas>
Subject: [jira] [Commented] (CASSANDRA-5831) Running sstableupgrade on C*
 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tyler Hobbs commented on CASSANDRA-5831:
----------------------------------------

bq. I think all we need to do here is "don't run upgradesstables if the ks/cf/ heirarchy doesn't exist already for the system tables."

If I'm interpreting you correctly, we'll just want upgradesstables to error out in that case and mention something about starting Cassandra 1.1+ before running upgradesstables again, is that correct?
                
> Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5831
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5831
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Jeremiah Jordan
>            Assignee: Tyler Hobbs
>            Priority: Minor
>             Fix For: 1.2.9
>
>
> If you try to upgrade from C* 1.0.X to 1.2.X and run offline sstableupgrade to try and migrate the sstables before starting 1.2.X for the first time, it messes up the system folder, because it doesn't migrate it right, and then C* 1.2 can't start.
> sstableupgrade should either refuse to run against a C* 1.0 data folder, or migrate stuff the right way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira