When scanning with storageClient, the storage address obtained from meta may not be used directly, such as 127.0.0.1. The code executed must be used with the storage service, but often the business code and the nebula server are not on the same machine or the same network segment. This results in the inability to scan the data using storageClient
How do you solve it?
StorageClient initializes the Address translation relationship, and then MateManger returns address translation
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Because of runing the local nebula-client exception, the code did not run the unit tests
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
Description:
When scanning with storageClient, the storage address obtained from meta may not be used directly, such as 127.0.0.1. The code executed must be used with the storage service, but often the business code and the nebula server are not on the same machine or the same network segment. This results in the inability to scan the data using storageClient
How do you solve it?
StorageClient initializes the Address translation relationship, and then MateManger returns address translation
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Because of runing the local nebula-client exception, the code did not run the unit tests