[
https://issues.apache.org/jira/browse/CASSANDRA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Dusbabek updated CASSANDRA-389:
------------------------------------
Comment: was deleted
(was: +1 on stu's patches. They can go in right after CASSANDRA-810 (anybody
care to review it?).)
> SSTable Versioning
> ------------------
>
> Key: CASSANDRA-389
> URL: https://issues.apache.org/jira/browse/CASSANDRA-389
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Chris Goffinet
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 0001-Rebase-389-v4-for-trunk.patch,
> 0002-Add-keyspace-name-to-SSTable.Descriptor.patch,
> 0003-Use-SSTable.Descriptor-for-Streaming.patch, 0004-Validate-params.patch,
> 0005-The-special-casing-begins.patch, 0006-Merge-oopses.patch,
> 0007-Don-t-serialize-Descriptors-as-filenames.patch, 389-v3.patch
>
>
> As we continue to make changes to the on-disk format of SSTables, I propose
> we start versioning. The easiest way without breaking backwards compatibility
> is to store the version in the filename. This would allow us to figure out
> the version without looking at the SSTable data. After speaking to Jonathan
> here is the proposed example:
> <CF>-<ID>-<VERSION>-<DATA|INDEX|FILTER>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
