Let me point out that the current thread is about counter removal, not about
counter TTL. Counter expiration have other problems, so that even if you do not
care about incrementing a counter again after it expires, it will
still not work for you
(please look at the discussion on
https://issues.apac
What if it is OK for our case and we need counters with TTL?
For us Counters and TTL both are important. After column is expired it is
not important what value counter will have.
Scanning millions rows just to delete expired ones is not a solution.
2011/6/14 Sylvain Lebresne
> As listed here: ht
As listed here: http://wiki.apache.org/cassandra/Counters, counter deletion is
provided as a convenience for permanent deletion of counters but, because
of the design of counters, it is never safe to issue an increment on a
counter that
has been deleted (that is, you will experience back to life be
Please take a look at this thread over in the hector-users mailing list:
http://groups.google.com/group/hector-users/browse_thread/thread/99835159b9ea1766
It looks as if the deleted columns are coming back to life when they shouldn't
be.
I don't want to open a bug on something if it's already g
