cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dikang Gu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-13475) First version of pluggable storage engine API.
Date Thu, 02 Nov 2017 05:39:00 GMT

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

Dikang Gu edited comment on CASSANDRA-13475 at 11/2/17 5:38 AM:
----------------------------------------------------------------

[~iamaleksey], [~bdeggleston], I write a new [patch|https://github.com/DikangGu/cassandra/commit/6d690c859cb640c320f25888cea1bdeb41565c2b]
of the interfaces abstracted from the Keyspace/CFS, and also a quip about the components we
need (and not need) to refactor and move to a CQLStorageEngine, https://quip.com/bhw5ABUCi3co.


Before I go deep and start to refactor the Keyspace/CFS classes, I'd like to hear your thoughts
on it.


was (Author: dikanggu):
[~iamaleksey], [~bdeggleston], I write a new [patch|https://github.com/DikangGu/cassandra/commit/6d690c859cb640c320f25888cea1bdeb41565c2b]
of the interfaces abstracted from the Keyspace/, and also a quip about the components we need
(and not need) to refactor and move to a CQLStorageEngine, https://quip.com/bhw5ABUCi3co.


Before I go deep and start to refactor the Keyspace/CFS classes, I'd like to hear your thoughts
on it.

> 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
>            Priority: Major
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message