[
https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-8558:
----------------------------------------
Attachment: 8558.txt
Yes, we're inconsistent in our use of the EOC for the start of slice/range
tombstones. We should really always be using {{EOC.START}} (the same way we use
{{EOC.END}} for the end), but for bad historical reasons we're using
{{EOC.NONE}}. In 2.0 we're fine because we're consistently using {{EOC.NONE}}
for both slices and range tombstones (which is ok in practice, even though it's
somewhat unlogical). In 2.1 however, range tombstones have somehow been "fixed"
to use {{EOC.START}} but slices haven't. Anyway, the right fix is basically to
finish the job and use {{EOC.START}} for slices too (it's an oversight of mine
that this hasn't been done before). Attaching simple patch that does that
(along with the test above as a unit test).
> 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: Sylvain Lebresne
> Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: 8558.txt
>
>
> 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)
