[ https://issues.apache.org/jira/browse/CASSANDRA-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942250#comment-13942250 ]
Bill Mitchell commented on CASSANDRA-6826: ------------------------------------------ No doubt. At the moment, though, the test case is embedded in a full application, as I mentioned to Joshua (CASSANDRA-6736). Stripping that application down so that the test case did not carry with it so much proprietary code is a couple of days of work, and I'm not sure when I will get to it. Even worse, when I first encountered this problem, it appeared only in a maven remove clean install of the whole project and not when the test case was run by itself. This last week, though, it would intermittently appear and disappear when I repeated the test unchanged, without doing the maven complete build. So it may be that a reduced version, when I have a chance to strip it down, will show the same anomaly. > 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)