Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 24 Oct 2016 13:26:58 +0000 (UTC)
From: "Alex Petrov (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13014411.1477085377000.66775.1477315618566@Atlassian.JIRA>
In-Reply-To: <JIRA.13014411.1477085377000@Atlassian.JIRA>
References: <JIRA.13014411.1477085377000@Atlassian.JIRA> <JIRA.13014411.1477085377121@arcas>
Subject: [jira] [Assigned] (CASSANDRA-12829) DELETE query with an empty IN
 clause can delete more than expected
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 24 Oct 2016 13:27:00 -0000


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

Alex Petrov reassigned CASSANDRA-12829:
---------------------------------------

    Assignee: Alex Petrov

> DELETE query with an empty IN clause can delete more than expected
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-12829
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12829
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>         Environment: Arch Linux x64, kernel 4.7.6, Cassandra 3.9 downloaded from the website
>            Reporter: Jason T. Bradshaw
>            Assignee: Alex Petrov
>
> When deleting from a table with a certain structure and using an *in* clause with an empty list, the *in* clause with an empty list can be ignored, resulting in deleting more than is expected.
> *Setup:*
> {code}
> cqlsh> create table test (a text, b text, id uuid, primary key ((a, b), id));
> cqlsh> insert into test (a, b, id) values ('a', 'b', 00000000-0000-0000-0000-000000000000);
> cqlsh> insert into test (a, b, id) values ('b', 'c', 00000000-0000-0000-0000-000000000000);
> cqlsh> insert into test (a, b, id) values ('a', 'c', 00000000-0000-0000-0000-000000000000);
> cqlsh> select * from test;
>  a | b | id
> ---+---+--------------------------------------
>  a | c | 00000000-0000-0000-0000-000000000000
>  b | c | 00000000-0000-0000-0000-000000000000
>  a | b | 00000000-0000-0000-0000-000000000000
> (3 rows)
> {code}
> *Expected:*
> {code}
> cqlsh> delete from test where a = 'a' and b in ('a', 'b', 'c') and id in ();
> cqlsh> select * from test;
>  a | b | id
> ---+---+--------------------------------------
>  a | c | 00000000-0000-0000-0000-000000000000
>  b | c | 00000000-0000-0000-0000-000000000000
>  a | b | 00000000-0000-0000-0000-000000000000
> (3 rows)
> {code}
> *Actual:*
> {code}
> cqlsh> delete from test where a = 'a' and b in ('a', 'b', 'c') and id in ();
> cqlsh> select * from test;
>  a | b | id
> ---+---+--------------------------------------
>  b | c | 00000000-0000-0000-0000-000000000000
> (1 rows)
> {code}
> Instead of deleting nothing, as the final empty *in* clause would imply, it instead deletes everything that matches the first two clauses, acting as if the following query had been issued instead:
> {code}
> cqlsh> delete from test where a = 'a' and b in ('a', 'b', 'c');
> {code}
> This seems to be related to the presence of a tuple clustering key, as I could not reproduce it without one.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)