[
https://issues.apache.org/jira/browse/CASSANDRA-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853046#comment-13853046
]
Pardeep Singh commented on CASSANDRA-6511:
------------------------------------------
But wouldn't it still be better than doing it client site?
SELECT * FROM top_posts WHERE id="music" LIMIT 11; // to get the 11th row
vs
SELECT * FROM top_posts WHERE id="music" LIMIT 10, 1;
If i remember correctly, thrift api had a way to do this using slices.
> extend LIMIT to define offset, row_count
> ----------------------------------------
>
> Key: CASSANDRA-6511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6511
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Pardeep Singh
> Labels: cql3, query
>
> Currently I can to do:
> SELECT * FROM top_posts WHERE id="music" LIMIT 10;
> If it was possible to extend the LIMIT clause to:
> [LIMIT {[offset,] row_count | row_count OFFSET offset}]
> SELECT * FROM top_posts WHERE id="music" LIMIT 10, 10;
> Pagination will be possible without using clustering key with less than or
> greater than.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
