Re: Trying to identify the problem with CQL ...

2013-03-05 Thread Sylvain Lebresne
You do seem to be experiencing a problem indeed, but hard to say what it is from just this (could be anything from a configuration problem, a cassandra bug or a bug in the java driver). But since you seem to be able to reproduce easily, if you can provide a script that reproduce that issue, I'd gla

Re: Trying to identify the problem with CQL ...

2013-03-05 Thread Gabriel Ciuloaica
So, I have added more logging to the test app (comments inline). For some reason I'm loosing updates. In a for loop I'm executing upload, read writetime, download blob. Executed 10 times... See iteration number 2 and 3 1. initialize session 0[main] INFO com.datastax.driver.core.Clus

Re: Trying to identify the problem with CQL ...

2013-03-05 Thread Gabriel Ciuloaica
Hi Sylvain, thanks for fast answer. I have updated keyspace definition and cassandra-topologies.properties to all 3 nodes and restarted each node. Both problems are still reproducible. I'm not able to read my writes and also the selects shows same data as in my previous email. for write and

Re: Trying to identify the problem with CQL ...

2013-03-05 Thread Sylvain Lebresne
Without looking into details too closely, I'd say you're probably hitting https://issues.apache.org/jira/browse/CASSANDRA-5292 (since you use NTS+propertyFileSnitch+a DC name in caps). Long story short, the CREATE KEYSPACE interpret your DC-TORONTO as dc-toronto, which then probably don't match wh

Trying to identify the problem with CQL ...

2013-03-05 Thread Gabriel Ciuloaica
Hello, I'm trying to find out what the problem is and where it is located. I have a 3 nodes Cassandra cluster (1.2.1), RF=3. I have a keyspace and a cf as defined (using PropertyFileSnitch): CREATE KEYSPACE backend WITH replication = { 'class': 'NetworkTopologyStrategy', 'DC-TORONTO': '3' };

Re: Problem with CQL

2013-02-28 Thread Jabbar
Because your name field is a primary key. You must specify the primary key for the query to be valid. On 28 February 2013 17:51, Everton Lima wrote: > Thanks. Thats work. > Why an Equal restriction is required? > > > 2013/2/28 Jason Wee > >> You need an equal operator in your query. For instan

Re: Problem with CQL

2013-02-28 Thread Everton Lima
Thanks. Thats work. Why an Equal restriction is required? 2013/2/28 Jason Wee > You need an equal operator in your query. For instance, SELECT * FROM > users WHERE country = 'malaysia' age > 20 > > > On Thu, Feb 28, 2013 at 10:04 PM, Everton Lima wrote: > >> Hello, >> I was using cql 2. I have

Re: Problem with CQL

2013-02-28 Thread Jason Wee
You need an equal operator in your query. For instance, SELECT * FROM users WHERE country = 'malaysia' age > 20 On Thu, Feb 28, 2013 at 10:04 PM, Everton Lima wrote: > Hello, > I was using cql 2. I have the following query: >SELECT * FROM users WHERE age > 20 AND age < 25; > > The table wa

Problem with CQL

2013-02-28 Thread Everton Lima
Hello, I was using cql 2. I have the following query: SELECT * FROM users WHERE age > 20 AND age < 25; The table was created as follow: CREATE TABLE users (name PRIMARY KEY, age float); After create table and insert some data I create the Secondary Index: CREATE INDEX age_index ON users