gosonzhang opened a new issue, #8142: URL: https://github.com/apache/inlong/issues/8142
### Description Adjust the operation mode of topic metadata and mq cluster information, currently there are two ways to obtain the mapping relationship between groupId/streamId and topic, and metadata information such as MQ cluster: getConfig and getAllConfig, these two methods save metadata in different , and use different logic to interact with the Manager to get the latest configuration. Through the analysis of the two methods, the design of getAllConfig is more in line with the requirements of online use. Only the metadata update request response will carry the full amount of metadata, at the same time, the response structure is easier to expand, but the configuration loading mode is not friendly to use: the metadata configuration is carried through the dataproxy.conf file, this kind of different configurations is mixed together, which is not convenient for system maintenance. The problem with the getConfig method is that the scalability of the response structure is not good enough, every request will return the full amount of metadata, regardless of whether the metadata changes. Adjust this part in this issue: use getAllConfig as the only metadata configuration acquisition method, save metadata in a separate configuration file, adjust the acquisition and processing logic of Topic and MQ cluster information, and remove the implementation logic of the original getConfig and getAllConfig methods ### InLong Component InLong DataProxy ### Are you willing to submit PR? - [X] Yes, I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
