cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-5485) Cannot set varchar column to null when using cql3/thrift and prepared statements
Date Wed, 17 Apr 2013 21:05:17 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-5485.
------------------------------------------

    Resolution: Won't Fix

Unfortunately, you are right about Thrift and nulls in lists. So consider null support in
prepared statements a native-proto-only feature.
                
> Cannot set varchar column to null when using cql3/thrift and prepared statements
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5485
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5485
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2.4
>            Reporter: Ondřej Černoš
>
> We use cql3 over thrift (there is no native driver for Erlang now) and prepared statements.
There is no way to set null to a varchar column in insert statement created from prepared
statement (as Thrift doesn't support null representation afaik). Empty byte array (empty binary
in Erlang) is translated to empty string.
> There are two workarounds for this:
> * don't use prepared statements
> * pass empty strings to null columns and delete these columns afterwards in a batch
> Both are inferior solutions however.

--
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