-
Notifications
You must be signed in to change notification settings - Fork 15.3k
Replace models.BaseOperator
to Task SDK one for Standard Provider
#52292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not only for standard operator?
BTW, if you want, you can create a template PR (this one) and we can drive it provider by provider lead by the community!
Yeah, that's the plan. I am uncovering few things as part of this exercise. So will wrap it up into a good AI-workable issue too :) |
ed8418f
to
9fa8d98
Compare
The Providers should use the BaseOperator from Task SDK for Airflow 3.0+.
5162a63
to
50af153
Compare
Follow-up of apache#52292 for Alibaba & Airbyte
Follow-up of apache#52292 for Alibaba & Airbyte
Follow-up of apache#52292 for Asana & Arangodb
Follow-up of apache#52292 for Asana & Arangodb
Follow-up of apache#52292 for Asana & Arangodb
The Providers should use the BaseOperator from Task SDK for Airflow 3.0+.
^ 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.rst
or{issue_number}.significant.rst
, in airflow-core/newsfragments.