[
https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049533#comment-14049533
]
Edward Capriolo commented on CASSANDRA-7443:
--------------------------------------------
I know its off topic anyway but...
I would suggest that Sized and LevelDB compose what essentially are two
pluggable storage engines, also both can be compressed, so maybe that is 2.5.
There are other ticktes around minimizing re-compaction for write once TTL only
data. I do agree that having N storage engines would be a bad. But I do not
feel like sized and leveled are the best fit for a variety of use cases.
I have a column-family-per-month design to get around re compaction issues in a
time series application. Many suggest that cassandra is the IDEAL timeseries
database, but its current compaction system for level/sized does not seem like
the perfect fit to me.
> 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)
