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

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

Hmm, there's one complication: {{sstableupgrade}} requires a keyspace and table 
to be specified, whereas the data directory migration is normally done all at 
once.  Changing the directory layout for only a single CF feels strange, but 
changing the layout for other keyspaces and CFs that you didn't specify also 
feels wrong.
                
> 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
>
>         Attachments: 
> 0001-Check-for-current-directory-layout-before-upgrading.patch
>
>
> 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

Reply via email to