-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
KAFKA-19060 Documented null edge cases in the Clients API JavaDoc #19393
base: trunk
Are you sure you want to change the base?
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.
Thanks for the PR. I left one commment.
In your PR description has a typo:
beginningOffsets -> endOffsets
@@ -1658,7 +1660,8 @@ public Map<TopicPartition, Long> beginningOffsets(Collection<TopicPartition> par | |||
* @see #seekToEnd(Collection) | |||
* | |||
* @param partitions the partitions to get the end offsets. | |||
* @return The end offsets for the given partitions. | |||
* @return The end offsets for the given partitions. If the offset for a specific partition cannot be found or the | |||
* timeout is zero, the corresponding value will be {@code null} |
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.
Some paragraphs have periods, while others do not, for existing JavaDocs. I think we could make them all consistent (this can be addressed in another PR).
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.
Sure, but I won't address this changes in this PR.
Hello @kirktrue, if you have free cycle, PTAL |
Some client APIs may return
null
values in the map, but thisbehaviorisn’t documented in the JavaDoc. We should update the JavaDoc to
include these edge cases.
These method have been modified.