cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-3783) Add 'null' support to CQL 3.0
Date Wed, 25 Jan 2012 18:49:41 GMT
Add 'null' support to CQL 3.0

                 Key: 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:
CREATE TABLE connections (
   userid int,
   ip text,
   port int,
   protocol text,
   time timestamp,
   PRIMARY KEY (userid, ip, port, protocol)
you can insert
INSERT INTO connections (userid, ip, port, time) VALUES (2, '', 80, 123456789);

You cannot however select that column specifically (i.e, without selecting column (2, '',
80, 'http') for instance).
This ticket proposes to allow that though 'null', i.e. to allow
SELECT * FROM connections WHERE userid = 2 AND ip = '' AND port = 80 AND protocol
= null;

It would then also make sense to support:
INSERT INTO connections (userid, ip, port, protocol, time) VALUES (2, '', 80, null,
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:!default.jspa
For more information on JIRA, see:


View raw message