[
https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084999#comment-14084999
]
T Jake Luciani commented on CASSANDRA-7443:
-------------------------------------------
One point to discuss is the upgrade path. My vote is we should support a per
node default for the SSTable format (what's currently implemented),
This way a user can take a node and upgrade it to the new format before going
forward.
When a user does set the format to the non-default it will end up incrementally
upgrading the sstables as they are compacted effectively the same as how the
current sstable revisions work. He/she could also run upgradesstables.
I think making it a per node setting makes sense for users who want to opt-in
initally similar to how we did vnodes and sstable compression. Once the format
is proved in battle tested we can either change the default format or remove
the setting altogether.
> SSTable Pluggability v2
> -----------------------
>
> Key: CASSANDRA-7443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7443
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 3.0
>
>
> As part of a wider effort to improve the performance of our storage engine we
> will need to support basic pluggability of the SSTable reader/writer. We
> primarily need this to support the current SSTable format and new SSTable
> format in the same version. This will also let us encapsulate the changes in
> a single layer vs forcing the whole engine to change at once.
> We previously discussed how to accomplish this in CASSANDRA-3067
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
