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] Issue Comment Edited: (CASSANDRA-389) SSTable Versioning
Date Wed, 26 Aug 2009 02:09:59 GMT

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

Stu Hood edited comment on CASSANDRA-389 at 8/25/09 7:09 PM:
-------------------------------------------------------------

The filename format I settled on was:

<CF>[-<TMP>]-<VERSION>-<GENERATION>-<DATA|INDEX|FILTER>

      was (Author: stuhood):
    The filename format I settled on was:

<CF>[-<TMP>]-<VERSION>-<ID>-<DATA|INDEX|FILTER>
  
> 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
>
>
> 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