[
https://issues.apache.org/jira/browse/CASSANDRA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919908#action_12919908
]
Jonathan Ellis commented on CASSANDRA-1599:
-------------------------------------------
This is sort of along the lines of what I was thinking, although I think just
adding a ColumnFamily index type would be adequate to distinguish it.
{code}
column families which are sorted by the index value
{code}
This is the hard part, I am having trouble wrapping my mind around a scheme
that allows both different sort orders in different CFs and always routes
things correctly by node token no matter which CF you are talking about.
{code}
which are queried using get_range_slices
{code}
As suggested by "adding a CF index type" I think using the same index query api
makes more sense.
> Add sort/order support for secondary indexing
> ---------------------------------------------
>
> Key: CASSANDRA-1599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1599
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Reporter: Todd Nine
> Fix For: 0.8
>
>
> 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.
