Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1AB66200B32 for ; Thu, 23 Jun 2016 15:13:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 19034160A59; Thu, 23 Jun 2016 13:13:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 607F5160A58 for ; Thu, 23 Jun 2016 15:13:17 +0200 (CEST) Received: (qmail 23797 invoked by uid 500); 23 Jun 2016 13:13:16 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 23629 invoked by uid 99); 23 Jun 2016 13:13:16 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2016 13:13:16 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2BC6C2C14F8 for ; Thu, 23 Jun 2016 13:13:16 +0000 (UTC) Date: Thu, 23 Jun 2016 13:13:16 +0000 (UTC) From: "Alex Petrov (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-12060) Different failure format for failed LWT between 2.x and 3.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 23 Jun 2016 13:13:18 -0000 [ 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)