[
https://issues.apache.org/jira/browse/KAFKA-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198387#comment-15198387
]
ASF GitHub Bot commented on KAFKA-3402:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1073
> 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)
