[
https://issues.apache.org/jira/browse/CASSANDRA-13475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210649#comment-16210649
]
Dikang Gu commented on CASSANDRA-13475:
---------------------------------------
[~bdeggleston], [~spo...@gmail.com], this little patch shows how read/write
paths and streaming work with the storage engine api,
https://github.com/DikangGu/cassandra/commit/3238dfbd8f4abfa2d95d5343edf07985fb732bd1.
The comment out part should be moved to a CQLEngine in the future.
For streaming, I think the rocksdb streaming impl gives good example about how
a new storage engine should implement the streaming flow,
https://github.com/Instagram/cassandra/tree/rocks_3.0/src/java/org/apache/cassandra/rocksdb/streaming.
Most of the logic are implemented within the storage engine, there is very
little changes outside the engine.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
