Open pmw-rp opened 4 months ago
Note this is KIP-734, introduced in Kafka 3.0. The client can use -3 to request the max timestamp.
While at it we should also address KIP-405, introduced in Kafka 3.4. The client can use -4 to request the local log start offset (in the context of tiered storage; we already have this information available via the admin API).
This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the stale
label – otherwise this will be closed in two weeks.
Version & Environment
23.3
What went wrong?
When calling listOffsets() with OffsetSpec.maxTimestamp() (to determine the timestamp of the latest message), I received the following:
What should have happened instead?
A valid ListOffsetsResult object is returned, containing the timestamp of the latest message.
How to reproduce the issue?
Additional information
JIRA Link: CORE-2345