[CASSANDRA-9842] Inconsistent behavior for '= null' conditions on static columns

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.15, 2.2.7, 3.0.8, 3.8
• Component/s: Legacy/CQL

Environment

cassandra-2.1.8 on Ubuntu 15.04

• Severity: Normal
• Assignee: Alex Petrov
• Reporter: Chandra Sekar

Authors

Alex Petrov

Reviewers

Benjamin Lerer

• Created: 18/Jul/15 03:39
• Updated: 16/Apr/19 09:31
• Resolved: 21/Jun/16 14:36

Description

Both inserting a row (in a non-existent partition) and updating a static column in the same LWT fails. Creating the partition before performing the LWT works.

Table Definition

create table txtable(pcol bigint, ccol bigint, scol bigint static, ncol text, primary key((pcol), ccol));

Inserting row in non-existent partition and updating static column in one LWT

begin batch
    insert into txtable (pcol, ccol, ncol) values (1, 1, 'A');
    update txtable set scol = 1 where pcol = 1 if scol = null;
apply batch;

[applied]
-----------
     False

Creating partition before LWT

insert into txtable (pcol, scol) values (1, null) if not exists;

begin batch
    insert into txtable (pcol, ccol, ncol) values (1, 1, 'A');
    update txtable set scol = 1 where pcol = 1 if scol = null;
apply batch;

[applied]
-----------
     True

Issue Links

• depends upon: CASSANDRA-10532 Allow LWT operation on static column with only partition keys