You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, after DataProxy pulls the metadata from Manager, it directly saves the response message DataProxyConfigResponse returned by Manager in the metadata.json file, and re-parses the DataProxyConfigResponse object when loading the metadata.
It is found during use that every time the metadata is loaded, DataProxy needs to perform content checks, and it is not convenient for DataProxy to save additional information in the saved metadata. For this reason, in this PR, I added a new class InLongMetaConfig to save the metadata information of DataProxy specifically.
Description
The parent issue:#10080
Currently, after DataProxy pulls the metadata from Manager, it directly saves the response message DataProxyConfigResponse returned by Manager in the metadata.json file, and re-parses the DataProxyConfigResponse object when loading the metadata.
It is found during use that every time the metadata is loaded, DataProxy needs to perform content checks, and it is not convenient for DataProxy to save additional information in the saved metadata. For this reason, in this PR, I added a new class InLongMetaConfig to save the metadata information of DataProxy specifically.
InLong Component
InLong DataProxy
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: