Fix deprecations into the GCP Dataproc links #36834
Merged
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
potiuk
reviewed
Jan 17, 2024
potiuk
approved these changes
Jan 17, 2024
hussein-awala
approved these changes
Jan 17, 2024
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.
Related:
warnings.warnraised every time when moduleairflow.providers.google.cloud.links.dataprocimported, so this warnings should be implemented inside of the__attrs_post_init__method.DataprocListLinkhas no any references into the Community Providers, that mean we could keep deprecationsDataprocLinkhas 3 references into the Operators, so we can't deprecate this link until we replace/remove this link into the operators:DataprocJobBaseOperator(all classes based on this operator are deprecated)DataprocScaleClusterOperator(operator deprecated)DataprocSubmitPigJobOperator(operator deprecated)cc: @bkossakowska
^ 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.