kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stevo Slavic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations
Date Mon, 17 Jul 2017 16:19:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090014#comment-16090014

Stevo Slavic commented on KAFKA-1694:

Here's one use case: with auto topic creation disabled, when trying to publish with KafkaProducer
to a topic that doesn't exist, one will get a timeout back - only way to differentiate is
the timeout caused by topic does not exist condition or any other issue I do now by issuing
topicExists check as followup to failed on timeout publish request.

Since auto topic creation can be disabled, all CRUD operations should be supported as minimum
through client APIs. Yes, this kind of check can already be done with list support and in
memory exist check. I see topicExists check as an optimization. With lots of topics, it's
handy to have this optimization available in Kafka's Java client APIs, and should be easy
to support so please consider adding it to Broker API and Java client.

> KIP-4: Command line and centralized operations
> ----------------------------------------------
>                 Key: KAFKA-1694
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1694
>             Project: Kafka
>          Issue Type: New Feature
>            Reporter: Joe Stein
>            Assignee: Grant Henke
>            Priority: Critical
>         Attachments: KAFKA-1694_2014-12-24_21:21:51.patch, KAFKA-1694_2015-01-12_15:28:41.patch,
KAFKA-1694_2015-01-12_18:54:48.patch, KAFKA-1694_2015-01-13_19:30:11.patch, KAFKA-1694_2015-01-14_15:42:12.patch,
KAFKA-1694_2015-01-14_18:07:39.patch, KAFKA-1694_2015-03-12_13:04:37.patch, KAFKA-1694.patch,
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements

This message was sent by Atlassian JIRA

View raw message