[jira] [Commented] (KAFKA-5770) AdminClient.deleteTopics future complete but topic is still here
[ https://issues.apache.org/jira/browse/KAFKA-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167530#comment-16167530 ] Vincent Maurin commented on KAFKA-5770: --- The behavior haven't changed with version 0.11.0.1 > AdminClient.deleteTopics future complete but topic is still here > > > Key: KAFKA-5770 > URL: https://issues.apache.org/jira/browse/KAFKA-5770 > Project: Kafka > Issue Type: Bug > Components: clients >Reporter: Vincent Maurin > Attachments: Main.java > > > After running some tests, it appears that a deleteTopics command futures are > completed even if the topic is still present on the broker. > If it is the expected behavior, it should be documented accordingly, but it > is not very convenient for integration tests for example, when we create and > delete topics on each tests > I am attaching a example java file that creates and deletes a bunch of topic > in a loop. Usually I got an error on the second loop saying that the topic > already exists -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KAFKA-5770) AdminClient.deleteTopics future complete but topic is still here
[ https://issues.apache.org/jira/browse/KAFKA-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138120#comment-16138120 ] Vincent Maurin commented on KAFKA-5770: --- Also listing topics after deleting them shows a empty list. Maybe related to a bug on the broker like this one https://issues.apache.org/jira/browse/KAFKA-5752 > AdminClient.deleteTopics future complete but topic is still here > > > Key: KAFKA-5770 > URL: https://issues.apache.org/jira/browse/KAFKA-5770 > Project: Kafka > Issue Type: Bug > Components: clients >Reporter: Vincent Maurin > Attachments: Main.java > > > After running some tests, it appears that a deleteTopics command futures are > completed even if the topic is still present on the broker. > If it is the expected behavior, it should be documented accordingly, but it > is not very convenient for integration tests for example, when we create and > delete topics on each tests > I am attaching a example java file that creates and deletes a bunch of topic > in a loop. Usually I got an error on the second loop saying that the topic > already exists -- This message was sent by Atlassian JIRA (v6.4.14#64029)