Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Feb 2017 09:59:41 +0000 (UTC)
From: "Benjamin Lerer (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13037694.1485350073000.14722.1486461581805@Atlassian.JIRA>
In-Reply-To: <JIRA.13037694.1485350073000@Atlassian.JIRA>
References: <JIRA.13037694.1485350073000@Atlassian.JIRA> <JIRA.13037694.1485350073117@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CASSANDRA-13152) UPDATE on counter columns with
 empty list as argument in IN disables cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Feb 2017 09:59:47 -0000


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

Benjamin Lerer updated CASSANDRA-13152:
---------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                       (was: 3.0.x)
                       (was: 3.x)
                   4.0
                   3.11.0
                   3.0.11
           Status: Resolved  (was: Ready to Commit)

Committed into 3.0 at fb606dd41c9f14324749efc1344421237c36a6db and merged into 3.11 and trunk

> UPDATE on counter columns with empty list as argument in IN disables cluster
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13152
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13152
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Linux Ubuntu 16
> 3 Virtual machines
>            Reporter: jorge collinet
>            Assignee: Benjamin Lerer
>             Fix For: 3.0.11, 3.11.0, 4.0
>
>
> On a 3 node cluster
> with this table (replication factor of 2):
> {code}
> CREATE TABLE tracking.item_items_rec_history (
> 	reference_id bigint,
> 	country text,
> 	portal text,
> 	app_name text,
> 	recommended_id bigint,
> 	counter counter,
> 	PRIMARY KEY (reference_id, country, portal, app_name, recommended_id)
> );
> {code}
> If I execute 
> {code}
> UPDATE user_items_rec_history 
> SET counter = counter + 1 
> WHERE reference_id = 1 AND country = '' AND portal = '' AND app_name = '' AND recommended_id IN ();
> {code}
> Take note that the IN is empty
> The cluster starts to malfunction and responds a lot of timeouts to any query.
> After resetting some of the nodes, the cluster starts to function normally again.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)