You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2012/05/05 16:55:55 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=13268977#comment-13268977 ]
Pavel Yaskevich commented on CASSANDRA-3771:
--------------------------------------------
I think we should a test for this one, at least a grammar test...
And two minor things:
- Relation(ColumnIdentifier entity, String type, Term value, boolean onToken) constructor should pass "onToken" to "this" call instead of "true".
- there is typo in IRE of getAsToken method - "literall" show be changed to "literal" :)
> 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
> Assignee: Sylvain Lebresne
> Priority: Minor
> 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