Re: sstable2json and resurrected rows

On 2012-03-31 08:45 , Zhu Han wrote: Did you hit the bug here? https://issues.apache.org/jira/browse/CASSANDRA-4054 Yes looks like it. But what confuses me most is not the sstable2json bug but why the major compaction does not replace the deleted row data with a tombstone. Is that a bug or

Re: sstable2json and resurrected rows

Did you hit the bug here? https://issues.apache.org/jira/browse/CASSANDRA-4054 best regards, 坚果云 , 最简捷易用的云存储 无限空间, 文件同步, 备份和分享! 2012/3/30 Jonas Borgström > Let me rephrase my question: > > Is it true that deleted rows will still be present in the sstable after a > m

Re: sstable2json and resurrected rows

Let me rephrase my question: Is it true that deleted rows will still be present in the sstable after a major compaction with 1.0.8 (not just tombstones)? Or did I mess up my test below? / Jonas On 2012-03-28 10:23 , Jonas Borgström wrote: Hi all, I've noticed a change in behavior between

sstable2json and resurrected rows

Hi all, I've noticed a change in behavior between 0.8.10 and 1.0.8 when it comes to sstable2json output and major compactions. Is this a bug or intended behavior? With 1.0.8: create keyspace ks; use ks; create column family foo; set foo[1][1] = 1; nodetool -h localhost flush sstable2json foo