[
https://issues.apache.org/jira/browse/CASSANDRA-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-3771:
----------------------------------------
Attachment: 3771.txt
So I agree that for pagination though large queries, some automatic paging will
be a better solution most of the time. However I think there is probably cases
where this won't work. For instance if you want to store the keys on a given
replica (for which you know the token ranges), or if you want to write a job
going through all your data and want to be able to not restart from the
beginning on some failure and maybe you don't want to go full map-reduce on it.
Anyway, not pretending those are very common, but I think there still is value
to exposing that token() function. So attached patch to do just that. It allows
to write either "token(k) = '1290845903242'" or "token(k) = token('some
value')".
> Allow paging through non-ordered partitioner results in CQL3
> ------------------------------------------------------------
>
> Key: CASSANDRA-3771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3771
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
> Affects Versions: 1.1.0
> Reporter: Jonathan Ellis
> Labels: cql
> Fix For: 1.1.1
>
> Attachments: 3771.txt
>
>
> CQL < 3 silently turns a "key >= X" into "token(key) >= token(X)". This is
> not what users will expect, since many of the rows returned will not in fact
> satisfy the requested key inequality. We should add syntax that makes the
> difference between keys and tokens explicit, possibly with a token()
> "function" as imagined here.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
