You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org> on 2011/11/23 17:25:40 UTC

[jira] [Commented] (CASSANDRA-1684) Entity groups

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

Jonathan Ellis commented on CASSANDRA-1684:
-------------------------------------------

Do we really need row groups now that we can have arbitrary nesting within a row via composite columns?  Looked at that way the row key itself becomes the "entity group id."
                
> 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