Thanks a lot, DuyHai!
2016-10-31 19:53 GMT+03:00 DuyHai Doan :
> 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
>
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
part
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 :
> http://www.planetcassandra.org/blog/cassan
http://www.planetcassandra.org/blog/cassandra-native-secondary-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
wrote:
> Hi,
>
> Is it a good approach to make a boolean column with TTL and build a
> secondary index on
