cassandra-commits mailing list archives

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

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

Thorsten von Eicken commented on CASSANDRA-3771:
------------------------------------------------

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!

I must say I don't like the statement that paging can be resolved at the transport level.
If the client is just stashing the result in memory, maybe, but in the code I write the client
operates on each batch of results it gets. That can take time and the server would somehow
have to flow-control what it's fetching as the client consumes little by little at the transport
level. I hope there no timeout on the consumption, right? Processing each batch can also require
additional queries, which now requires new connections, etc. Doesn't seem like a clean path,
but maybe you have some tricks in mind.

                
> 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