[
https://issues.apache.org/jira/browse/CASSANDRA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998732#comment-12998732
]
Ed Anuff commented on CASSANDRA-1684:
-------------------------------------
This is something I've been thinking about while consolidating the number of
column families within an application so that I ended up with row keys that
were constructed from concatenating an entity id with various other strings
(eg. 9081bd70-3fe4-11e0-9207-0800200c9a66:something ). Is it feasible to have
a partitioner that hashed on just the first x bytes in a key? Do tokens have
to be one-to-one unique with keys, or could you have multiple keys share the
same token? (apparently that's currently possible, although an extreme edge
case, with the RandomPartitioner)
> 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: 0.8
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
