[
https://issues.apache.org/jira/browse/CASSANDRA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stu Hood updated CASSANDRA-389:
-------------------------------
Attachment: CASSANDRA-389.diff
The coding style changes are in this new version of the patch. I also noticed
that we weren't ignoring subdirectories in the ColumnFamily directory
(BootstrapTest leaves behind a subdirectory in there, which is a separate
issue).
I didn't change the tokenization, because I didn't see how it would make the
code simpler... since TEMPFILE_MARKER is optional, checking the count of tokens
isn't enough, and the split code would have had a proliferation of nested if
statements (or something identical to the current code, with a position int to
increment, rather than a 'nextToken' method).
> 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
>
> Attachments: CASSANDRA-389.diff, CASSANDRA-389.diff
>
>
> 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.
