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 Thu, 15 Dec 2011 20:51:31 GMT


Jonathan Ellis commented on CASSANDRA-1684:

bq. if there were more optimizations done on rows (allowed them to be even larger, etc.),
would that be a better approach? 

I think it would be.  That's definitely a long-term play, though.  I only have ideas on how
to fix some of the problems Sylvain raised.  And then there's others like CASSANDRA-3362.

But we kind of need to fix large rows independent of the entity group idea.

bq. Two use cases where same row does not work for us:

Both of these sound like basically workarounds for weaknesses elsewhere.  Which again feels
like the right answer is to fix those weaknesses rather than adding another layer of hack
on top.

I guess there's really two questions here:
- Should we add a special "row group" api?
- What should the implementation look like?

In other words, we could add a row group api and implement it in terms of large rows.  Or
implement it another way.  But, we want wide rows that work "well" independent of row groups,
so it feels like that's the right place to spend our efforts now.
> 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