cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1684) Entity groups
Date Wed, 04 Jan 2012 19:31:40 GMT


Jonathan Ellis commented on CASSANDRA-1684:

bq. Should we add a special "row group" api?

I really like how the composite PK model is shaking out over in CASSANDRA-2474.  Feels like
that's the right model for this too, conceptually.  Implementation-wise, wide rows still come
up short as noted above.

I'm starting to think that the right way to implement this is to start to erase the distinction
between row and column lookups.  Which is basically where Stu was going in CASSANDRA-674.
> Entity groups
> -------------
>                 Key: CASSANDRA-1684
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2
>   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
>  - 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message