Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 18 Jun 2013 13:47:20 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12653075.1371402418721.132307.1371563240147@arcas>
In-Reply-To: <JIRA.12653075.1371402418721@arcas>
References: <JIRA.12653075.1371402418721@arcas>
Subject: [jira] [Commented] (CASSANDRA-5648) Cassandra: Insert of null value
 not possible with CQL3?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686722#comment-13686722 ] 

Aleksey Yeschenko commented on CASSANDRA-5648:
----------------------------------------------

(row markers are what makes it possible for non-compact)
                
> 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
>          Components: API
>    Affects Versions: 1.2.0
>            Reporter: Tobias Schlottke
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.6
>
>
> 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.
> Inserting an empty String works fine, but this seems a bit bloated.
> 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