Deleting the entire row at once only creates a row-level tombstone. This is almost free. "Tombstone buildup" happens when performing column-level deletes, then inserting more (different) columns. The classic example is modeling a queue in a row.
On Tue, Feb 14, 2012 at 1:54 PM, Todd Burruss <[email protected]> wrote: > my design calls for deleting a row (by key, not individual columns) and > re-inserting it a lot and I'm concerned about tombstone build up slowing > down reads. I know if I delete a lot of individual columns the tombstones > will build up and slow down reads until they are cleaned up, but not sure if > the same holds for deleting the whole role. > > thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
