Change DataInKeySpacePath to contain a KeySpacePath instead of ResolvedKeySpacePath #3716
+100
−356
Conversation
This file contains hidden or 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
…edKeySpacePath It was unnecessary to have the ResolvedKeySpacePath, and we want to be able to import into a different cluster, where the resolved values are different from the exported data. This means that DataInKeySpacePath has a few more fields, but makes it more versatile going forward.
ScottDugas
commented
Nov 3, 2025
|
|
||
| public CompletableFuture<ResolvedKeySpacePath> getResolvedPath() { | ||
| return resolvedPath; | ||
| this.value = value; |
There was a problem hiding this comment.
Instead of copying the byte[] here and in getValue, I created an issue to convert it to ByteString: #3717
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It was unnecessary to have the ResolvedKeySpacePath, and we want to be able to import into a different cluster, where the resolved values are different from the exported data.
This means that DataInKeySpacePath has a few more fields, but makes it more versatile going forward.
This also changes
exportAllDatato usemapPipelinedto resolve the path, so thatDataInKeySpacePathdoes not contain a future.This is in support of #3573