You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by MayureshGharat <gi...@git.apache.org> on 2016/09/27 03:23:24 UTC

[GitHub] kafka pull request #1913: KAFKA-3175 (Rebased) : topic not accessible after ...

GitHub user MayureshGharat opened a pull request:

    https://github.com/apache/kafka/pull/1913

    KAFKA-3175 (Rebased) : topic not accessible after deletion even when delete.topic.enable is disabled

    Rebased the patch with current trunk.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/MayureshGharat/kafka kafka-3175_latest

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1913.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1913
    
----
commit 3b4412eb948318ac8fbea855ff52071bbb6f8fb3
Author: MayureshGharat <gh...@gmail.com>
Date:   2016-02-01T21:51:57Z

    Remove topics under /admin/delete_topics path in zk if deleteTopic is disabled. The topic should never be enqueued for deletion

commit 1bf29ae00da0eaa0044bdc1bb8dc6cc80ee90951
Author: MayureshGharat <gh...@gmail.com>
Date:   2016-03-11T17:25:32Z

    Addressed Jun's comment to clean the zk state for a topic on cluster restart and delete topic disabled

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---