[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850474#action_12850474
]
Jonathan Ellis commented on CASSANDRA-749:
------------------------------------------
The more I think about the pseudo-CF api the less I like it.
We want to push filtering down to the node with the data on it, where possible.
This means that, even if we only actually scan one index, we need to be able
to say "AND cond2 op val2" and apply that before moving data off-node. This
isn't possible the "pretend index is a supercolumn row" approach.
An alternative would be to combine range scans, multigets, and index scans into
a single api,
multiget(rowpredicate, columnpredicate)*
rowpredicate would then be one of
- named keys [current multiget]
- key range [current get_range_slices]
- column comparisons [index scan]
This unifies the concept of "get a bunch of rows at once" nicely.
*open to a different method name if we can come up with one that doesn't suck.
> Secondary indices for column families
> -------------------------------------
>
> Key: CASSANDRA-749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-749
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.8
>
> Attachments: 0001-simple-secondary-indices.patch,
> views-discussion-2.txt, views-discussion.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
