[
https://issues.apache.org/jira/browse/CASSANDRA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979673#action_12979673
]
Ryan King commented on CASSANDRA-1935:
--------------------------------------
That seems like a somewhat bigger change. Perhaps we could tackle the startup
situation now and open another ticket for making sure we don't try to stream
incompatible sstables?
> Refuse to open SSTables from the future
> ---------------------------------------
>
> Key: CASSANDRA-1935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1935
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Priority: Minor
> Fix For: 0.8
>
>
> If somebody has rolled back to a previous version of Cassandra that is unable
> to read an SSTable written by a future version correctly (indicated by a
> version change), failing fast is safer than accidentally performing a
> compaction that rewrites incorrect data and leaves you in an odd state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
