[
https://issues.apache.org/jira/browse/CASSANDRA-13475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226281#comment-16226281
]
Blake Eggleston commented on CASSANDRA-13475:
---------------------------------------------
Sure, but everywhere it’s used, Cassandra is interacting with the storage
layer. You’re going to have to make changes everywhere it’s used anyway. I
don’t think it’s going to be practical to start with an api and refactor
Cassandra to conform to it.
In other words, a storage api (albeit a leaky one) already exists. Adding
another api on top of the existing one is just going to complicate things. I
think any effort to make storage pluggable needs to start with the loose api
that already exists, and start working out ways to refine it and hide
implementation details behind a more generic interface as needed, piece by
piece. That’s going to be 99.99% of the work involved here.
> 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
