Repository navigation
Commit 899d121
committed
docs(migrate): add the migrate glossary and the forced-pass obligation ADR
The review of #1193 kept reopening the same question: whether a forced
backfill pass may resume without force. The rule was being worked out per
run and per command. This records the vocabulary agreed for the follow-up
design in #1217 (column migration, direction, twin, backfill pass, run,
obligation, waiver, abort) and the decision that a forced pass is an
obligation on the column migration, enforced by @cipherstash/migrate for
every caller, CLI or embedded worker.
Refs #12171 parent d168a94 commit 899d121
1 file changed
Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| 10 | + | |
| 11 | + | |
10 | 12 | | |
11 | 13 | | |
12 | 14 | | |
| |||
0 commit comments