[
https://issues.apache.org/jira/browse/CASSANDRA-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155948#comment-13155948
]
Hudson commented on CASSANDRA-2786:
-----------------------------------
Integrated in Cassandra-0.8 #403 (See
[https://builds.apache.org/job/Cassandra-0.8/403/])
avoid dropping tombstones when they might still be needed to shadow data in
another sstable
patch by slebresne and jbellis for CASSANDRA-2786
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1205452
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/EchoedRow.java
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/compaction/CompactionController.java
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/compaction/LazilyCompactedRow.java
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/compaction/PrecompactedRow.java
*
/cassandra/branches/cassandra-0.8/test/unit/org/apache/cassandra/SchemaLoader.java
*
/cassandra/branches/cassandra-0.8/test/unit/org/apache/cassandra/db/compaction/CompactionsTest.java
> After a minor compaction, deleted key-slices are visible again
> --------------------------------------------------------------
>
> Key: CASSANDRA-2786
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2786
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0, 0.8.7
> Environment: Reproduced on single Cassandra node (CentOS 5.5)
> Reproduced on single Cassandra node (Windows Server 2008)
> Reporter: rene kochen
> Assignee: Sylvain Lebresne
> Fix For: 0.8.8
>
> Attachments: 0001-Fix-wrong-purge-of-deleted-cf.patch,
> 2786_part2.patch, 2786_part3-v2.txt, 2786_part3.patch, CassandraIssue.zip,
> CassandraIssueJava.zip
>
>
> After a minor compaction, deleted key-slices are visible again.
> Steps to reproduce:
> 1) Insert a row named "test".
> 2) Insert 500000 rows. During this step, row "test" is included in a major
> compaction:
> file-1, file-2, file-3 and file-4 compacted to file-5 (includes "test").
> 3) Delete row named "test".
> 4) Insert 500000 rows. During this step, row "test" is included in a minor
> compaction:
> file-6, file-7, file-8 and file-9 compacted to file-10 (should include
> tombstoned "test").
> After step 4, row "test" is live again.
> Test environment:
> Single node with empty database.
> Standard configured super-column-family (I see this behavior with several
> gc_grace settings (big and small values):
> create column family Customers with column_type = 'Super' and comparator =
> 'BytesType;
> In Cassandra 0.7.6 I observe the expected behavior, i.e. after step 4, the
> row is still deleted.
> I've included a .NET program to reproduce the problem. I will add a Java
> version later on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
