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 2017/01/25 14:42:27 UTC
[jira] [Assigned] (CASSANDRA-13152) UPDATE on counter columns with
empty list as argument in IN disables cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Lerer reassigned CASSANDRA-13152:
------------------------------------------
Assignee: Benjamin Lerer
> 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.3
>
>
> On a 3 node cluster
> with this table (replication factor of 2):
> 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)
> );
> If I execute
> UPDATE user_items_rec_history
> SET counter = counter + 1
> WHERE reference_id = 1 AND country = '' AND portal = '' AND app_name = '' AND recommended_id IN ();
> 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.4#6332)