[
https://issues.apache.org/jira/browse/CASSANDRA-13475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dikang Gu updated CASSANDRA-13475:
----------------------------------
Description:
In this jira, we discuss how to make Cassandra's storage engine to be
pluggable. We will discuss the scope, expectation, and guideline for this
project, as well as a detailed design so that we can create sub tasks for each
small project.
Here is a design quip we are currently working on:
https://quip.com/bhw5ABUCi3co
was:
In this jira, we discuss how to make Cassandra's storage engine to be pluggable.
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.
> Pluggable storage engine design
> -------------------------------
>
> 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 this jira, we discuss how to make Cassandra's storage engine to be
> pluggable. We will discuss the scope, expectation, and guideline for this
> project, as well as a detailed design so that we can create sub tasks for
> each small project.
> Here is a design quip we are currently working on:
> https://quip.com/bhw5ABUCi3co
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
