[
https://issues.apache.org/jira/browse/CASSANDRA-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506840#comment-14506840
]
Sam Tunnicliffe commented on CASSANDRA-8049:
--------------------------------------------
I've pushed a rebased version
[here|https://github.com/beobal/cassandra/tree/8049]. I've also relaxed the
check on previous and current installed versions. If a previous install is
detected we still snapshot the tables in the system keyspace, but I've removed
the check that aborts startup if the previous version was "too old" as
hardcoding the oldest permitted version was just too brittle & burdensome.
> Explicitly examine current C* state on startup to detect incompatibilities
> before upgrade
> -----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8049
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8049
> Project: Cassandra
> Issue Type: Bug
> Reporter: Aleksey Yeschenko
> Assignee: Sam Tunnicliffe
> Fix For: 3.0
>
> Attachments: 8049-v2.txt, 8049.txt
>
>
> Unfortunately, we cannot rely on users reading, and following, NEWS.txt
> before upgrading. People don't read, or ignore it, and sometimes have issues
> as the result (see CASSANDRA-8047, for example, and I know of several cases
> like that one).
> We should add an explicit compatibility check on startup, before we modify
> anything, or write out sstables with the new format. We should fail and
> complain loudly if we detect a skipped upgrade step.
> We should also snapshot the schema tables before attempting any conversions
> (since it's not uncommon to make schema modifications as part of the upgrade).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
