[ https://issues.apache.org/jira/browse/CASSANDRA-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-9571: --------------------------------------- Attachment: 9571-2.0.txt Trivial patch targetting 2.0, it merges basically cleanly to 2.1 onwards with 1 tiny conflict (from 2.1 {{setHasMorePages}} is void). > Set HAS_MORE_PAGES flag when PagingState is null > ------------------------------------------------ > > Key: CASSANDRA-9571 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9571 > Project: Cassandra > Issue Type: Improvement > Reporter: Sam Tunnicliffe > Assignee: Sam Tunnicliffe > Priority: Minor > Fix For: 2.1.x, 2.0.x, 2.2.x, 3.0.x > > Attachments: 9571-2.0.txt > > > If {{ResultSet.Metadata#setHasMorePages}} is called with a null > {{PagingState}}, indicating that there are no more available results, we > should explicitly unset the {{HAS_MORE_PAGES}} flag. This can be necessary > where a custom {{QueryHandler}} implements its own {{LIMIT}} logic and wishes > to send the signal to the client that the results are exhausted before the > storage engine would normally do so. -- This message was sent by Atlassian JIRA (v6.3.4#6332)