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) First version of pluggable storage engine API.
Date Fri, 03 Nov 2017 16:04:00 GMT

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

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

[~dikanggu] SLOW DOWN!

I’m not asking you questions, or asking for more details, I’m trying to have a discussion
with you. This is going to be a long process, and without a high level plan or strategy, it’s
not going anywhere.

Each point in the plan proposal I posted is going to end up being it’s own lengthy discussion.
A few sentences in a quip doc about a major cassandra component is nearly meaningless, and
is just noise at this point. Honestly, I’d suggest you edit out the pasted doc here just
to remove an unnecessary wall of text which is linked elsewhere.

Now look, each of my points (well pair of points, discussion/implementation are split up chronologically)
is a component that’s going to need to be individually refactored. As an incremental approach
to abstracting the storage layer, does this make sense?

> 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. 
> Here is a design quip we are currently working on:  https://quip.com/bhw5ABUCi3co
> 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