Hi All,
Sorry for the wide distribution.
Our cassandra is running on 1.0.10. Recently, we are facing a weird
situation. We have a column family containing wide rows (each row might
have a few million of columns). We delete the columns on a daily basis and
we also run major compaction on it
Boris,
We hit exactly the same issue, and you are correct the newly created SSTables
are the cause of why most of the column-tombstone not being purged.
There is an improvement in 1.2 train where both the minimum and maximum
timestamp for a row is now stored and used during the compaction to
This makes sense. Unless you are running major compaction a delete could
only happen if the bloom filters confirmed the row was not in the sstables
not being compacted. If your rows are wide the odds are that they are in
most/all sstables and then finally removing them would be tricky.
On Thu,
