cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3067) Simple SSTable Pluggability
Date Thu, 01 Sep 2011 03:51:10 GMT


Jonathan Ellis updated CASSANDRA-3067:

    Reviewer: slebresne

> Simple SSTable Pluggability
> ---------------------------
>                 Key: CASSANDRA-3067
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 1.0
>         Attachments: 0001-CASSANDRA-3067-Create-an-ABC-for-SSTableIdentityIterat.txt,
0002-CASSANDRA-3067-Move-from-linear-SSTable-versions-to-fe.txt, 0003-CASSANDRA-3067-Create-an-ABC-for-SSTableWriter.txt,
0004-CASSANDRA-3067-Rename-SSTable-Names-Slice-Iterator-to-.txt, 0005-CASSANDRA-3067-Create-ABCs-for-SSTableReader-and-KeyIt.txt,
> CASSANDRA-2995 proposes full storage engine pluggability, which is probably unavoidable
in the long run. For now though, I'd like to propose an incremental alternative that preserves
the sstable model, but allows it to evolve non-linearly.
> The sstable "version" field could allow for simple switching between writable sstable
types, without moving all the way to differentiating between engines as CASSANDRA-2995 requires.
This can be accomplished by moving towards a "feature flags" model (with a mapping between
versions and feature sets), rather than a linear versions model (where versions can be strictly
ordered and all versions above X have a feature).
> There are restrictions on this approach:
> * It's sufficient for an alternate SSTable(Writer|Reader|*) set to require a patch to
enable (rather than a JAR)
> * Filenames/descriptors/components must conform to the existing conventions

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message