[v3-2-test] Enable parallel backfill by eliminating shared state between providers (#63288)#66909
Closed
vatsrahul1001 wants to merge 1 commit into
Closed
[v3-2-test] Enable parallel backfill by eliminating shared state between providers (#63288)#66909vatsrahul1001 wants to merge 1 commit into
vatsrahul1001 wants to merge 1 commit into
Conversation
#63288) Add --provider and --providers-json flags to extract_parameters.py and extract_connections.py so each backfill run uses an isolated temp providers.json and only scans the target provider. In --provider mode, modules.json is not written (it would be incomplete), so concurrent runs don't clobber each other. The backfill command now creates a TemporaryDirectory with per-version providers.json files instead of patching a shared file. (cherry picked from commit a9c0bf3)
Closed
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #63288 for the Airflow 3.2.2 patch release.
Backported as a prerequisite for the `breeze registry` tooling chain that ultimately enables #66311 (Breeze `down` discovery). #63288 introduces the `@option_python` decorator on `registry backfill` and the parallel-backfill plumbing that downstream PRs (#65223, #65972, #65984, #66311) build on.
Conflict resolution
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.7) following the guidelines