Problems using secondary index with IN keyword

Hi, I have a table that (in simplified version) looks like this: CREATE TABLE mytable ( a varchar, b varchar, c varchar d timstamp, e varchar, PRIMARY KEY (a, b, c, d) ); CREATE INDEX mytable_c_idx ON mytable ( c ); After populating I execute: SELECT * FROM mytable WHERE

Re: Problems using secondary index with IN keyword

Algermissen jan.algermis...@nordsc.com Petter, On 24.10.2013, at 14:38, Petter von Dolwitz (Hem) petter.von.dolw...@gmail.com wrote: Hi, I have a table that (in simplified version) looks like this: CREATE TABLE mytable ( a varchar, b varchar, c varchar d timstamp

Re: Problems using secondary index with IN keyword

and if the behaviour I am experiencing is a problem with my design, a problem with the data or a problem with Cassandra. /Petter Den torsdagen den 24:e oktober 2013 skrev Jan Algermissen: On 24.10.2013, at 15:13, Petter von Dolwitz (Hem) petter.von.dolw...@gmail.com javascript:; wrote: You

COPY command times out

Hi, I'm trying to import CSV data using the COPY ... FROM command. After importing 10% of my 2.5 GB csv file the operation aborts with the message: Request did not complete within rpc_timeout. Aborting import at record #504631 (line 504632). Previously-inserted values still present. There are

Re: COPY command times out

von Dolwitz (Hem) petter.von.dolw...@gmail.com wrote: Hi, I'm trying to import CSV data using the COPY ... FROM command. After importing 10% of my 2.5 GB csv file the operation aborts with the message: Request did not complete within rpc_timeout. Aborting import at record #504631 (line

Re: Bad Request: Invalid null value for clustering key part

it in your csv and that your are sure nothing that's not supposed to be null will be represented by the string 'null'). -- Sylvain On Tue, Sep 24, 2013 at 9:41 AM, Petter von Dolwitz (Hem) petter.von.dolw...@gmail.com wrote: Hi Sylvain, I was not describing the problem correctly. I'm

Re: Bad Request: Invalid null value for clustering key part

, Petter 2013/9/25 Petter von Dolwitz (Hem) petter.von.dolw...@gmail.com 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 my problem

Bad Request: Invalid null value for clustering key part

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 primary key?

Re: Cannot get secondary indexes on fields in compound primary key to work (Cassandra 2.0.0)

For the record: https://issues.apache.org/jira/browse/CASSANDRA-5975 (2.0.1) resolved this issue for me. 2013/9/8 Petter von Dolwitz (Hem) petter.von.dolw...@gmail.com Thank you for you reply. I will look into this. I cannot not get my head around why the scenario I am describing does

Re: Cannot get secondary indexes on fields in compound primary key to work (Cassandra 2.0.0)

://www.datastax.com/dev/blog/cql3-for-cassandra-experts 2013/9/6 Robert Coli rc...@eventbrite.com On Fri, Sep 6, 2013 at 6:18 AM, Petter von Dolwitz (Hem) petter.von.dolw...@gmail.com wrote: I am struggling with getting secondary indexes to work. I have created secondary indexes on some fields

Cannot get secondary indexes on fields in compound primary key to work (Cassandra 2.0.0)

I am struggling with getting secondary indexes to work. I have created secondary indexes on some fields that are part of the compound primary key but only one of the indexes seems to work (the one set on the field 'e' on the table definition below). Using any other secondary index in a where