cassandra-commits mailing list archives

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

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

Jonathan Ellis commented on CASSANDRA-389:
------------------------------------------

i suggest replacing the ad-hoc split/tokenize code in multiple places with a single method

  SSTableInfo parseSSTableInfo(String filename)

where SSTI is something like

class SSTableInfo {
  public final String columnFamilyName, version;
  public final int generation;
}


> 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
>            Priority: Minor
>
> 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>

-- 
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