[ https://issues.apache.org/jira/browse/CASSANDRA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan King updated CASSANDRA-1935: --------------------------------- Attachment: CASSANDRA-1935.patch Here's the simplest patch that could work. I'm a bit afraid that this may cause problems in scenarios other than startup. Also, I'd appreciate feedback on a better exception to raise. > 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 > > Attachments: CASSANDRA-1935.patch > > > 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.