[
https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346396#comment-15346396
]
Alex Petrov edited comment on CASSANDRA-12060 at 6/23/16 1:11 PM:
------------------------------------------------------------------
I've checked the pre-9842 behaviour (on top of [CASSANDRA-10532] alone)
{code}
[cqlsh 5.0.1 | Cassandra 2.1.14-SNAPSHOT | CQL spec 3.2.1 | Native protocol v3]
Use HELP for help.
cqlsh> CREATE KEYSPACE test WITH replication = {'class':
'NetworkTopologyStrategy', 'datacenter1': '1' };
cqlsh> USE test;
cqlsh:test> CREATE TABLE testtable (a int, b int, s1 int static, s2 int static,
v int, PRIMARY KEY (a, b));
cqlsh:test> INSERT INTO testtable (a,b,s1,s2,v) VALUES (2,2,2,null,2);
cqlsh:test> DELETE s1 FROM testtable WHERE a = 2 IF s2 IN (10,20,30);
[applied] | s2
-----------+------
False | null
{code}
{code}
[cqlsh 5.0.1 | Cassandra 3.0.7-SNAPSHOT | CQL spec 3.4.0 | Native protocol v4]
Use HELP for help.
cqlsh> CREATE KEYSPACE test WITH replication = {'class':
'NetworkTopologyStrategy', 'datacenter1': '1' };
cqlsh> USE test;
cqlsh:test> CREATE TABLE testtable (a int, b int, s1 int static, s2 int static,
v int, PRIMARY KEY (a, b));
cqlsh:test> INSERT INTO testtable (a,b,s1,s2,v) VALUES (2,2,2,null,2);
cqlsh:test> DELETE s1 FROM testtable WHERE a = 2 IF s2 IN (10,20,30);
[applied]
-----------
False
{code}
[UPDATE] (previous version of this message was due to wrong checked out commit
on {{3.0}}) So the inconsistency was there before the [CASSANDRA-9842].
was (Author: ifesdjeen):
I've checked the pre-9842 behaviour (on top of [CASSANDRA-10532] alone)
{code}
[cqlsh 5.0.1 | Cassandra 2.1.14-SNAPSHOT | CQL spec 3.2.1 | Native protocol v3]
Use HELP for help.
cqlsh> CREATE KEYSPACE test WITH replication = {'class':
'NetworkTopologyStrategy', 'datacenter1': '1' };
cqlsh> USE test;
cqlsh:test> CREATE TABLE testtable (a int, b int, s1 int static, s2 int static,
v int, PRIMARY KEY (a, b));
cqlsh:test> INSERT INTO testtable (a,b,s1,s2,v) VALUES (2,2,2,null,2);
cqlsh:test> DELETE s1 FROM testtable WHERE a = 2 IF s2 IN (10,20,30);
[applied] | s2
-----------+------
False | null
{code}
{code}
cqlsh> CREATE KEYSPACE test WITH replication = {'class':
'NetworkTopologyStrategy', 'datacenter1': '1' };
cqlsh> USE test;
cqlsh:test> CREATE TABLE testtable (a int, b int, s1 int static, s2 int static,
v int, PRIMARY KEY (a, b));
cqlsh:test> INSERT INTO testtable (a,b,s1,s2,v) VALUES (2,2,2,null,2);
cqlsh:test> DELETE s1 FROM testtable WHERE a = 2 IF s2 IN (10,20,30);
[applied] | s2
-----------+------
False | null
{code}
So there's no inconsistency before [CASSANDRA-9842].
Although it might still be worth digging into the reason behind it, since only
{3.x} behaviour changes and LWT itself is not applied consistently. If there's
just a problem with output format due to some result on {3.x}, we can just fix
that part.
> Different failure format for failed LWT between 2.x and 3.x
> -----------------------------------------------------------
>
> Key: CASSANDRA-12060
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12060
> Project: Cassandra
> Issue Type: Bug
> Reporter: Alex Petrov
>
> When executing following CQL commands:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'NetworkTopologyStrategy',
> 'datacenter1': '1' };
> USE test;
> CREATE TABLE testtable (a int, b int, s1 int static, s2 int static, v int,
> PRIMARY KEY (a, b));
> INSERT INTO testtable (a,b,s1,s2,v) VALUES (2,2,2,null,2);
> DELETE s1 FROM testtable WHERE a = 2 IF s2 IN (10,20,30);
> {code}
> The output is different between {{2.x}} and {{3.x}}:
> 2.x:
> {code}
> cqlsh:test> DELETE s1 FROM testtable WHERE a = 2 IF s2 = 5;
> [applied] | s2
> -----------+------
> False | null
> {code}
> 3.x:
> {code}
> cqlsh:test> DELETE s1 FROM testtable WHERE a = 2 IF s2 = 5;
> [applied]
> -----------
> False
> {code}
> {{2.x}} would although return same result if executed on a partition that
> does not exist at all:
> {code}
> cqlsh:test> DELETE s1 FROM testtable WHERE a = 5 IF s2 = 5;
> [applied]
> -----------
> False
> {code}
> It _might_ be related to static column LWTs, as I could not reproduce same
> behaviour with non-static column LWTs. The most recent change was
> [CASSANDRA-10532], which enabled LWT operations on static columns with
> partition keys only. Another possible relation is [CASSANDRA-9842], which
> removed distinction between {{null}} column and non-existing row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
