cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3708) Support "composite prefix" tombstones
Date Tue, 10 Apr 2012 15:05:16 GMT


Sylvain Lebresne commented on CASSANDRA-3708:

I've pushed a first version of this at

It's an inefficient version in that range tombstones are stored where the row deletion infos
is stored today. In other words, we deserialize all those range tombstones (for a row) every
time. Thus this won't scale to more than a few tombstones. I have plans to improve that, but
in the meantime this version felt like a good first step. In particular, outside of not scaling,
it is fully functional and an improved version will build on this anyway. As such, feedbak
on this would already be useful.

Basically, what this does is abstracting the deletion details inside the (existing) DeletionInfo
class, to then adds support for range tombstones (stored with an interval tree) to that class.
Amongst various details, this change the serialized form of a ColumnFamily, and thus required
to push the message versioning down to the ColumnFamilySerializer.

Unit tests are passing but I've also put a simple at
Note that only CQL3 has support for those range tombstones.

> Support "composite prefix" tombstones
> -------------------------------------
>                 Key: CASSANDRA-3708
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message