[
https://issues.apache.org/jira/browse/KAFKA-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-223.
-----------------------------
Resolution: Fixed
We have added an API like this in 0.8. It is described here:
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol
> Add metadata requests to Kafka broker
> -------------------------------------
>
> Key: KAFKA-223
> URL: https://issues.apache.org/jira/browse/KAFKA-223
> Project: Kafka
> Issue Type: Improvement
> Components: clients, core
> Reporter: David Ormsbee
> Priority: Minor
> Labels: features
>
> It would be useful to be able to query metadata from Kafka for the purposes
> of monitoring and discovery:
> 1. Version: Just a quick way to get the broker version so that we know not to
> send it a version of a request or response that it can't handle.
> 2. Topic information: Return the default number of partitions per topic, a
> list of all topics, number of partitions per topic if there are overrides,
> and start/end offsets for those topics (assuming it's cheap to do so). This
> would allow Consumers and Producers to discover topics and partitions on a
> single broker without involving ZooKeeper, and would also make it easier to
> know how many partitions can be sent to when making a new topic with a
> ZK-aware Producer.
> Discussed in thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kafka-dev/201112.mbox/%3CCALStshY02xT7b2n-%3DDjTF_QifEzjxWnCvmgRhSu8v8-ibbSGyQ%40mail.gmail.com%3E
--
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
