-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Fix consistent return response from PubSubPullSensor #42080
Fix consistent return response from PubSubPullSensor #42080
Conversation
681799f
to
111c632
Compare
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.
Looks great! Thanks for making the immediate modifications.
One thing I just think of @eladkal do you think it's a breaking change? as we change the trigger here |
IMHO we can treat it as a bugfix. |
But it would be nice to add a note at the top of the CHANGELOG explaining the change expected. |
Yep, it sounds more like a bug fix to me, but I would like to be cautious. I'll merge it later today if no one object. |
* fix consistent return response pubsubsensor * removed messages_callback argument to pubsub trigger and using it in execute_complete * updated variable name * updates as per comments, added return types and refactored logic * update types, tests and use inherit exception
* fix consistent return response pubsubsensor * removed messages_callback argument to pubsub trigger and using it in execute_complete * updated variable name * updates as per comments, added return types and refactored logic * update types, tests and use inherit exception
closes: #41877
^ 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 newsfragments.