-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Fixes the Kafka provider's max message limit error (#32926) #33321
Conversation
Fixes the issue(apache#32926) where kafka provider returns an error when max messages is not set since it keeps reading and messages left goes into negative.
Makes sure that the kafka provider works when max messages isn't passed into the operator
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.
The added test reproduces the reported issue, and the change fixes it. LGTM!
if not self.read_to_end: | ||
messages_left -= len(msgs) |
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.
Discussed and proposed in slack
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.
LGTM +1
…ache#33321) * Fixes kafka provider failing reading messages Fixes the issue(apache#32926) where kafka provider returns an error when max messages is not set since it keeps reading and messages left goes into negative. Makes sure that the kafka provider works when max messages isn't passed into the operator
The Kafka provider ConsumeFromTopicOperator throws
an error when max_messages is not set and there exist
more that a 1000 (Default value of max messages) messages
closes: #32926
^ 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.