Hi Mahesh, the problem is that every column is only tombstoned for as long as the original column was valid.
So if the last update was only valid for 1 sec, then the tombstone will also be valid for 1 second! If the previous was valid for a longer time, then this old value might reappear. Maybe you can explain why you are doing this? kind regards, Christian On Mon, Feb 17, 2014 at 6:18 PM, mahesh rajamani <rajamani.mah...@gmail.com>wrote: > Christain, > > Yes. Is it a problem? Can you explain what happens in this scenario? > > Thanks > Mahesh > > > On Fri, Feb 14, 2014 at 3:07 PM, horschi <hors...@gmail.com> wrote: > >> Hi Mahesh, >> >> is it possible you are creating columns with a long TTL, then update >> these columns with a smaller TTL? >> >> kind regards, >> Christian >> >> >> On Fri, Feb 14, 2014 at 3:45 PM, mahesh rajamani < >> rajamani.mah...@gmail.com> wrote: >> >>> Hi, >>> >>> I am using Cassandra 2.0.2 version. On a wide row (approx. 10000 >>> columns), I expire few column by setting TTL as 1 second. At times these >>> columns show up during slice query. >>> >>> When I have this issue, running count and get commands for that row >>> using Cassandra cli it gives different column counts. >>> >>> But once I run flush and compact, the issue goes off and expired columns >>> don't show up. >>> >>> Can someone provide some help on this issue. >>> >>> -- >>> Regards, >>> Mahesh Rajamani >>> >> >> > > > -- > Regards, > Mahesh Rajamani >
