Relocate SmoothOperator to standard provider and add tests #47530
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
shahar1
force-pushed
the
relocate-smooth-operator
branch
2 times, most recently
from
95de1c1 to
774c712
Compare
shahar1
force-pushed
the
relocate-smooth-operator
branch
from
774c712 to
5a49e9b
Compare
potiuk
approved these changes
Mar 8, 2025
Member
potiuk
left a comment
potiuk
left a comment
There was a problem hiding this comment.
❤️ ... @turbaszek ..... Smooth Operator lives forever - even in Airlflow 3
Member
And it's even tested now :D |
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.
Now that we relocate ShortCircuit and Branch operators to the standard provider, our beloved SmoothOperator might remain alone in
airflow/operators. Considering the fact that it also executes logic (similar to the other standard operators), I thought that it would be appropriate to relocate it as well :)^ 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.