On Tue, Jul 13, 2010 at 5:47 AM, Samuru Jackson
wrote:
> Thanks for the links.
>
> Actually it is pretty easy to catch those tombstoned keys on the
> client side. However, in certain applications it can generate some
> additional overhead on the network.
>
> I think it would be nice to have a forc
Thanks for the links.
Actually it is pretty easy to catch those tombstoned keys on the
client side. However, in certain applications it can generate some
additional overhead on the network.
I think it would be nice to have a forced garbage collection in the
API. This would IMHO ease to write Unit
The Tomstones are removed after GCGraceSeconds (in the
storage-config.xml), at the next Major Compaction
http://wiki.apache.org/cassandra/MemtableSSTable?highlight=%28tombstones%29Take
a look at http://wiki.apache.org/cassandra/DistributedDeletes and
Handling Failure on http://wiki.apache.org/
Hi,
I'm fairly new to Cassandra and started to set up a small cluster for
playing around and evaluating it for my potential purposes.
As far as I understand I can't remove whole rows - instead the columns
of a deleted rows are removed and a client can decided based on the
row's column count if it
