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] Updated: (CASSANDRA-389) SSTable Versioning
Date Tue, 12 Jan 2010 02:44:54 GMT

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

Stu Hood updated CASSANDRA-389:
-------------------------------

    Attachment: 389-v5-3-use-descriptor-for-streaming.diff
                389-v5-2-add-keyspace-to-descriptor.diff
                389-v5-1-rebase-v4-for-trunk.diff

New patchset: v5. Rebases v4 for trunk, adds the keyspace to the descriptor, and uses descriptors
for streaming.

No versions are checked: they're just being made available, so that something like #674 can
increment, and add conditional handling.

> 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
>             Fix For: 0.9
>
>         Attachments: 389-v3.patch, 389-v4.patch, 389-v5-1-rebase-v4-for-trunk.diff, 389-v5-2-add-keyspace-to-descriptor.diff,
389-v5-3-use-descriptor-for-streaming.diff, 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