cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-389) SSTable Versioning
Date Thu, 27 Aug 2009 19:25:59 GMT


Jonathan Ellis commented on CASSANDRA-389:

not much point in having a version code if we don't validate it.  this needs to start now,
not in the future, since even if we did try to preserve indefinite backwards compatibility,
there is no way to make 0.4 forwards-compatibile.

(for the record, both of those options are bad.  we'll probably write conversion utilities
for contrib/ to migrate from version N-1 to version N.  anything else is insane -- we have
enough trouble debugging a single binary format!)

> SSTable Versioning
> ------------------
>                 Key: CASSANDRA-389
>                 URL:
>             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:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message