merge AzureDataFactoryPipelineRunStatusAsyncSensor to AzureDataFactoryPipelineRunStatusSensor #30250
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
…ataFactoryPipelineRunStatusAsyncSensor to AzureDataFactoryPipelineRunStatusSensor
…eRunStatusSensor when its deferrable attribute is set to True
Lee-W
force-pushed
the
merge-AzureDataFactoryPipelineRunStatusAsyncSensor-into-AzureDataFactoryPipelineRunStatusSensor
branch
from
18e8a85 to
bbfcaaf
Compare
…eRunStatusSensor deferrable mode and deprecate AzureDataFactoryPipelineRunStatusAsyncSensor
Lee-W
force-pushed
the
merge-AzureDataFactoryPipelineRunStatusAsyncSensor-into-AzureDataFactoryPipelineRunStatusSensor
branch
from
bbfcaaf to
8121f18
Compare
uranusjr
approved these changes
Mar 29, 2023
potiuk
approved these changes
Mar 29, 2023
64 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Why making this change?
apache-airflow-providers-microsoft-azure treats the deferred execution of its operators and sensors differently, which might cause confusion. For example, AzureDataFactoryRunPipelineOperator uses the deferrable parameter to toggle deferred execution while we need to use another sensor for AzureDataFactoryPipelineRunStatusSensor (i.e., AzureDataFactoryPipelineRunStatusAsyncSensor) to achieve the same thing.
What's changed?
In this pull request, I move the deferred logic from AzureDataFactoryPipelineRunStatusAsyncSensor to AzureDataFactoryPipelineRunStatusSensor so that we can keep the consistency and reduce maintenance effort. Instead of removing AzureDataFactoryPipelineRunStatusAsyncSensor, I add a deprecation warning in case there're users using it.
^ 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.