[CASSANDRA-12765] SSTable ignored incorrectly with partition level tombstone

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 2.1.17, 2.2.9, 3.0.10, 3.10, 4.0-alpha1, 4.0
• Component/s: Legacy/Local Write-Read Paths
• Bug Category: Correctness - API / Semantic Implementation
• Severity: Critical
• Since Version: 2.0 beta 1
• Assignee: Cameron Zemek
• Reporter: Cameron Zemek

Authors

Cameron Zemek

Reviewers

Marcus Eriksson

• Created: 10/Oct/16 05:04
• Updated: 15/May/20 08:02
• Resolved: 21/Oct/16 07:18

Description

CREATE TABLE test.payload(
  bucket_id TEXT,
  name TEXT,
  data TEXT,
  PRIMARY KEY (bucket_id, name)
);
insert into test.payload (bucket_id, name, data) values ('8772618c9009cf8f5a5e0c18', 'test', 'hello');

Flush nodes (nodetool flush)

insert into test.payload (bucket_id, name, data) values ('8772618c9009cf8f5a5e0c19', 'test2', 'hello');
delete from test.payload where bucket_id = '8772618c9009cf8f5a5e0c18';

Flush nodes (nodetool flush)

select * from test.payload where bucket_id = '8772618c9009cf8f5a5e0c18' and name = 'test';

Expected 0 rows but get 1 row back.