cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13475) Define pluggable storage engine API.
Date Wed, 26 Apr 2017 16:52:04 GMT

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

Blake Eggleston commented on CASSANDRA-13475:
---------------------------------------------

It would also need to support repair, so it would need to be able to 
 * Mark portions of data as unrepaired, pending repair, or repaired, and preserve this during
streaming
 * Build merkle trees (or some implementation specific data) on all or some of it's data in
a token range


> Define 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
>
> 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.3.15#6346)

Mime
View raw message