OP wants to know good use cases where to use ttl setting.
Answer: Any situation where the cost of retaining the data exceeds the value to
be gained from the data. Using ttl allows for automatic purging of data.
Answer2: Any situation where you have to enforce specific retention policies
for
This is a good writeup that should probably go to refguide.
bq. example would be password reset attempts
In some systems such information would have long retention period (maybe to
conform to certain regulation).
Cheers
On Fri, Sep 26, 2014 at 9:10 AM, Wilm Schumacher wrote:
> Hi,
>
> your ma
Hi,
your mail got me thinking about a general answer.
I think a good answer would be: all data that are only usefull for a
specific time AND are possibly generated infinitely for a finite number
of users should have a ttl. OR when the space is very small compared to
the number of users.
An examp
I wrote a cookie store for node.js using hbase. By this method the
sessions are deleted "regularly" after a specific time nothing happens
on a specific session.
Am 26.09.2014 um 17:20 schrieb yonghu:
> Hello,
>
> Can anyone give me a concrete use case for ttl deletions? I mean in which
> situatio
Hello,
Can anyone give me a concrete use case for ttl deletions? I mean in which
situation we should set ttl property?
regards!
Yong
