Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-12952

AlterTableStatement propagates base table and affected MV changes inconsistently

    XMLWordPrintableJSON

    Details

    • Severity:
      Normal
    • Since Version:

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                adelapena Andres de la Peña
                Reporter:
                aleksey Aleksey Yeschenko
                Authors:
                Andres de la Peña
                Reviewers:
                ZhaoYang
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: