Add start execution from trigger support for existing core sensors #41021
Conversation
This file contains 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:core-operators
Lee-W
force-pushed
the
add-start-execution-from-trigger-support-for-existing-core-sensors
branch
from
6b001c1
to
e6ea031
Compare
Lee-W
force-pushed
the
add-start-execution-from-trigger-support-for-existing-core-sensors
branch
from
e6ea031
to
4768c52
Compare
Lee-W
force-pushed
the
add-start-execution-from-trigger-support-for-existing-core-sensors
branch
from
4768c52
to
470d4ca
Compare
phanikumv
approved these changes
Jul 30, 2024
Lee-W
deleted the
add-start-execution-from-trigger-support-for-existing-core-sensors
branch
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.
After #38674, #39585 and #40935, we allow tasks to be executed directly from trigger. This PR added this feature to TimeSensorAsync, FileSensor and DateTimeSensorAsync
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.