[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017626#comment-16017626
]
Colin P. McCabe commented on KAFKA-5275:
----------------------------------------
bq. [~rhauch]: Also, a common use case for creating topics is going to be
"create new topic(s) if they don't already exist". The current AdminClient can
do this, but it requires a fair amount of error handling, especially when
trying to create multiple topics at once.
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...
bq. it would be nice to have a default describeTopics() that doesn't need a
list of topics and just returns the description for all topics, right now i
have to do
adminClient.describeTopics(a.listTopics().names().get()).all().get(); :/
The intention here was to encourage people to fetch a few topics at a time,
since we don't currently have very scalable ways of fetching all topics.
KIP-142 will help here.
Of course, sometimes you really do need to fetch every single topic in the
cluster. We probably should have some nicer way of doing this. Perhaps it
could do batching in the AdminClient.
> 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)
