You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org> on 2012/01/23 18:12:40 UTC

[jira] [Commented] (CASSANDRA-3771) Allow paging through non-ordered partitioner results in CQL3

    [ https://issues.apache.org/jira/browse/CASSANDRA-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191260#comment-13191260 ] 

Jonathan Ellis commented on CASSANDRA-3771:
-------------------------------------------

As an alternative, since the only reason to do this with non-[B]OPP is to paginate through a large query, our hypothetical native CQL transport supporting streaming may make this unnecessary.

Until/unless we want to introduce a CqlInputFormat again...
                
> 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: New Feature
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Jonathan Ellis
>              Labels: cql
>             Fix For: 1.1
>
>
> 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