cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola OrrĂ¹ (Issue Comment Edited) (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-2995) Making Storage Engine Pluggable
Date Thu, 10 Nov 2011 11:40:52 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147617#comment-13147617
] 

Nicola OrrĂ¹ edited comment on CASSANDRA-2995 at 11/10/11 11:39 AM:
-------------------------------------------------------------------

I wonder how alternative engines would perform on very large rows. One of the main rationales
behind my choice for Cassandra was exactly that.

Besides it, I wonder why I would want to back the backend with another backend. Looks cool
in term of interface consistency, but wouldn't the overhead in terms of performance and operations
be a bit too much?

I'm working on an application which already has swappable backends (so I can trade Cassandra
for some other one, say Redis). That would allow me to deploy a redis backend in place of
a cassandra backend. What would the advantage of having to deploy Cassandra AND Redis be?

However, there is a point in "swappable engines". MySQL survived well the myisam/innodb malarkey.
                
      was (Author: norru):
    I wonder how alternative engines would perform on very large rows. One of the main rationales
behind my choice for Cassandra was exactly that.
                  
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message