[
https://issues.apache.org/jira/browse/CASSANDRA-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Zarutin updated CASSANDRA-5524:
------------------------------------
Attachment: CASSANDRA-5524.txt
Issue has verified, on both failure to load sstables w/o upgrade using this
tool, and upgrade and load upgraded sstables.
Details and steps to repro can we foundin attached CASSANDRA-5524.txt that was
reviewed by Nick Bailey.
> Allow upgradesstables to be run against a specified directory
> -------------------------------------------------------------
>
> Key: CASSANDRA-5524
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5524
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 1.2.6
>
> Attachments: 0001-Add-a-snapshot-upgrade-tool.patch,
> 0002-Rename-snapshotupgrade-to-sstableupgrade.patch,
> 0003-Update-NEWS.txt-and-debian-scripts.patch, CASSANDRA-5524.txt
>
>
> Currently, upgradesstables only modifies live SSTables. Because
> sstableloader cannot stream old SSTable formats, this makes it difficult to
> restore data from a snapshot taken in a previous major version of Cassandra.
> Allowing the user to specify a directory for upgradesstables would resolve
> this, but it may also be nice to upgrade SSTables in snapshot directories
> automatically or with a separate flag.
--
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
