cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12420) Duplicated Key in IN clause with a small fetch size will run forever
Date Tue, 27 Sep 2016 16:56:22 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tyler Hobbs updated CASSANDRA-12420:
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.1.x)
                   2.1.16
           Status: Resolved  (was: Patch Available)

Thank you, committed with the nits fixed to 2.1 as {{cdd535fcac4ba79bb371e8373c6504d9e3978853}}
and merged to 2.2 with {{-s ours}}.

> 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.16
>
>         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)

Mime
View raw message