cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5511) Clean up backwards compatibility complexity for 2.0
Date Wed, 24 Apr 2013 06:09:16 GMT


Marcus Eriksson commented on CASSANDRA-5511:

iirc i created a throwaway unit test that does a few RMs with a breakpoint to stop SchemaLoader
from removing the sstable, then copied it into the legacy dir

want me to do it again for ic?
> Clean up backwards compatibility complexity for 2.0
> ---------------------------------------------------
>                 Key: CASSANDRA-5511
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 2.0
> We've supported rolling upgrades (network-compatible for read/write operations) for several
releases, but both 1.0 -> 1.1 and 1.1 -> 1.2 required being on a recent release of the
immediately prior major series for this to work as desired.
> Meanwhile, we still support reading sstables at least back to 0.6 and possibly even earlier.
 This makes dealing with changes to the sstable quite challenging; the recently written-and-reverted
CASSANDRA-5487 comes to mind.
> 2.0 is a good place to drop support for sstables older than 1.2.5.  Our experience with
network compatibility demonstrates that this is not an unreasonable burden to impose, and
the major version number change suggests that this is a logical time to make such a change.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message