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 Mon, 22 Aug 2011 19:06:29 GMT


Stu Hood commented on CASSANDRA-2995:

I opened CASSANDRA-3067: I see this ticket as being inevitable, but I'd (personally) like
to punt on full engine pluggability until there is a patch that proposes changing Cassandra
internals sufficiently to justify it. CASSANDRA-674 does not.

> 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