cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <>
Subject Re: Performance effects of tombstones in queue-like use cases
Date Tue, 30 Mar 2010 00:57:49 GMT
Does help?

On Mon, Mar 29, 2010 at 7:54 PM, Tatu Saloranta <> wrote:
> Quick question: Cassandra documentation explains implementation of
> deletes (using tombstones) quite well.
> But what I was not quite sure about was what actual effects of
> existing tombstones might have on doing range queries that would
> include those tombstones.
> That is: for a use case where new entries are always added at the end
> (like using time uuid as key, or just simple timestamp), but read and
> deleted from head (oldest entry), and range query always use minimal
> key. When accessing rows, does Cassandra then have to filter out all
> deleted (tombstone) entries from range?
> -+ Tatu +-

View raw message