Add 'null' support to CQL 3.0 ----------------------------- Key: CASSANDRA-3783 URL: https://issues.apache.org/jira/browse/CASSANDRA-3783 Project: Cassandra Issue Type: Sub-task Reporter: Sylvain Lebresne Priority: Minor
Dense composite supports adding records where only a prefix of all the component specifying the key is defined. In other words, with: {noformat} CREATE TABLE connections ( userid int, ip text, port int, protocol text, time timestamp, PRIMARY KEY (userid, ip, port, protocol) ) WITH COMPACT STORAGE {noformat} you can insert {noformat} INSERT INTO connections (userid, ip, port, time) VALUES (2, '192.168.0.1', 80, 123456789); {noformat} 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 {noformat} SELECT * FROM connections WHERE userid = 2 AND ip = '192.168.0.1' AND port = 80 AND protocol = null; {noformat} It would then also make sense to support: {noformat} INSERT INTO connections (userid, ip, port, protocol, time) VALUES (2, '192.168.0.1', 80, null, 123456789); {noformat} as an equivalent to the insert query above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira