[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020058#comment-16020058
]
Randall Hauch commented on KAFKA-5275:
--------------------------------------
[~cmccabe] wrote:
{quote}
Hmm. Methods like these, can't handle the case where there is an error other
than TopicExistsException. They have to throw an exception, and then you get no
information about any topic other than the one that had the exception. Can't
you just iterate through the map and do per-topic error handling? It just seems
like an easier and cleaner solution, unless there's something I'm missing.
{quote}
Yes, that's true that consumers don't really know how to handle any kind of
exception, so I would assume that they just log the exceptions and continue or
fail by rethrowing them. However, you're right that we wouldn't want to lose
any of the exceptions, so if we don't provide an exception handler or can't
aggregate them somehow into a single exception then we probably shouldn't offer
the capability to create topics this way.
> 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)
