State the limitation of the newly added start execution from trigger feature#40935
Merged
phanikumv merged 5 commits intoJul 25, 2024
Merged
Conversation
9edb80a to
00de837
Compare
uranusjr
reviewed
Jul 23, 2024
2bf41c1 to
6719a38
Compare
524c169 to
059d8ea
Compare
836cee0 to
3a193d2
Compare
…" as "Triggering Deferral from Task Start"
3a193d2 to
4c5186d
Compare
phanikumv
approved these changes
Jul 25, 2024
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.
In #38674, #39585 and #39912, we introduce
start_from_triggerandstart_trigger_argsto allow OP author/ DAG author to run task directly from triggerer without going into worker. However, the limitation is that all the kwargs passed to the trigger_cls need to be serializable. This PR add the description and update example to the deferring doc^ 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.