Add dynamic task mapping no-op example#67022
Open
vividbaek wants to merge 1 commit into
Open
Conversation
potiuk
added
the
ready for maintainer review
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
2 participants
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.
This PR adds a small documentation example for zero-length dynamic task
mapping.
The example shows a scan-and-repair style Dag where a discovery task can return
an empty list. In that case, the mapped task is marked as skipped, and a
downstream summary task can treat the run as a successful no-op when it uses a
trigger rule that allows skipped upstream tasks.
How tested:
git diff --check.Was generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex (GPT-5) following [the guidelines](https://github.com/
apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-
contributions)