Optimize deferrable execution mode AzureDataFactoryPipelineRunStatusSensor
#30983
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:microsoft-azure
josh-fell
approved these changes
May 1, 2023
Contributor
josh-fell
left a comment
josh-fell
left a comment
There was a problem hiding this comment.
LGTM, just a small naming update for a test case.
tests/providers/microsoft/azure/sensors/test_azure_data_factory.py
Outdated
Show resolved
Hide resolved
phanikumv
force-pushed
the
optimize_datafactory_sensor
branch
from
4cab412 to
9654443
Compare
80 tasks
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.
In deferrable mode for AzureDataFactoryPipelineRunStatusSensor, we should first check if job is successful or not in the execute method and only defer if that is not successful. This way we don’t run an unnecessary deferral cycle if the condition is already true.
cc @dstandish
^ 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.