On Wed, Sep 25, 2013 at 5:00 AM, Petter von Dolwitz (Hem) <
petter.von.dolw...@gmail.com> wrote:
> I am generating the CSV file by other means than the COPY ... TO command
> and I thought that the NULL option did not apply to the COPY ... FROM
> command but, as it turns out, it does! This solved m
escribing the problem correctly. I'm sorry for this. This is
>>> the situation:
>>>
>>> 1. I'm populating the DB with the java-driver (INSERT INTO...). Some
>>> fields that are part of the primary key is *empty strings*. This works fine.
>>> 2. I&
art of the primary key is *empty strings*. This works fine.
>> 2. I'm trying to populate the DB from a CSV (COPY ... FROM) using cqlsh.
>> Some fields that are part of the primary key is *empty strings*. This
>> scenario gives me the "Bad Request: Invalid null value for
r (INSERT INTO...). Some
> fields that are part of the primary key is *empty strings*. This works fine.
> 2. I'm trying to populate the DB from a CSV (COPY ... FROM) using cqlsh.
> Some fields that are part of the primary key is *empty strings*. This
> scenario gives me the "Bad
rom a CSV (COPY ... FROM) using cqlsh.
Some fields that are part of the primary key is *empty strings*. This
scenario gives me the "Bad Request: Invalid null value for clustering key
part {field_name}" message. Seems like empty strings are treated as NULL
when using the COPY .. FROM comman
> Is it not permitted to have null values in a field that is part a primary
> key?
>
It's not.
> This seems to be ok when using the java-driver
>
Are you sure? Because that would qualify as a bug (in the sense that it's
not supported by C* so there is not reason why this would work with any
dri
I'm trying to import some rows to a table using the COPY command. I have a
PRIMARY KEY that is built up from many fields. During the import I get
Bad Request: Invalid null value for clustering key part {field_name}
Is it not permitted to have null values in a field that is part a primar
