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

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

GitHub user ijuma opened a pull request:

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

    KAFKA-3402; Restore behaviour of MetadataCache.getTopicMetadata when 
unsupported security protocol is received

    

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

    $ git pull https://github.com/ijuma/kafka 
kafka-3402-restore-get-topic-metadata-behaviour

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

    https://github.com/apache/kafka/pull/1073.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 #1073
    
----
commit f314f180dae4a80a2b47120e6188137bf679ff7e
Author: Ismael Juma <ism...@juma.me.uk>
Date:   2016-03-15T14:11:53Z

    Restore behaviour of MetadataCache.getTopicMetadata when unsupported 
security protocol is received

----


> Restore behaviour of MetadataCache.getTopicMetadata when unsupported security 
> protocol is received
> --------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3402
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3402
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>            Priority: Critical
>             Fix For: 0.10.0.0
>
>
> The behaviour of `MetadataCache.getTopicMetadata` when a security protocol 
> that is not supported by a broker is passed as a parameter was to throw 
> BrokerEndpointNotAvailableException until 
> https://github.com/apache/kafka/commit/764d8ca9eb0aba6099ba289a10f437e72b53ffec
>  when it was accidentally changed to return a response with error code 
> `LeaderNotAvailable` or `ReplicaNotAvailable`.
> The right behaviour is probably to return a new error code, but in the 
> meantime we should restore the existing behavior and add some tests.
> This issue was found by [~hachikuji].



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

Reply via email to