[
https://issues.apache.org/jira/browse/CASSANDRA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919687#action_12919687
]
Todd Nine edited comment on CASSANDRA-1599 at 10/10/10 7:13 PM:
----------------------------------------------------------------
Consider a query similar to the following.
email == 'b...@gmail.com' && (lastlogindate > today - 5 days || newmessagedate
> today -1 day).
Which start key do I advance, one, both? As a client I would have to iterate
over every field in the expression tree to determine what my start key should
be for two index clauses. While this is not impossible, this becomes very
complex for large boolean operand trees. As a user, this functionality would
provide a clean interface that abstracts the user from the need to perform an
analysis of the previous result set and "diff" it with the expression tree
provided. I'm not saying it's an absolute must have, but it would certainly
provide a lot of appeal to users that are utilizing Cassandra as an eventually
consistent storage mechanism for web based applications once union and
intersections are implemented in Cassandra.
was (Author: tnine):
Consider a query similar to the following.
email == 'b...@gmail.com' && (lastlogindate > today - 5 days || newmessagedate
> today -1 day).
Which start key do I advance, one, both? As a client I would have to iterate
over every field in the expression tree to determine what my start key should
be for two index clauses. While this is not impossible, this becomes very
complex for large boolean operand trees. As a user, this functionality would
provide a clean interface that abstracts the user from the need to perform an
analysis of the previous result set and "diff" it with the expression tree
provided. I'm not saying it's an absolute must have, but it would certainly
provide a lot of appeal to users that are utilizing Cassandra as an eventually
consistent storage mechanism for web based applications once union and
intersections are implemented server side.
> Add paging support for secondary indexing
> -----------------------------------------
>
> Key: CASSANDRA-1599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1599
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Todd Nine
> Fix For: 0.7.0
>
>
> For a lot of users paging is a standard use case on many web applications.
> It would be nice to allow paging as part of a Boolean Expression.
> Page -> start index
> -> end index
> -> page timestamp
> -> Sort Order
> When sorting, is it possible to sort both ASC and DESC?
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
