[
https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760531#comment-17760531
]
Chris Egerton edited comment on KAFKA-12879 at 8/30/23 7:27 PM:
----------------------------------------------------------------
Looks like this behavior change has resurfaced in
[https://github.com/apache/kafka/pull/13432|https://github.com/apache/kafka/pull/13432],
which has not been included in a release yet. I've reopened the ticket,
upgraded it to a blocker, and given it a fix version of 3.6.0.
[~rhauch] [~tombentley] [~cmccabe] [~ijuma] [~dajac] [~dengziming]
[~dimitarndimitrov] Do we want to continue to preserve this behavior? If so, we
should move quickly to get a fix merged in time for the upcoming 3.6.0 release.
was (Author: chrisegerton):
Looks like this behavior change has resurfaced in
[https://github.com/apache/kafka/pull/13432|https://github.com/apache/kafka/pull/13432.],
which has not been included in a release yet. I've reopened the ticket,
upgraded it to a blocker, and given it a fix version of 3.6.0.
[~rhauch] [~tombentley] [~cmccabe] [~ijuma] [~dajac] [~dengziming]
[~dimitarndimitrov] Do we want to continue to preserve this behavior? If so, we
should move quickly to get a fix merged in time for the upcoming 3.6.0 release.
> Compatibility break in Admin.listOffsets()
> ------------------------------------------
>
> Key: KAFKA-12879
> URL: https://issues.apache.org/jira/browse/KAFKA-12879
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 2.8.0, 2.7.1, 2.6.2, 3.6.0
> Reporter: Tom Bentley
> Assignee: Chris Egerton
> Priority: Blocker
> Fix For: 2.5.2, 2.8.2, 3.2.0, 3.1.1, 3.0.2, 2.7.3, 2.6.4, 3.6.0
>
>
> KAFKA-12339 incompatibly changed the semantics of Admin.listOffsets().
> Previously it would fail with {{UnknownTopicOrPartitionException}} when a
> topic didn't exist. Now it will (eventually) fail with {{TimeoutException}}.
> It seems this was more or less intentional, even though it would break code
> which was expecting and handling the {{UnknownTopicOrPartitionException}}. A
> workaround is to use {{retries=1}} and inspect the cause of the
> {{TimeoutException}}, but this isn't really suitable for cases where the same
> Admin client instance is being used for other calls where retries is
> desirable.
> Furthermore as well as the intended effect on {{listOffsets()}} it seems that
> the change could actually affect other methods of Admin.
> More generally, the Admin client API is vague about which exceptions can
> propagate from which methods. This means that it's not possible to say, in
> cases like this, whether the calling code _should_ have been relying on the
> {{UnknownTopicOrPartitionException}} or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
