[CASSANDRA-12952] AlterTableStatement propagates base table and affected MV changes inconsistently

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.15, 3.11.1, 4.0-alpha1, 4.0
• Component/s: Feature/Materialized Views, Legacy/Distributed Metadata
• Bug Category: Availability - Unavailable
• Severity: Normal
• Since Version: 3.0.0
• Assignee: Andres de la Peña
• Reporter: Aleksey Yeschenko

Authors

Andres de la Peña

Reviewers

Zhao Yang

• Created: 24/Nov/16 15:11
• Updated: 15/May/20 08:05
• Resolved: 28/Jul/17 10:59

Description

In AlterTableStatement, when renaming columns or changing their types, we also keep track of all affected MVs - ones that also need column renames or type changes. Then in the end we announce the migration for the table change, and afterwards, separately, one for each affected MV.

This creates a window in which view definitions and base table definition are not in sync with each other. If a node fails in between receiving those pushes, it's likely to have startup issues.

The fix is trivial: table change and affected MV change should be pushed as a single schema mutation.

Issue Links

• links to: GitHub Pull Request #3