Feature/refactor azure synapse pipeline class - #38723
Merged
eladkal merged 7 commits intoApr 4, 2024
Merged
Conversation
boring-cyborg
Bot
added
area:providers
provider:microsoft-azure
eladkal
reviewed
Apr 3, 2024
romsharon98
force-pushed
the
feature/refactor-azure-synapse-pipeline
branch
from
April 4, 2024 12:37
7d656f6 to
ec418c0
Compare
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
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.
This PR intends to:
Introduce BaseAzureSynapseClass as the parent class for better code maintainability in Azure Synapse Hooks.
The base class will manage the common connection form, enabling child classes to inherit and share this connection form while implementing individual functionalities.
Add managed identity support to DefaultAzureCredential.
redo stale PR: #36622
^ 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.