feat(resync): Add support to update snapshot config (max_parallel_workers, num_tables, rows_per_partition) during resync signal#4273
Conversation
…kers, num_tables, rows_per_partition) during resync signal
01f3100 to
c396d6f
Compare
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Code reviewBug: Snapshot parameter overrides lost in resync-during-resync path (flow/workflows/cdc_flow.go, line 652-656). overrideSnapshotParametersInState(val, state) correctly updates the workflow state with the new snapshot parameters, but uploadConfigToCatalog(ctx, cfg) (line 653) and state.DropFlowInput.FlowConnectionConfigs = cfg (line 656) both use the raw cfg which still has the old snapshot parameter values. When DropFlowWorkflow later calls ContinueAsNew with input.FlowConnectionConfigs and nil state, NewCDCFlowWorkflowState initializes snapshot params from the config which never received the overrides. The snapshot parameter changes are silently discarded. Compare with the other resync paths (e.g., lines 516-524 and lines 889-897) which correctly use syncStateToConfigProtoInCatalog(ctx, cfg, state) to copy state values into the config. Suggested fix: After overrideSnapshotParametersInState(val, state), manually copy snapshot parameters from state to cfg before uploading to catalog. |
❌ 2 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
🔄 Flaky Test DetectedAnalysis: Two e2e tests failed due to flaky conditions: a CDC setup phase timeout ( ✅ Automatically retrying the workflow |
🔄 Flaky Test DetectedAnalysis: The e2e test ✅ Automatically retrying the workflow |
|
moved to #4276 |
No description provided.