[CASSANDRA-3783] Add 'null' support to CQL 3.0

• Type: Sub-task
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.4
• Component/s: Legacy/CQL
• Labels: cql3
• Assignee: Michał Michalski
• Reporter: Sylvain Lebresne

Authors

Michał Michalski

Reviewers

Aleksey Yeschenko

• Created: 25/Jan/12 18:49
• Updated: 16/Apr/19 09:32
• Resolved: 04/Apr/13 17:16

Description

Dense composite supports adding records where only a prefix of all the component specifying the key is defined. In other words, with:

CREATE TABLE connections (
   userid int,
   ip text,
   port int,
   protocol text,
   time timestamp,
   PRIMARY KEY (userid, ip, port, protocol)
) WITH COMPACT STORAGE

you can insert

INSERT INTO connections (userid, ip, port, time) VALUES (2, '192.168.0.1', 80, 123456789);

You cannot however select that column specifically (i.e, without selecting column (2, '192.168.0.1', 80, 'http') for instance).
This ticket proposes to allow that though 'null', i.e. to allow

SELECT * FROM connections WHERE userid = 2 AND ip = '192.168.0.1' AND port = 80 AND protocol = null;

It would then also make sense to support:

INSERT INTO connections (userid, ip, port, protocol, time) VALUES (2, '192.168.0.1', 80, null, 123456789);

as an equivalent to the insert query above.

Issue Links

• is duplicated by: CASSANDRA-5416 Support CQL map and list deletes within an update statement