Hi Jonas, the bug that was fixed in 4116 meant that the max timestamp recorded for an sstable didn't consider any tombstones from row deletions. This meant that from some queries, some sstables were not being read when they should have been. I couldn't say categorically that this would cause the deleted data to reappear in read results, but I can see how it could do.
Cheers, Sam On 8 May 2012 10:15, Jonas Borgström <jo...@borgstrom.se> wrote: > Hi, > > Can someone give some more details about the CASSANDRA-4116 bug fixed in > this release? Could this cause resurrection of deleted data for example? > > https://issues.apache.org/jira/browse/CASSANDRA-4116 > > / Jonas > > > On 2012-05-08 11:04 , Sylvain Lebresne wrote: >> The Cassandra team is pleased to announce the release of Apache Cassandra >> version 1.0.10. >> >> Cassandra is a highly scalable second-generation distributed database, >> bringing together Dynamo's fully distributed design and Bigtable's >> ColumnFamily-based data model. You can read more here: >> >> http://cassandra.apache.org/ >> >> Downloads of source and binary distributions are listed in our download >> section: >> >> http://cassandra.apache.org/download/ >> >> This version is maintenance/bug fix release[1]. As always, please pay >> attention to the release notes[2] and Let us know[3] if you were to encounter >> any problem. >> >> Have fun! >> >> [1]: http://goo.gl/u8gIO (CHANGES.txt) >> [2]: http://goo.gl/mAHbY (NEWS.txt) >> [3]: https://issues.apache.org/jira/browse/CASSANDRA > >
