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

ASF GitHub Bot commented on KAFKA-4032:
---------------------------------------

GitHub user granthenke opened a pull request:

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

    KAFKA-4032: Uncaught exceptions when autocreating topics

    handled by adding a catch all for any unhandled exception. Because the jira 
specifically mentions the InvalidReplicationFactor exception, a test was added 
for that specific case.

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

    $ git pull https://github.com/granthenke/kafka create-errors

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

    https://github.com/apache/kafka/pull/1739.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 #1739
    
----
commit 6c85bcebf2e9ea96fbbfaf8eaab1b8d96ef160f5
Author: Grant Henke <granthe...@gmail.com>
Date:   2016-08-15T03:18:03Z

    KAFKA-4032: Uncaught exceptions when autocreating topics
    
    handled by adding a catch all for any unhandled exception. Because the jira 
specifically mentions the InvalidReplicationFactor exception, a test was added 
for that specific case.

----


> Uncaught exceptions when autocreating topics
> --------------------------------------------
>
>                 Key: KAFKA-4032
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4032
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: Jason Gustafson
>            Assignee: Grant Henke
>
> With the addition of the CreateTopics API in KIP-4, we have some new 
> exceptions which can be raised from {{AdminUtils.createTopic}}. For example, 
> it is possible to raise InvalidReplicationFactorException. Since we have not 
> yet removed the ability to create topics automatically, we need to make sure 
> these exceptions are caught and handled in both the TopicMetadata and 
> GroupCoordinator request handlers. Currently these exceptions are propagated 
> all the way to the processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to