Philip Nee 4e0578fb81 KAFKA-16156: beginningOrEndOffsets does not need to build an OffsetAndTimestamps object upon completion (#15525) ... A subtle difference in the behavior of the two API causes the failures with Invalid negative timestamp. In this PR, the list offsets response will be processed differently based on the API. For beginingOffsets/endOffsets - the offset response should be directly returned. For offsetsForTimes - A OffsetAndTimestamp object is constructed for each requested TopicPartition before being returned. The reason beginningOffsets and endOffsets - We are expecting a -1 timestamp from the response which subsequently causes the invalid timestamp exception because the original code tries to construct an OffsetAndTimestamp object upon returning. In this PR, the following missing tasks are added: short-circuit both beginningOrEndOffsets Test both API (beginningOrEndOffsets, OffsetsForTime) Seems like we don't have tests for this API: Note it is presented in other IntegrationTests but they are added to test Async consumer Reviewers: Lucas Brutschy <lbrutschy@confluent.io>, Lianet Magrans <lianetmr@gmail.com>		2024-04-08 13:04:58 +02:00
..
src	KAFKA-16156: beginningOrEndOffsets does not need to build an OffsetAndTimestamps object upon completion (#15525)	2024-04-08 13:04:58 +02:00
.gitignore	KAFKA-4848: Fix retryWithBackoff deadlock issue	2017-03-20 21:56:15 -07:00