[
https://issues.apache.org/jira/browse/CASSANDRA-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598813#comment-16598813
]
Sylvain Lebresne commented on CASSANDRA-14683:
----------------------------------------------
No mystery here, the paging state uses a 4-byte integer (currently interpreted
signed) to encode the limit of rows yet to return. A query (paged or not) can
thus currently not return more than ~2 billion rows. That's definitively an
issue that should be fixed, and it's not really hard to do so in principle (the
paging state should use a 8-byte long), but it will require a native protocol
change. Translation, this cannot be fixed in current versions, and given the
freeze date for 4.0, this won't be fixed there either.
So short term, you will have to complicate your dumping code a bit I'm afraid
to use more than one query to do this.
> Pagestate is null after 2^31 rows
> ---------------------------------
>
> Key: CASSANDRA-14683
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14683
> Project: Cassandra
> Issue Type: Bug
> Reporter: Abhishek
> Priority: Major
>
> I am using the nodejs driver to take a dump of my table via
> [pagination|http://datastax.github.io/nodejs-driver/features/paging/#manual-paging]
> for a simple query.
> My query is \{{select * from mytable}}
> The table has close to 4 billion rows and cassandra stops returning results
> exactly after 2147483647 rows. The pagestate is not returned after this.
> Cassandra version - 3.0.9
> Nodejs cassandra driver version - 3.5.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
