[
https://issues.apache.org/jira/browse/KAFKA-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934290#comment-14934290
]
Edward Ribeiro edited comment on KAFKA-2578 at 9/29/15 9:36 PM:
----------------------------------------------------------------
Thanks!
[~jasong35], Hi, Jason! When I pushed to the github repo I forgot to prefix it
with the "KAFKA-XXX" number, and even after doing a {{commit --amend}} the
asfbot didn't pick it up to show here on the JIRA. :( I tried to close and open
and the PR, but no success either.
Nevertheless, the PR is at:
https://github.com/apache/kafka/pull/263
was (Author: eribeiro):
Thanks!
[~jasong35], Hi, Jason! When I pushed to the github repo I forgot to prefix it
with the "KAFKA-XXX" number, and even after doing a {{commit --amend}} the
asfbot didn't pick it up to show here on the JIRA. Nevertheless, the PR is at:
https://github.com/apache/kafka/pull/263
> 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)
