cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Anuff (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-1684) Entity groups
Date Wed, 23 Nov 2011 17:37:40 GMT

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

Ed Anuff commented on CASSANDRA-1684:
-------------------------------------

I agree with Sylvain points.  This does raise the question, though, if there were more optimizations
done on rows (allowed them to be even larger, etc.), would that be a better approach?  I'm
personally all for that.
                
> Entity groups
> -------------
>
>                 Key: CASSANDRA-1684
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1684
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>             Fix For: 1.1
>
>   Original Estimate: 80h
>  Remaining Estimate: 80h
>
> Supporting entity groups similar to App Engine's (that is, allow rows to be part of a
parent "entity group," whose key is used for routing instead of the row itself) allows several
improvements:
>  - batches within an EG can be atomic across multiple rows
>  - order-by-value queries within an EG only have to touch a single replica even with
RandomPartitioner

--
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