;
>> and
>> select count(*)
>> where token(customer_id,event_time) >= token('289','2016-03-01
>> 18:45:00+')
>> and token(customer_id,event_time) <= token('289','2016-03-12
>> 19:05:00+0000') ;
>>
>
thanks. that explains it.
-Original Message-
From: Jack Krupansky
To: user
Sent: Thu, Mar 10, 2016 5:28 pm
Subject: Re: What is wrong in this token function
>From the doc: "When using the RandomPartitioner or Murmur3Partitioner,
>Cassandra rows are ordered by the ha
27;,'2016-03-12
> 19:05:00+') ;
>
> are not same ?
>
> And yes I am aware of how to change the clustering_key to get the first
> query. This question is more of academic exercise for me.
>
>
> -Original Message-
> From: Jack Krupansky
> To: use
question is more of academic exercise for me.
-Original Message-
From: Jack Krupansky
To: user
Sent: Thu, Mar 10, 2016 4:55 pm
Subject: Re: What is wrong in this token function
What partitioner are you using? The default partitioner is not "ordered", so it
will randomly or
What partitioner are you using? The default partitioner is not "ordered",
so it will randomly order the hashes/tokens, so that tokens will not be
ordered even if your PKs are ordered. You probably want to use customer as
your partition key and event time as a clustering column - then you can use
RD
typo: the primary key was (customer_id + event_time )
-Original Message-
From: Rakesh Kumar
To: user
Sent: Thu, Mar 10, 2016 4:44 pm
Subject: What is wrong in this token function
C* 3.0.3
I have a table table1 which has the primary key on ((customer_id,event_id)).
I loaded 1.0
