You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/04/28 09:51:16 UTC
[jira] [Resolved] (CASSANDRA-6826) Query returns different number
of results depending on fetchsize
[ https://issues.apache.org/jira/browse/CASSANDRA-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne resolved CASSANDRA-6826.
-----------------------------------------
Resolution: Fixed
Thanks for the feedback. Closing as dup of CASSANDRA-6825 then (for the driver issue, I saw your issue and will look it up there).
> 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)