Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.214.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CB5FFBF2.4538%bburruss@expedia.com>
References: <CB5FFBF2.4538%bburruss@expedia.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Fri, 17 Feb 2012 07:55:29 -0600
Message-ID: 
 <CALdd-zhthxk0O-wm4DbLW-zyrL1RsbppOnr46uE4PQ4VcuefaA@mail.gmail.com>
Subject: Re: deleting rows and tombstones
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <bburruss@expedia.com> 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. =A0I know if I delete a lot of individual columns the tombsto=
nes
> 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?


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com