cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3771) Allow paging through non-ordered partitioner results in CQL3
Date Tue, 24 Jan 2012 13:22:40 GMT

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

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

bq. As someone who uses key >= X with random partitioner all the time to walk through results
I'm concerned about this ticket. I hope you guys are not considering releasing 1.1 without
a solution!

This is one reason we're retaining CQL2 as an option, unchanged from 1.0.
                
> 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

        

Mime
View raw message