[
https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043412#comment-14043412
]
Jason Brown commented on CASSANDRA-7443:
----------------------------------------
bq. we probably don't want to reimplement LCS/STCS etc. for each storage engine
that needs them
Agreed, but not all storage engines will need compaction. I'm not sure it's as
easy as "a custom compaction strategy (which permits, e.g., turning it off)",
but I would need to think through it some more. However, storage engines should
be able to freely pull in existing components like compaction strategies,
current memtable, and the like.
> 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)
