We're finding that reading deleted columns can be very slow and I'm
trying to get confirmation for our analysis of what happens. We wrote
lots of data eons ago into fairly large rows (up to 1MB). We recently
read those rows and then deleted them. After this, we ran a
verification-type pass that
This is expected due to tombstones, which this explains pretty well:
http://wiki.apache.org/cassandra/DistributedDeletes
If you don't have any tombstones for the row, the bloom filter will let
Cassandra avoid doing any disk reads at all 99% of the time.
On Tue, Jul 10, 2012 at 10:50 AM, Thorsten
