[
https://issues.apache.org/jira/browse/CASSANDRA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012396#comment-14012396
]
Sylvain Lebresne commented on CASSANDRA-4415:
---------------------------------------------
Your understanding is wrong and it's not the proper place for that kind of user
question: you should use the cassandra-user mailing list. This ticket
absolutely does not guarantee no timeout for any query. It only allow *some*
queries that return a lot of data to be a lot less likely to timeout. Assuming
you do use paging of course (typically cqlsh does *not* page queries currently).
> 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 beta 1
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
