[
https://issues.apache.org/jira/browse/CASSANDRA-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252204#comment-14252204
]
Tyler Hobbs commented on CASSANDRA-8087:
----------------------------------------
bq. We do update the slice count in SliceQueryPager but not in
RangeSliceQueryPager. Not sure why though, and I think that can make us fetch
more than we should so it might be kind of a bug.
I think the current behavior is okay (although it's hard to follow).
AbstractQueryPager updates the page size (taking "remaining" into account)
before calling queryNextPage(). The new page size is used as the limit for the
new PagedRangeCommand. It then gets passed to CFS.makeExtendedFilter(), which
makes an ExtendedFilter with maxResults as the limit. When countCQL3Rows is
true, this is used as the column (cql3 row) limit.
> Multiple non-DISTINCT rows returned when page_size set
> ------------------------------------------------------
>
> Key: CASSANDRA-8087
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8087
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Adam Holmberg
> Assignee: Tyler Hobbs
> Priority: Minor
> Fix For: 2.0.12
>
> Attachments: 8087-2.0.txt
>
>
> Using the following statements to reproduce:
> {code}
> CREATE TABLE test (
> k int,
> p int,
> s int static,
> PRIMARY KEY (k, p)
> );
> INSERT INTO test (k, p) VALUES (1, 1);
> INSERT INTO test (k, p) VALUES (1, 2);
> SELECT DISTINCT k, s FROM test ;
> {code}
> Native clients that set result_page_size in the query message receive
> multiple non-distinct rows back (one per clustered value p in row k).
> This is only reproduced on 2.0.10. Does not appear in 2.1.0
> It does not appear in cqlsh for 2.0.10 because thrift.
> See https://datastax-oss.atlassian.net/browse/PYTHON-164 for background
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
