Radim, We are only deleting columns. *Rows are never deleted.* We are continually adding new columns that are then deleted. * Existing columns (deleted or otherwise) are never updated. * Ross*
* On 28 March 2012 13:51, John Laban <j...@pagerduty.com> wrote: > (Radim: I'm assuming you mean "do not delete already deleted columns" as > Ross doesn't delete his rows.) > > Just to be clear about Ross' situation: he continually inserts columns > and later deletes columns from the same set of rows. As long as he * > doesn't* *keep deleting already-deleted columns* (which refreshes the > tombstone on them), the deleted columns *should* get cleaned up, right? > (Even though the row itself continually gets new columns inserted and > other columns deleted?) > > Thanks, > John > > > > > On Tue, Mar 27, 2012 at 2:21 AM, Radim Kolar <h...@filez.com> wrote: > >> Dne 27.3.2012 11:13, Ross Black napsal(a): >> >> Any pointers on what I should be looking for in our application that >>> would be stopping the deletion of tombstones? >>> >> do not delete already deleted rows. On read cassandra returns deleted >> rows as empty in range slices. >> > >
