[
https://issues.apache.org/jira/browse/CASSANDRA-13475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198094#comment-16198094
]
Dikang Gu edited comment on CASSANDRA-13475 at 10/10/17 8:05 PM:
-----------------------------------------------------------------
Here is the first version of the pluggable storage engine api, based on trunk.
|[trunk|https://github.com/DikangGu/cassandra/commit/f1c69f688d05504f7409dd735e1473982c59fa52]|[unit
test|https://circleci.com/gh/DikangGu/cassandra/2]|
It contains the API, and a little bit refactoring of the streaming part.
You can check https://github.com/Instagram/cassandra/tree/rocks_3.0 for the
RocksDB based implementation.
was (Author: dikanggu):
Here is the first version of the pluggable storage engine api, based on trunk.
https://github.com/DikangGu/cassandra/commit/f1c69f688d05504f7409dd735e1473982c59fa52
It contains the API, and a little bit refactoring of the streaming part.
You can check https://github.com/Instagram/cassandra/tree/rocks_3.0 for the
RocksDB based implementation.
> First version of pluggable storage engine API.
> ----------------------------------------------
>
> Key: CASSANDRA-13475
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13475
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Dikang Gu
> Assignee: Dikang Gu
>
> In order to support pluggable storage engine, we need to define a unified
> interface/API, which can allow us to plug in different storage engines for
> different requirements.
> In very high level, the storage engine interface should include APIs to:
> 1. Apply update into the engine.
> 2. Query data from the engine.
> 3. Stream data in/out to/from the engine.
> 4. Table operations, like create/drop/truncate a table, etc.
> 5. Various stats about the engine.
> I create this ticket to start the discussions about the interface.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
