Browse Source
fix: rebuild executor consumes bound plan, fix catch-up timing
fix: rebuild executor consumes bound plan, fix catch-up timing
Planner/executor contract: - RebuildExecutor.Execute() takes no arguments — consumes plan-bound RebuildSource, RebuildSnapshotLSN, RebuildTargetLSN - RecoveryPlan binds all rebuild targets at plan time - Executor cannot re-derive policy from caller-supplied history Catch-up timing: - Removed unused completeTick parameter from CatchUpExecutor.Execute - Per-step ticks synthesized as startTick + stepIndex + 1 - API shape matches implementation New test: PlanExecuteConsistency_RebuildCannotSwitchSource - Plans snapshot+tail, then mutates storage history - Executor succeeds using plan-bound values (not re-derived) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>feature/sw-block
3 changed files with 80 additions and 35 deletions
-
21sw-block/engine/replication/driver.go
-
44sw-block/engine/replication/executor.go
-
50sw-block/engine/replication/executor_test.go
Write
Preview
Loading…
Cancel
Save
Reference in new issue