[ https://issues.apache.org/jira/browse/CASSANDRA-12426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415269#comment-15415269 ]
Alex Petrov commented on CASSANDRA-12426: ----------------------------------------- So the behaviour is correct: after insert, we can not differentiate between partition that was inserted with null and that was never existing? Should it be same for 3.x, or it should return {{'a', 'b', null}} in 3.0? > Writing a null value into a dense table results into a no-op > ------------------------------------------------------------- > > Key: CASSANDRA-12426 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12426 > Project: Cassandra > Issue Type: Bug > Reporter: Alex Petrov > > Making an insert into the dense table doesn't seem to create a live partition: > {code} > cqlsh> CREATE KEYSPACE test WITH replication = {'class': > 'NetworkTopologyStrategy', 'datacenter1': '1' }; > cqlsh> use test ; > cqlsh:test> CREATE TABLE a (partition text, key text, owner text, PRIMARY KEY > (partition, key) ) WITH COMPACT STORAGE; > cqlsh:test> INSERT INTO a (partition, key, owner) VALUES ('a', 'b', null); > cqlsh:test> select * from a; > partition | key | owner > -----------+-----+-------- > {code} > (same behaviour on 2.2) -- This message was sent by Atlassian JIRA (v6.3.4#6332)