[
https://issues.apache.org/jira/browse/CASSANDRA-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368951#comment-14368951
]
Benedict commented on CASSANDRA-8928:
-------------------------------------
Data translations are inherently dangerous acts, and very hard to vet (see
CASSANDRA-8993 which seems to be a result of upgrade corrupting index state so
that records are silently not returned). Having a bidirectional translation
seems particularly problematic. If we are to go down this route, we need to
ensure HUGE effort is put in to exhaustively testing the resulting outputs,
after a double cycle of upgrade/downgrade. This effort wouldn't be wasted
though, as it would also help vet upgrades, which are essential acts.
> 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
> Priority: Minor
>
> 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)
