[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850583#action_12850583
]
Stu Hood commented on CASSANDRA-749:
------------------------------------
Thinking about this more, ANY range we allow is basically unbounded, because
the distance between A and B may be billions of rows.
Instead of disallowing them, I think the approach that get_range_slices takes
for unbounded ranges (http://wiki.apache.org/cassandra/FAQ#range_ghosts) is
reasonable: it bounds the time that can be spent on a specific query, because a
query will return null rows rather than doing an unending scan.
It's not ideal, because a user will probably be tempted to write a loop that
pages through the null rows, but it will be a clear anti-pattern, because we
can tell users: "if you're thinking about paging through the results from
multiget, then you should probably be using a view instead.".
> 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.
