cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7443) SSTable Pluggability v2
Date Wed, 25 Jun 2014 12:40:25 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043398#comment-14043398
] 

Jason Brown commented on CASSANDRA-7443:
----------------------------------------

Do we actually want to move the abstraction even higher? When I was experimenting with creating
a pluggable storage engine, I started by splitting ColumnFamilyStore in half, as that's where
a lot of things like compaction strategy, sstable, and such, begin to be exposed.

bq. We will eventually want to make writes configurable before they hit memtables as well

Yeah, this is definitely starting to sound like a pluggable storage engine :). Thus, that's
why I think CFS is a good place place to start. 

> 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)

Mime
View raw message