I don't think thats solves my problem. The question really is why can't we
use ranges for both time columns when they are part of the primary key.
They are on 1 row after all. Is this just a CQL limitation?
-Raj
On Sat, Feb 14, 2015 at 3:35 AM, DuyHai Doan wrote:
> "I am trying to get the state
Jirka,
> But I am really interested how it can work well with Spark/Hadoop where
> you basically needs to read all the data as well (as far as I understand
> that).
I can't give you any benchmarking between technologies (nor am i
particularly interested in getting involved in such a discussion)
"I am trying to get the state as of a particular transaction_time"
--> In that case you should probably define your primary key in another
order for clustering columns
PRIMARY KEY (weatherstation_id,transaction_time,event_time)
Then, select * from temperatures where weatherstation_id = 'foo' an
