You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2012/09/27 03:21:07 UTC
[jira] [Resolved] (KAFKA-473) Use getMetadata Api in
ZookeeperConsumerConnector
[ https://issues.apache.org/jira/browse/KAFKA-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao resolved KAFKA-473.
---------------------------
Resolution: Fixed
+1 on patch v4. Committed to 0.8.
> Use getMetadata Api in ZookeeperConsumerConnector
> -------------------------------------------------
>
> Key: KAFKA-473
> URL: https://issues.apache.org/jira/browse/KAFKA-473
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Assignee: Yang Ye
> Priority: Blocker
> Labels: newbie, optimization
> Fix For: 0.8
>
> Attachments: kafka_473_v1.diff, kafka_473_v2.diff, kafka_473_v3.diff, kafka_473_v4.diff
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Currently, ZookeeperConsumerConnector gets topic metadata from ZK directly. It's better to use the getMetadata Api since it's batched. This is especially helpful if the consumer client is in a different data center.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira