cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2995) Making Storage Engine Pluggable
Date Tue, 23 Aug 2011 06:37:31 GMT


Stu Hood commented on CASSANDRA-2995:

bq. -1. "if you can't provide the same data model, you're creating fragmentation, not pluggability."
Anything that can implement ordered tables with compound keys can provide Cassandra's datamodel
(which is almost any disk-backed data store).

> Making Storage Engine Pluggable
> -------------------------------
>                 Key: CASSANDRA-2995
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.8.2
>            Reporter: Muga Nishizawa
> Will you design and implement Cassandra's storage engine API like MyCassandra?
> MyCassandra provides extensible architecture for pluging other storage engines to Cassandra
like MySQL.  
> It could be advantageous for Cassandra to make the storage engine pluggable.  This could
allow Cassandra to 
> - deal with potential use cases where maybe the current sstables are not the best fit
> - allow several types of internal storage formats (at the same time) optimized for different
data types
> - allow easier experiments and research on new storage formats (encourage research institutions
to do strange things with Cassandra)
> - there could also be potential advantages from better isolation of the data engine in
terms of less risk for data corruptions if other parts of Cassandra change

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message