You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2016/09/26 11:11:20 UTC
[jira] [Commented] (CASSANDRA-12420) Duplicated Key in IN clause
with a small fetch size will run forever
[ https://issues.apache.org/jira/browse/CASSANDRA-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15522751#comment-15522751 ]
Benjamin Lerer commented on CASSANDRA-12420:
--------------------------------------------
Two minor nits:
* The {{HAS_LOGGED_WARNING_FOR_IN_RESTRICTION_WITH_DUPLICATES}} static variable in {{SelectStatement}} is not used anymore and can be removed.
* The {{assertRowsIgnoringOrder}}, {{assertRowsIgnoringOrderAndExtra}} and {{assertRowsIgnoringOrderInternal}} methods in {{CQLTester}} are not used and should be removed from the patch.
> Duplicated Key in IN clause with a small fetch size will run forever
> --------------------------------------------------------------------
>
> Key: CASSANDRA-12420
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12420
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: cassandra 2.1.14, driver 2.1.7.1
> Reporter: ZhaoYang
> Assignee: Tyler Hobbs
> Labels: doc-impacting
> Fix For: 2.1.x
>
> Attachments: CASSANDRA-12420.patch
>
>
> This can be easily reproduced and fetch size is smaller than the correct number of rows.
> A table has 2 partition key, 1 clustering key, 1 column.
> > Select select = QueryBuilder.select().from("ks", "cf");
> > select.where().and(QueryBuilder.eq("a", 1));
> > select.where().and(QueryBuilder.in("b", Arrays.asList(1, 1, 1)));
> > select.setFetchSize(5);
> Now we put a distinct method in client side to eliminate the duplicated key, but it's better to fix inside Cassandra.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)