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] Updated: (CASSANDRA-389) SSTable Versioning
Date Fri, 28 Aug 2009 19:26:32 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-389:
-------------------------------------

          Component/s: Core
    Affects Version/s:     (was: 0.4)
        Fix Version/s:     (was: 0.4)

okay.  let's table this until we actually need to break SSTable format again for whatever
reason.

> SSTable Versioning
> ------------------
>
>                 Key: CASSANDRA-389
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-389
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Goffinet
>            Assignee: Stu Hood
>            Priority: Minor
>         Attachments: 389-v3.patch, 389-v4.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