[jira] [Updated] (TUBEMQ-470) Add query API of TopicName and BrokerId collection

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TUBEMQ-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated TUBEMQ-470:
----------------------------------
    Labels: pull-request-available  (was: )

> Add query API of TopicName and BrokerId collection
> --------------------------------------------------
>
>                 Key: TUBEMQ-470
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-470
>             Project: Apache TubeMQ
>          Issue Type: Sub-task
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, the Master Web API has detailed query APIs for topic and broker meta info. If we only need to query the TopicName field information, or view the BrokerId collection information, the existing interface is very bloated, and a convenient api is needed to obtain these information.
>  
> Currently, the Master Web API has detailed query APIs for topic and broker meta info. If we only need to query the TopicName field information, or view the BrokerId collection information, the existing interface is very bloated, and a convenient api is needed to obtain these information.
> For example, I configured topic1, topic2 on broker-a, topic2, topic3 on broker-b, topic1, topic3, topic3 on broker-c. I can get the topic distribution details on the broker by querying the topicName api:
> broker-a: [topic1, topic2],
> broker-b: [topic2, topic3],
> broker-c: [topic1, topic2, topic3].
> and, we can get the broker deployment information for each topic through brokerId api:
> topic1: [broker-a, broker-c]
> topic2: [broker-a, broker-b, broker-c]
> topic3: [broker-b, broker-c]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)