[
https://issues.apache.org/jira/browse/CASSANDRA-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943037#comment-13943037
]
Bill Mitchell commented on CASSANDRA-6826:
------------------------------------------
It is worth noting that, when I first reported this problem, the difference
between the two expected and actual number of rows returned was 1413, a rather
odd number. So far, on 2.0.6, I have seen differences that are always a
multiple of 10,000, matching the behavior in CASSANDRA-6825. So it may indeed
be, as Sylvain suggested, that CASSANDRA-6748 fixed one problem, that I was
seeing when I first reported this, but that the one test was hitting two
problems, depending on timing and other issues, and now only CASSANDRA-6825
remains.
> Query returns different number of results depending on fetchsize
> ----------------------------------------------------------------
>
> Key: CASSANDRA-6826
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6826
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: quad-core Windows 7 x64, single node cluster
> Cassandra 2.0.5
> Reporter: Bill Mitchell
> Assignee: Sylvain Lebresne
>
> I issue a query across the set of partitioned wide rows for one logical row,
> where s, l, and partition specify the composite primary key for the row:
> SELECT ec, ea, rd FROM sr WHERE s = ? and partition IN ? and l = ? ALLOW
> FILTERING;
> If I set fetchSize to only 1000 when the Cluster is configured, the query
> sometimes does not return all the results. In the particular case I am
> chasing, it returns a total of 98586 rows. If I increase the fetchsize to
> 100000, all the 99999 actual rows are returned. This suggests there is some
> problem with fetchsize re-establishing the position on the next segment of
> the result set, at least when multiple partitions are being accessed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
