[jira] [Updated] (CASSANDRA-12060) Different failure format for failed LWT between 2.x and 3.x
[ https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-12060: Status: Patch Available (was: Open) > 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 >Assignee: 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.- (striked > through since same happens on pre-[CASSANDRA-9842] code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12060) Different failure format for failed LWT between 2.x and 3.x
[ https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-12060: Description: 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.- (striked through since same happens on pre-[CASSANDRA-9842] code. was: 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. > 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.- (striked > through since same happens on pre-[CASSANDRA-9842] code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12060) Different failure format for failed LWT between 2.x and 3.x
[ https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-12060: Description: 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. was: 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}} and non-existing rows. > 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)
[jira] [Updated] (CASSANDRA-12060) Different failure format for failed LWT between 2.x and 3.x
[ https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-12060: Description: 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}} and non-existing rows. was: 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]. > 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}} and non-existing rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12060) Different failure format for failed LWT between 2.x and 3.x
[ https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-12060: Description: 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]. was: 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} > 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]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)