[
https://issues.apache.org/jira/browse/CASSANDRA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277701#comment-15277701
]
Alex Petrov commented on CASSANDRA-9842:
----------------------------------------
I've taken another look on my patch yesterday and made yet another change:
isolated both code paths (for {{executeWithCondition}} and via
{{executeInternalWithCondition}} within {{ModificationStatement}}) as previous
version would've generated more garbage by creating an empty CF twice. I've ran
the tests, too.
There's also a discussion on whether or not we need dtests for that.
Technically, I could convert dtests into unit tests with `net`. Are there any
preferences about such things?
> Inconsistent behavior for '= null' conditions on static columns
> ---------------------------------------------------------------
>
> Key: CASSANDRA-9842
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9842
> Project: Cassandra
> Issue Type: Bug
> Environment: cassandra-2.1.8 on Ubuntu 15.04
> Reporter: Chandra Sekar
> Assignee: Alex Petrov
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> 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.
> h3. Table Definition
> {code}
> create table txtable(pcol bigint, ccol bigint, scol bigint static, ncol text,
> primary key((pcol), ccol));
> {code}
> h3. Inserting row in non-existent partition and updating static column in one
> LWT
> {code}
> 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
> {code}
> h3. Creating partition before LWT
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
