cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DuyHai Doan <doanduy...@gmail.com>
Subject Re: Secondary Index on Boolean column with TTL
Date Mon, 31 Oct 2016 16:53:58 GMT
Technically TTL should be handled properly. However, be careful of expired
data turning into tombstones. For the original table, it may be a tombstone
on a skinny partition but for the 2nd index, it may be a tombstone set on a
wide partition and you'll start getting into trouble when reading a
partition with a lot of them

On Mon, Oct 31, 2016 at 5:08 PM, Oleg Krayushkin <allight.me@gmail.com>
wrote:

> Hi, DuyHai, thank you.
>
> I got the idea of caveat with too low cardinality, but still wondering of
> possible troubles at the idea to put TTL (months) on indexed column (not
> bool, say, 100 different values of int).
>
> 2016-10-31 16:33 GMT+03:00 DuyHai Doan <doanduyhai@gmail.com>:
>
>> http://www.planetcassandra.org/blog/cassandra-native-seconda
>> ry-index-deep-dive/
>>
>> See section E Caveats which applies to your boolean use-case
>>
>> On Mon, Oct 31, 2016 at 2:19 PM, Oleg Krayushkin <allight.me@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Is it a good approach to make a boolean column with TTL and build a
>>> secondary index on it?
>>> (For example, I want to get rows which need to be updated after a
>>> certain time, but I don't want, say, to add a filed "update_date" as
>>> clustering column or to create another table)
>>>
>>> In what kind of trouble it could lead me?
>>>
>>> Thanks in advance for any suggestions.
>>>
>>> --
>>>
>>> Oleg Krayushkin
>>>
>>
>>
>
>
> --
>
> Oleg Krayushkin
>

Mime
View raw message