Skip to content

Draft: (DO NOT MERGE) Draft: Keeps for desired sharding key backfills

Tiger Watson requested to merge sharding-key-backfill-keeps into master

What does this MR do and why?

Not for merging. Similar to !139747, these are single-use keeps.

Status of Keeps

Small tables

Reference issue: #429173 (closed)

Steps:

  1. Add column, index and FK, start backfill
    • Keep: BackfillDesiredShardingKeySmallTable
    • Status: Ready, several MRs merged ✅
  2. Finalize backfill
    • Keep: OverdueFinalizeBackgroundMigration (not part of this MR)
    • Status: Ready ✅ (runs automatically)
  3. Add not null constraint
    • Keep: BackfillDesiredShardingKeySmallTableStep3
    • Status: Ready, not yet run ✅

Large tables

Reference issue: #429174 (closed)

Steps:

  1. Add column and async index, start backfill
    • Keep: BackfillDesiredShardingKeyLargeTable
    • Status: Ready, not yet run ✅
  2. Finalize backfill
    • Keep: OverdueFinalizeBackgroundMigration (not part of this MR)
    • Status: Ready ✅ (runs automatically)
  3. Finalize aynsc index, add invalid FK and not null constraint, schedule async validation of FK and not null constraint
    • Keep: BackfillDesiredShardingKeyLargeTableStep3
    • Status: Ready, not yet run ✅
  4. Finalize async FK and not null constraints
    • Keep: BackfillDesiredShardingKeyLargeTableStep4
    • Status: Ready, not yet run ✅
Edited by Tiger Watson

Merge request reports