[CASSANDRA-16175] Avoid removing batch when it's not created during view replication

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.26, 3.11.12, 4.0.2, 4.1-alpha1, 4.1
• Component/s: Feature/Materialized Views
• Bug Category: Code - Bug - Unclear Impact
• Severity: Low
• Complexity: Normal
• Discovered By: User Report
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/57f53f53ae811f00cf9c1f84bd0414d99391f1ce

Test and Documentation Plan

https://issues.apache.org/jira/browse/CASSANDRA-16175?focusedCommentId=17407713&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17407713

• Assignee: Ekaterina Dimitrova
• Reporter: Zhao Yang

Authors

Ekaterina Dimitrova, Zhao Yang

Reviewers

Brandon Williams

• Created: 02/Oct/20 17:46
• Updated: 27/May/22 19:25
• Resolved: 07/Sep/21 15:02

Description

When the base replica is also a view replica we don't write a local batchlog, but they are unnecessarily removed when the view write is successful, what creates (and persists) a tombstone into the system.batches table.

Issue Links

• is a child of: CASSANDRA-15921 4.0 quality testing: Materialized View