cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: 0.6, 0.7, and the future
Date Thu, 18 Feb 2010 19:56:49 GMT
On Thu, Feb 18, 2010 at 2:49 PM, Ryan King <ryan@twitter.com> wrote:
> On Thu, Feb 18, 2010 at 11:45 AM, Anthony Molinaro
> <anthonym@alumni.caltech.edu> wrote:
>> +1
>> (although I'm dreading the export from old sstables into new sstables,
>> any ideas on how fast that might be?, and I guess any idea if a tool
>> for doing this will be provided, or is it sstable2json and json2sstable?)
>
> I'm not entirely sure of the plans here, but I think the idea is that
> any release of cassandra going forward is going to have to be able to
> deal with multiple versions of SSTable formats.
>
> I propose that when we change the format in a release we don't
> proactively rewrite the tables– just keep the old tables as-is and
> only write with the new format when we're already going to be writing
> a table (flushing or compacting). That way you can have a smooth
> upgrade if you want, or if you want to force the upgrade, you just
> trigger a major compaction.

This is my preference as well.  We'll see if we can pull it off. :)

-Jonathan

Mime
View raw message