cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8928) Add downgradesstables
Date Mon, 27 Jun 2016 14:42:52 GMT

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

Aleksey Yeschenko commented on CASSANDRA-8928:
----------------------------------------------

bq. The same end result can be achieved, although with maybe a bit more of work, by backing
up sstables of the upgraded node and wiping/recreating the node in a previous version, and
then use sstableloader of the newer version to reload the data in the recreated node, which
would be easily enabled by CASSANDRA-8110.

sstableloader itself however is not backward or future compatible at the moment (schema loading
code isn't, for one). Not a big deal, but something we should make work and add tests for.
Otherwise I agree that CASSANDRA-8110 will do, at least for now. We can close this JIRA now
and reopen later, if necessary.

> 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
>            Assignee: Kaide Mu
>            Priority: Minor
>              Labels: gsoc2016, mentor
>
> 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)

Mime
View raw message