cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12060) Establish consistent distinction between non-existing partition and NULL value for LWTs on static columns
Date Mon, 19 Sep 2016 08:29:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502704#comment-15502704
] 

Sylvain Lebresne commented on CASSANDRA-12060:
----------------------------------------------

Thanks, this sounds good to go but there seems to have been problems with the CI runs either
not running or doing crazy things. Also, the branch as many commits adding stuffs that are
later removed so I squashed the brand to make sure we didn't missed something (which we don't
seem to have) and re-ran the tests below. Could you btw turn your dtest update into a pull
request so it's easier to merge there?

| [12060-3.0-squashed|https://github.com/pcmanus/cassandra/commits/12060-3.0-squashed] | [utests|http://cassci.datastax.com/job/pcmanus-12060-3.0-squashed-testall]
| [dtests|http://cassci.datastax.com/job/pcmanus-12060-3.0-squashed-dtest] |
| [12060-trunk-squashed|https://github.com/pcmanus/cassandra/commits/12060-trunk-squashed]
| [utests|http://cassci.datastax.com/job/pcmanus-12060-trunk-squashed-testall] | [dtests|http://cassci.datastax.com/job/pcmanus-12060-trunk-squashed-dtest]
|


> Establish consistent distinction between non-existing partition and NULL value for LWTs
on static columns
> ---------------------------------------------------------------------------------------------------------
>
>                 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)

Mime
View raw message