[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266195#comment-14266195 ]
Philip Thompson commented on CASSANDRA-8558: -------------------------------------------- Thanks for the better test. The new bisect was much cleaner, the only failure I saw was the expected one highlighted by the reporter. Here is the bisect output: {code} 362cc05352ec67e707e0ac790732e96a15e63f6b is the first bad commit commit 362cc05352ec67e707e0ac790732e96a15e63f6b Author: Sylvain Lebresne <sylv...@datastax.com> Date: Tue Oct 29 11:03:52 2013 +0100 Push composites support in the storage engine patch by slebresne; reviewed by benedict for CASSANDRA-5417 :100644 100644 c0d0f0d243f0454c1b1926957634bb52165295aa dcc7e33b064e52d245d8c6ba5de887c74e0f0a00 M CHANGES.txt :040000 040000 da620b5b36e8ba6b97cdb8efe4f690692a85e15e 5dd1113af54ad7b90dd8694e462483bac6e7f985 M src :040000 040000 1fe1db9fca3bf03946828cdc917a0aef5bf7a9e1 3bf0563361febc821a357cf61b5a0760f5a8eca4 M test {code} > deleted row still can be selected out > ------------------------------------- > > Key: CASSANDRA-8558 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8558 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: 2.1.2 > java version "1.7.0_55" > Reporter: zhaoyan > Assignee: Philip Thompson > Priority: Blocker > Fix For: 2.1.3 > > > first > {code}CREATE KEYSPACE space1 WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': 3}; > CREATE TABLE space1.table3(a int, b int, c text,primary key(a,b)); > CREATE KEYSPACE space2 WITH replication = {'class': 'SimpleStrategy', > 'replication_factor': 3};{code} > second > {code}CREATE TABLE space2.table1(a int, b int, c int, primary key(a,b)); > CREATE TABLE space2.table2(a int, b int, c int, primary key(a,b)); > INSERT INTO space1.table3(a,b,c) VALUES(1,1,'1'); > drop table space2.table1; > DELETE FROM space1.table3 where a=1 and b=1; > drop table space2.table2; > select * from space1.table3 where a=1 and b=1;{code} > you will find that the row (a=1 and b=1) in space1.table3 is not deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)