cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-389) SSTable Versioning
Date Thu, 27 Aug 2009 17:20:59 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748457#action_12748457
] 

Stu Hood commented on CASSANDRA-389:
------------------------------------

> but I renamed a set of sstable files in data/ to the "wrong" version and it did not catch
this at startup.
I'm not sure what you mean. Which is the "wrong" version: the legacy version?

> (does it still ignore tmp files at startup?)
I'll double check, but I assume so. I didn't change the check that removes tmp files, because
it did it based on looking for TEMPFILE_MARKER anywhere in the file name, which should continue
to work.

> 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: 389-v3.patch, 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.


Mime
View raw message