[
https://issues.apache.org/jira/browse/KAFKA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-500:
--------------------------------
Attachment: kafka-500-v1.patch
1. Created java apis for TopicMetadataRequest and TopicMetadataResponse.
2. Added a send(topicMetadataRequest) method in javaapi/SyncProducer.
3. Created unit tests to make sure that the underlying object is correctly
created for javaapi/TopicMetadataRequest and javaapi/TopicMetadataResponse.
(Are they an overkill?)
4. Removed detailedMetadata, timestamp and count from TopicMetadataRequest as
those fields were not being used anywhere.
5. Refactored kafka.api.TopicMetaDataResponse to TopicMetadataResponse. Sorry,
this patch will touch a couple of more files.
> javaapi support for getTopoicMetaData
> -------------------------------------
>
> Key: KAFKA-500
> URL: https://issues.apache.org/jira/browse/KAFKA-500
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: bugs
> Fix For: 0.8
>
> Attachments: kafka-500-v1.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> TopicMetaRequest and TopicMetaResponse use scala Seq and Option. We need a
> version so that java applications can use more easily.
--
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
