r data per
> sstable is already sorted.
>
>
>
> But be careful, if you end up with a worst case. If a customer_id is
> insertet every hour you can end up with reading many sstables decreasing
> read performance if the data should be kept a year or so.
>
>
>
> Jan
&
job, as your data per
>> sstable is already sorted.
>>
>>
>>
>> But be careful, if you end up with a worst case. If a customer_id is
>> insertet every hour you can end up with reading many sstables decreasing
>> read performance if the data should be kept
be kept a year or so.
>
>
>
> Jan
>
>
>
> Gesendet von meinem Windows 10 Phone
>
>
>
> Von: Jerry Lam <mailto:chiling...@gmail.com>
> Gesendet: Freitag, 7. April 2017 00:30
> An: user@cassandra.apache.org <mailto:user@cassandra.apache.org>
_id is
> insertet every hour you can end up with reading many sstables decreasing
> read performance if the data should be kept a year or so.
>
>
>
> Jan
>
>
>
> Gesendet von meinem Windows 10 Phone
>
>
>
> *Von: *Jerry Lam
> *Gesendet: *Frei
Gesendet von meinem Windows 10 Phone
Von: Jerry Lam
Gesendet: Freitag, 7. April 2017 00:30
An: user@cassandra.apache.org
Betreff: How does clustering key works with TimeWindowCompactionStrategy (TWCS)
Hi guys,
I'm a new and happy user of Cassandra. We are using Cassandra for time series
data
Hi guys,
I'm a new and happy user of Cassandra. We are using Cassandra for time
series data so we choose TWCS because of its predictability and its ease of
configuration.
My question is we have a table with the following schema:
CREATE TABLE IF NOT EXISTS customer_view (
customer_id bigint,
date
