[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-tabpanelfocusedCommentId=13269510#comment-13269510 ] Pavel Yaskevich commented on CASSANDRA-3771: +1 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-v2.txt, 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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=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
