[
https://issues.apache.org/jira/browse/CASSANDRA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Goffinet updated CASSANDRA-389:
-------------------------------------
Description:
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>
was:
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>-<DATA|INDEX|FILTER>-<VERSION>
> SSTable Versioning
> ------------------
>
> Key: CASSANDRA-389
> URL: https://issues.apache.org/jira/browse/CASSANDRA-389
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.4
> Reporter: Chris Goffinet
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 0.4
>
>
> 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.
