[
https://issues.apache.org/jira/browse/CASSANDRA-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407890#comment-13407890
]
Sylvain Lebresne commented on CASSANDRA-4415:
---------------------------------------------
Yeah, I guess we haven't much choice, though I'll note that the burden of
saying when a query might lack isolation will be on the client driver
documentation. That is, we can explain that drivers will likely use query
paging for large queries which will defeats isolation, but then we'll have to
refer to said driver documentation to know exactly when paging is used and how
to control it. Unless we fix the page size to a constant, but that's a bit lame
imho.
> 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
> Reporter: Sylvain Lebresne
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
