[
https://issues.apache.org/jira/browse/CASSANDRA-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088934#comment-13088934
]
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: https://issues.apache.org/jira/browse/CASSANDRA-2995
> 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.
> https://github.com/sunsuk7tp/MyCassandra/
>
> 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: http://www.atlassian.com/software/jira
