[
https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-5831:
--------------------------------------
Component/s: Tools
Priority: Minor (was: Major)
Fix Version/s: 1.2.9
Assignee: Tyler Hobbs
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."
In particular, upgradesstables against a 1.1 install should be fine.
> 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
