cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Schlottke (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-5648) Cassandra: Insert of null value not possible with CQL3?
Date Sun, 16 Jun 2013 17:07:21 GMT
Tobias Schlottke created CASSANDRA-5648:
-------------------------------------------

             Summary: Cassandra: Insert of null value not possible with CQL3?
                 Key: CASSANDRA-5648
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5648
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.5
            Reporter: Tobias Schlottke


Hi there,

I'm trying to migrate a project from thrift to cql3/java driver and I'm experiencing a strange
problem.

Schema:
{code}
CREATE TABLE foo (
  key ascii,
  column1 ascii,
  foo ascii,
  PRIMARY KEY (key, column1)
) WITH COMPACT STORAGE;
{code}

The table just consists of a primary key and a value, sometimes all the information lies in
the key though, so the value is not needed.
Through the thrift interface, it just works fine to leave out "foo".
Executing this query:
{code}
INSERT INTO foo(key, column1) VALUES ('test', 'test2');
{code}

Fails with
"Bad Request: Missing mandatory column foo"

though.

Explicitly inserting "null" as a value does not store the column / deletes the old one with
a "null" value inserted through thrift.

Is this intended to (not) work this way?

Best,

Tobias







--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message