listOffsets returns UnsupportedVersionException when using OffsetSpec.maxTimestamp()

[pmw-rp]

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:

Exception in thread "main" java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support LIST_OFFSETS with version in range [7,8]. The supported range is [0,4].
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
at Clean.lastProduced(Clean.java:60)
at Clean.main(Clean.java:97)
Caused by: org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support LIST_OFFSETS with version in range [7,8]. The supported range is [0,4].

What should have happened instead?

A valid ListOffsetsResult object is returned, containing the timestamp of the latest message.

How to reproduce the issue?

1. Create admin client
2. Query any topic-partition with OffsetSpec.maxTimestamp()
3. See the error message

Additional information

JIRA Link: CORE-2345

[twmb]

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).

[github-actions[bot]]

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.