[
https://issues.apache.org/jira/browse/CASSANDRA-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-5511:
---
Attachment: CASSANDRA-5511-on_1.2.patch
CASSANDRA-5511-on_trunk.patch
adds an ignored test to 1.2 that generates sstables and refactors the test in
trunk
- apply 1.2-patch
- merge 1.2 -> trunk
- apply trunk-patch
if the patches look ok, i can do the git-gymnastics (ie, they can be applied on
current trunk/1.2 without breaking anything)
> Clean up backwards compatibility complexity for 2.0
> ---
>
> Key: CASSANDRA-5511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5511
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Jonathan Ellis
>Assignee: Jonathan Ellis
> Fix For: 2.0
>
> Attachments: CASSANDRA-5511-on_1.2.patch,
> CASSANDRA-5511-on_trunk.patch
>
>
> 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: http://www.atlassian.com/software/jira
