[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844872#action_12844872
]
Jonathan Ellis commented on CASSANDRA-749:
------------------------------------------
> This is why we have load balancing.
Load balancing doesn't help if you are indexing something with less potential
values than you have nodes in the cluster. At the extreme, say booleans, it's
probably not worth indexing vs just doing full scans. But if you have 100s of
nodes then not being able to usefully index something woth 20 or 50 or 100
values kinda sucks.
> We could easily have a built in "SecondaryIndex" view class that uses a
> matching column name/value as the row key in the view.
That would probably work, although I don't want to fall into the trap of
overgeneralizing because it's sexy. Nobody wants to write static java code to
define a view, I can promise you that. :)
> Is the intention that the indexes would be used to speed up
> predicates/filters in get_range_slices
No, it's to add a different kind of predicate: "give me these columns [existing
functionality] from rows that match this index condition [new functionality]."
> 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.
