[
https://issues.apache.org/jira/browse/KAFKA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101076#comment-14101076
]
Krzysztof Szafrański commented on KAFKA-1123:
---------------------------------------------
1. I agree that parseAndValidateAddress() could reuse ClientUtils (though it
implies dealing with Tuple2 in Java).
2. InetSocketAddress can take the address without the square braces, but my
intention with addressString() was to propagate this notation throughout the
system. And as for the standard it would be RFC 2732
(http://www.ietf.org/rfc/rfc2732.txt).
> Broker IPv6 addresses parsed incorrectly
> ----------------------------------------
>
> Key: KAFKA-1123
> URL: https://issues.apache.org/jira/browse/KAFKA-1123
> Project: Kafka
> Issue Type: Bug
> Components: producer
> Affects Versions: 0.8.2
> Reporter: Andrew Otto
> Labels: newbie
> Attachments: KAFKA-1123.patch
>
>
> It seems that broker addresses are parsed incorrectly when IPv6 addresses are
> supplied. IPv6 addresses have colons in them, and Kafka seems to be
> interpreting the first : as the address:port separator.
> I have only tried this with the console-producer --broker-list option, so I
> don't know if this affects anything deeper than the CLI.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
