[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

2017-07-17 Thread Stevo Slavic (JIRA) 

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

Stevo Slavic commented on KAFKA-1694:
-

Thanks for providing Java AdminClient. While migrating from Scala 
{{AdminUtils}} to Java {{AdminClient}} I noticed that in the new Java one there 
is no {{topicExists}} API support other than listing all topics and doing the 
search locally in memory.

Are there plans already and if not would it make sense to add {{topicExists}} 
to the Java AdminClient and matching Kafka broker API?

> 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, KAFKA-1772_1802_1775_1774_v2.patch
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

2017-07-17 Thread Ismael Juma (JIRA) 

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

Ismael Juma commented on KAFKA-1694:


[~sslavic], `AdminUtils` is communicating with ZooKeeper directly. The broker 
doesn't currently expose a protocol API that just checks if a topic exists. We 
are currently planning to make `listTopics` more efficient, but no immediate 
plans for a topic exists protocol API. Is there a use case where this is 
important?

> 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, KAFKA-1772_1802_1775_1774_v2.patch
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

2017-07-17 Thread Stevo Slavic (JIRA) 

[ 
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, KAFKA-1772_1802_1775_1774_v2.patch
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

2017-07-19 Thread Ismael Juma (JIRA) 

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

Ismael Juma commented on KAFKA-1694:


Is the intent to create the topic if it doesn't exist? In that case, you can 
just call createTopics and if the error states that it already exists, you're 
good.

> 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, KAFKA-1772_1802_1775_1774_v2.patch
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KAFKA-1694) KIP-4: Command line and centralized operations

2018-01-04 Thread Felix GV (JIRA) 

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

Felix GV commented on KAFKA-1694:
-

[~ijuma],

Because delete topic is asynchronous, it is useful to have a way of knowing 
when the deletion process is completed properly. Currently, we do an extensive 
series of checks to verify this, but a lightweight approach would be 
preferable. Obviously, calling createTopics is not an appropriate way of 
checking if delete topic finished. This particular issue could be side-stepped 
by providing a first-class synchronous topic deletion API, but at the end of 
the day, it's probably useful to have a proper topic existence API regardless. 
The challenge, I suppose, is that this is not a binary state, but rather a 
gradient. The valid responses might be something along the lines of:

# EXISTS
# DOES_NOT_EXIST
# CREATION_IN_PROGRESS
# DELETION_IN_PROGRESS.

-F

> 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.patch, 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-1772_1802_1775_1774_v2.patch
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)