[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017701#comment-16017701
]
Randall Hauch commented on KAFKA-5275:
--------------------------------------
[~colinmccabe] wrote:
{quote}
We could add an option to {{CreateTopicsOptions}} that suppresses
{{TopicExistsException}} in the results. I guess the question is, does your
code want to at least log something when a topic already exists rather than
getting created, since the configuration options will potentially be
different...
{quote}
Kafka Connect does log which topics were created and which were found. That'd
be trivial if {{CreateTopicResults}} had methods to return the names of the
newly-created and existing topics -- perhaps something like:
{code:java}
KafkaFuture<Set<String>> createdTopicNames() {...}
KafkaFuture<Set<String>> existingTopicNames() {...}
{code}
[~xvrl] wrote:
{quote}
However, we should also define constants for every topic configuration option
that exists.
{quote}
Yes, and ideally the NewTopic builder might even have some convenience methods
that saved having to use some of them.
> 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)
