You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by jaikiran <gi...@git.apache.org> on 2017/05/13 12:26:10 UTC

[GitHub] kafka pull request #3043: KAFKA-5232 Fix Log.parseTopicPartitionName to take...

GitHub user jaikiran opened a pull request:

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

    KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot character in topic names of deleted topics

    The commit here contains a fix and testcase for the issue reported in https://issues.apache.org/jira/browse/KAFKA-5232, where if a topic marked for deletion, has a `.` character in its name then the Kafka broker fails to start and keeps shutting down

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

    $ git pull https://github.com/jaikiran/kafka KAFKA-5232

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

    https://github.com/apache/kafka/pull/3043.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 #3043
    
----
commit 512fc57e3fe9482d5b059bb2279a04a3640ccde5
Author: Jaikiran Pai <ja...@gmail.com>
Date:   2017-05-13T12:15:05Z

    KAFKA-5232 Fix the bug where the Log.parseTopicPartitionName wasn't taking into account the potential presence of '.' character in topic names while looking for topics that are marked for deletion

----


---
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.
---

[GitHub] kafka pull request #3043: KAFKA-5232 Fix Log.parseTopicPartitionName to take...

Posted by jaikiran <gi...@git.apache.org>.
Github user jaikiran closed the pull request at:

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


---
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.
---