Add storage address mapping transform #589
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Nicole00
force-pushed
the
storage_address_mapping
branch
from
0576e90
to
75c8b6e
Compare
|
@awang12345 Hi, I am advancing this PR, can you confirm your email and sign the following cla for jiangyiwang-jk? |
The name jiangyiwang-jk is wrong.The correct name is wang12345 |
I don't know how to change this wrong name |
Don't worry, the cla has passed. |
Nicole00
approved these changes
Jul 5, 2024
Nicole00
added a commit
that referenced
this pull request
Jul 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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