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] [Created] (CASSANDRA-8049) Explicitly examine current C* state on startup to detect incompatibilities before upgrade
Date Fri, 03 Oct 2014 15:53:34 GMT
Aleksey Yeschenko created CASSANDRA-8049:
--------------------------------------------

             Summary: 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
             Fix For: 3.0


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)

Mime
View raw message