thanks Jens and Ryan, is clear to me what happens with tombstones for a CF
row
Now, the same behavior that apply to CF rows also apply to elements in a
set Data type?
Regards
On Tue, Jan 6, 2015 at 12:31 PM, Ryan Svihla wrote:
> Tombstone management is a big conversation, you can manage it in
Tombstone management is a big conversation, you can manage it in one of the
following ways
1) set a gc_grace_seconds of 0 and then run nodetool compact while using
size tiered compaction..as frequently as needed. This often is a pretty
lousy solution as gc_grace_seconds means you're not very parti
Hi Eduardo,
Zitat von Eduardo Cusa :
[...]
I have to worry about the tombstones generated? Considering that I will
have many daily set updates
that depends on your definition of "many"... we've run into a
situation where we wanted to age out old data using TTL...
unfortunately, we ran in
Hi, using the following updates i made expire the direfent values in
deferent times:
update categories_sync using ttl 60 set category = category + {'2'} where
userid = 'u1';
update categories_sync using ttl 120 set category = category + {'3'}
where userid = 'u1';
update categories_sync using
Hi guys, I have to work with the following model:
userid : text
categories: [3, 4, 55, 623, ...]
in my use case, the list of values is updated every day, with 100 millons
of users and a total of 500 categories at most.
There is a way to assign a TT to each item in the category list?
