[CASSANDRA-13762] Ensure views created during (or just before) range movements are properly built

• Type: Bug
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Component/s: Feature/Materialized Views
• Labels: materializedviews
• Severity: Low
• Assignee: Unassigned
• Reporter: Paulo Motta

Reviewers

Andres de la Peña

• Created: 14/Aug/17 13:02
• Updated: 22/Jul/21 11:50

Description

CASSANDRA-13065 assumes the source node has its views built to skip running base mutations through the write path during range movements.

It is possible that the source node has not finished building the view, or that a new view is created during a range movement, in which case the view may be wrongly marked as built on the destination node.

The former problem was introduced by #13065, but even before that a view created during a range movement may not be correctly built on the destination node because the view builder will be triggered before it has finished streaming the source data, wrongly marking the view as built on that node.

Issue Links

• is related to: CASSANDRA-12245 initial view build can be parallel