[
https://issues.apache.org/jira/browse/KAFKA-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051203#comment-15051203
]
ASF GitHub Bot commented on KAFKA-2578:
---------------------------------------
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/659
KAFKA-2578; Client Metadata internal state should be synchronized
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka KAFKA-2578
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/659.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 #659
----
commit 938a19a7a09238d7f6089a7a75d613fc33dd7ce3
Author: Edward Ribeiro <[email protected]>
Date: 2015-09-29T21:23:19Z
KAFKA-2578; Client Metadata internal state should be synchronized
----
> Client Metadata internal state should be synchronized
> -----------------------------------------------------
>
> Key: KAFKA-2578
> URL: https://issues.apache.org/jira/browse/KAFKA-2578
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Edward Ribeiro
> Priority: Trivial
>
> Some recent patches introduced a couple new fields in o.a.k.clients.Metadata:
> 'listeners' and 'needMetadataForAllTopics'. Accessor methods for these fields
> should be synchronized like the rest of the internal Metadata state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
