g the single
>>>> coordinator as the bottleneck.
>>>>
>>>> On Tue, Apr 17, 2018 at 10:05 PM, Xiangfei Ni
>>>> wrote:
>>>>
>>>>> Hi Nate,
>>>>>
>>>>>
17, 2018 at 10:05 PM, Xiangfei Ni
>>> wrote:
>>>
>>>> Hi Nate,
>>>>
>>>> Thanks for your reply!
>>>>
>>>> Is there other way to design this table to meet this requirement?
>>>>
>>>>
>>>>
&g
: user@cassandra.apache.org
主题: Re: 答复: Time serial column family design
Hi David,
Could you describe why you chose to include the create date in the partition
key? If the vin in enough "partitioning", meaning that the size (number of rows
x size of row) of each partition is less than 1
Thanks for your reply!
>>>
>>> Is there other way to design this table to meet this requirement?
>>>
>>>
>>>
>>> Best Regards,
>>>
>>>
>>>
>>> 倪项菲*/ **David Ni*
>>>
>>> 中移德电网络科技有限公司
>>&
Ltd, co.
>>
>> Add: 2003,20F No.35 Luojia creative city,Luoyu Road,Wuhan,HuBei
>>
>> Mob: +86 13797007811|Tel: + 86 27 5024 2516
>>
>>
>>
>> *发件人:* Nate McCall
>> *发送时间:* 2018年4月17日 7:12
>> *收件人:* Cassandra Users
>> *主题:* Re: Time seri
e city,Luoyu Road,Wuhan,HuBei
>
> Mob: +86 13797007811|Tel: + 86 27 5024 2516
>
>
>
> *发件人:* Nate McCall
> *发送时间:* 2018年4月17日 7:12
> *收件人:* Cassandra Users
> *主题:* Re: Time serial column family design
>
>
>
>
>
> Select * from test where vin =“ZD41578123DSAF
: Nate McCall
发送时间: 2018年4月17日 7:12
收件人: Cassandra Users
主题: Re: Time serial column family design
Select * from test where vin =“ZD41578123DSAFWE12313” and create_date in
(20180416, 20180415, 20180414, 20180413, 20180412….);
But this cause the cql query is very long,and I don’t know
>
>
> Select * from test where vin =“ZD41578123DSAFWE12313” and create_date in
> (20180416, 20180415, 20180414, 20180413, 20180412….);
>
> But this cause the cql query is very long,and I don’t know whether there
> is limitation for the length of the cql.
>
> Please give me some advice,t
Hi Experts,
We have a design requirement, for example,
Create table test(
vin text,
create_date int,
create_time timestamp,
a text,
b text,
primary key ((vin,create_date),create_time))
with clustering order by (create_time DESC);
we store data in this table like thi