[
https://issues.apache.org/jira/browse/CASSANDRA-11963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318823#comment-15318823
]
Adam Holmberg commented on CASSANDRA-11963:
-------------------------------------------
This is not a huge concern to me (scans like this can be broken up using
token()), but just for the sake of discussion, is there any reason
PagingState.remaining could just be reset for each paged of the query? That
seems to be the behavior in 3.0. It wouldn't require any change in format, and
there was never any client contract on the semantics of those parts. Most
clients of which I'm aware treat them as opaque blobs. Also, I don't think that
changes the PagingState semantics from a server cursor perspective -- it just
removes the limitation.
> Paged queries limited to Integer.MAX_VALUE total rows
> -----------------------------------------------------
>
> Key: CASSANDRA-11963
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11963
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Adam Holmberg
> Priority: Minor
> Fix For: 2.1.x, 2.2.x
>
>
> Paged queries are artificially limited to Integer.MAX_INT rows in total. This
> appears to be related to PagingState.remaining, which decrements
> monotonically as pages are consumed.
> I don't think this is intentional behavior, and haven't found any mention of
> it in the docs.
> Issue observed in latest 2.1 and 2.2 releases. Does not occur in 3.x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
