fix: logical_date or run_after for google bigquery and workflow #55109
Conversation
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
boring-cyborg
bot
added
area:providers
provider:apache-hive
provider:google
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
related: #53634 #55073 #55092
In airflow 3,
logcial_dateis not available for asset triggered DAG runs.However, it was previously used for job ID generation in Bigquery and workflow ID for Workflows.
This PR proposes using
dag_run.run_afteras a substitute for asset triggered DAG runs.In this PR, I propose to use dagrun.run_after for assert triggered dag run.
What Wasn't Fixed
The usage of
context["logical_date"]inproviders/google/cloud/sensors/cloud_composer.pyremains unchangeed.