[jira] [Assigned] (CASSANDRA-4415) Add cursor API/auto paging to the native CQL protocol
[ https://issues.apache.org/jira/browse/CASSANDRA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko reassigned CASSANDRA-4415: Assignee: Sylvain Lebresne (was: Aleksey Yeschenko) Sorry. Misclicked (: > Add cursor API/auto paging to the native CQL protocol > - > > Key: CASSANDRA-4415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4415 > Project: Cassandra > Issue Type: New Feature >Affects Versions: 1.2.0 beta 1 >Reporter: Sylvain Lebresne >Assignee: Sylvain Lebresne > Labels: cql, protocol > Fix For: 2.0 > > > The goal here would be to use a query paging mechanism to the CQL native > protocol. Typically the client/server with that would look something like > this: > {noformat} > C sends query to S. > S sends N first rows matching the query + flag saying the response is not > complete > C requests the next N rows > S sends N next rows + flag saying whether there is more > C requests the next N rows > ... > S sends last rows + flag saying there is no more result > {noformat} > The clear goal is for user to not have to worry about limiting queries and > doing manual paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-4415) Add cursor API/auto paging to the native CQL protocol
[ https://issues.apache.org/jira/browse/CASSANDRA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko reassigned CASSANDRA-4415: Assignee: Aleksey Yeschenko (was: Sylvain Lebresne) > Add cursor API/auto paging to the native CQL protocol > - > > Key: CASSANDRA-4415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4415 > Project: Cassandra > Issue Type: New Feature >Affects Versions: 1.2.0 beta 1 >Reporter: Sylvain Lebresne >Assignee: Aleksey Yeschenko > Labels: cql, protocol > Fix For: 2.0 > > > The goal here would be to use a query paging mechanism to the CQL native > protocol. Typically the client/server with that would look something like > this: > {noformat} > C sends query to S. > S sends N first rows matching the query + flag saying the response is not > complete > C requests the next N rows > S sends N next rows + flag saying whether there is more > C requests the next N rows > ... > S sends last rows + flag saying there is no more result > {noformat} > The clear goal is for user to not have to worry about limiting queries and > doing manual paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-4415) Add cursor API/auto paging to the native CQL protocol
[ https://issues.apache.org/jira/browse/CASSANDRA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne reassigned CASSANDRA-4415: --- Assignee: Sylvain Lebresne > Add cursor API/auto paging to the native CQL protocol > - > > Key: CASSANDRA-4415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4415 > Project: Cassandra > Issue Type: New Feature >Affects Versions: 1.2.0 beta 1 >Reporter: Sylvain Lebresne >Assignee: Sylvain Lebresne > Fix For: 2.0 > > > The goal here would be to use a query paging mechanism to the CQL native > protocol. Typically the client/server with that would look something like > this: > {noformat} > C sends query to S. > S sends N first rows matching the query + flag saying the response is not > complete > C requests the next N rows > S sends N next rows + flag saying whether there is more > C requests the next N rows > ... > S sends last rows + flag saying there is no more result > {noformat} > The clear goal is for user to not have to worry about limiting queries and > doing manual paging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira