Strange select result when using date grater than query

Hello, I am fairly new to cassandra so this might be naieve question: I have table that currently has following entries: SELECT asset_id,event_time,sensor_type, temperature,humidity from temp_humidity_data where asset_id='2'; asset_id | event_time | sensor_type | temperature | hu

Re: Strange select result when using date grater than query

e than 7 time zones behind GMT? If so, that would make 03:33 your > query less than 03:33-0700 Your query is using the default time zone, which > will be the time zone configured for the coordinator node executing the > query. > > IOW, where are you? > > -- Jack Krupansky > >

Suggestion for improving cassandra performance

I have table with 128244 entries in it. I am running one cassandra node on AWS EC2 x.large instance. Cassandra is the only daemon running on this machine. Its SSD storage. Its taking cassandra python driver running on another machine 7 seconds to retrieve that data. This is pretty small table wit

Re: Strange select result when using date grater than query

hat is > separate from the actual query execution on the server coordinator node. > cqlsh is merely a "client", not the "server". And separate from the actual > data, which is stored in GMT. > > > -- Jack Krupansky > > -Original Message- From: Sub

Re: range query times out (on 1 node, just 1 row in table)

I am running into exact same issue where >= queries on secondary indexes don't work reliably, even in single node environment (using 2.1.0-rc5) and quering from same machine where cassandra server is running. If secondary indices can't give results, when using cassandra is one supposed to create

Help with select IN query in cassandra

generate unique id upon insert (like old-style rdms's auto-fields). Below is software version info. show VERSION ; [cqlsh 4.1.1 | Cassandra 2.0.9 | CQL spec 3.1.1 | Thrift protocol 19.39.0] I really don't understand what the error message preceeding column "event_time" is either not restricted or by no-EQ relation? -Subodh Nijsure

Re: Help with select IN query in cassandra

timestamp field is my bridge between Sal and nosql world. Subodh On Aug 31, 2014 5:33 PM, "Laing, Michael" wrote: > Are event_time and timestamp essentially representing the same datetime? > > On Sunday, August 31, 2014, Subodh Nijsure > wrote: > >> I have following dat

Re: Help with select IN query in cassandra

o_table where asset_id = 'a' and event_time = >>> 1231234; >> >> >> Or you could apply a range of "timestamp"s: >>> >>> SELECT * from sensor_info_table where asset_id = 'a' and event_time = >>> 1231234 and "time

Re: Help with select IN query in cassandra

= and event_time < >> ; >> select * from sensor_asset where asset_id = and event_time < >> and event_time > ; >> >> *** >> >> Many people (not me) handle sensor data, so there may be better overall >> approaches considering volumes, deleti

Re: Help with select IN query in cassandra

etc. > > But the above is simple and should make your current approach workable as > you iterate toward a complete solution. > > Cheers, > ml > > > > On Sun, Aug 31, 2014 at 11:08 PM, Subodh Nijsure > wrote: >> >> Thanks for your help Michael. >&g

Unable to connect to cassandra server on EC2?

Hello, I have setup a new EC2 instance to run cassandra on EC2, have gone through bunch of questions that don't seem to help. I am running apache-cassandra-2.1.0-rc3 I have opened port 9160, 9042 on my EC2 instance say its IP address is 1.2.3.4 Since this is single node system I haven't opened

Re: Unable to connect to cassandra server on EC2?

Thanks Mark, indeed changing port to 9042 worked. In addition I set following parameters in my cassandra.yaml rpc_address: 0.0.0.0 broadcast_rpc_address: 1.2.3.4 ( External IP address of my EC2 machine) Regards, -Subodh Nijsure On Sun, Aug 10, 2014 at 6:13 AM, Mark Reddy wrote: >