use batch.num.messages config in KafkaGroupReadableResource::Next #1460
Conversation
This file contains 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
add test case for batch.num.messages
kvignesh1420
changed the title
|
cc: @yongtang |
dopiera
pushed a commit
to Unoperate/tensorflow_io
that referenced
this pull request
Dec 3, 2021
…nsorflow#1460) * use max.poll.records config in KafkaGroupReadableResource * switch to batch.num.messages add test case for batch.num.messages * fix failing kafka test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR addresses #1458 by allowing the users to set the number of records fetched from kafka per
next()onKafkaGroupIODatasetandKafkaBatchIODataset. (Defaults to 1024).