[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020137#comment-16020137
]
Colin P. McCabe commented on KAFKA-5275:
----------------------------------------
I can imagine clients handling some types of exceptions. For example, an
{{InvalidConfigurationException}} includes the name of the unknown
configuration key, so you could strip that configuration key off and retry.
Maybe you don't care about {{TopicExistsException}}, so you log that and ignore
it. If you get a subclass of {{RetriableException}}, you can retry at the
application level (these are nearly always fallout from network issues which
could be transitory.) If you get {{AuthenticationException}}, you might want
to display a nicer message to the user. Of course, {{UnknownServerException}}
really is unhandleable, but it also shouldn't happen that often.
> Review and potentially tweak AdminClient API for the initial release (KIP-117)
> ------------------------------------------------------------------------------
>
> Key: KAFKA-5275
> URL: https://issues.apache.org/jira/browse/KAFKA-5275
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Fix For: 0.11.0.0
>
>
> Once all the pieces are in, we should take a pass and ensure that the APIs
> work well together and that they are consistent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
