[
https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043384#comment-14043384
]
Benedict commented on CASSANDRA-7443:
-------------------------------------
A quick comment: we may need to make pluggability a bit higher in the stack
than sstable reader/writer; CcollationController should probably be involved in
this step. A related goal to keep in mind, whilst not the explicit goal of this
ticket, is making replacing "ColumnFamily" with a new internal
resultset/iterator abstraction a little easier. We should position ourselves to
be able to tackle that after this (or one more follow up) ticket.
We will eventually want to make writes configurable before they hit memtables
as well, though that can probably be bumped to a later ticket also.
> SSTable Pluggability v2
> -----------------------
>
> Key: CASSANDRA-7443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7443
> Project: Cassandra
> Issue Type: Bug
> 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)
