HDDS-14939. Implement version file rewrite logic for path migration across metadata history#10067
Open
sreejasahithi wants to merge 5 commits intoapache:masterfrom
Open
HDDS-14939. Implement version file rewrite logic for path migration across metadata history#10067sreejasahithi wants to merge 5 commits intoapache:masterfrom
sreejasahithi wants to merge 5 commits intoapache:masterfrom
Conversation
added 2 commits
April 10, 2026 15:31
…cross metadata history
d830800 to
74d4ff2
Compare
Contributor
ashishkumar50
left a comment
There was a problem hiding this comment.
@sreejasahithi Thanks for working on this. Please find the comments inline.
Also can you create a utility class and put common methods there instead adding everything in the same class.
Contributor
ashishkumar50
left a comment
There was a problem hiding this comment.
@sreejasahithi overall LGTM, some minor nits.
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
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 changes were proposed in this pull request?
This change implements the logic to rewrite table metadata version files across the metadata history, enabling path migration from a source prefix to a target prefix.
Traversal should start from the provided endMetadata (current or specified version) and iterate backwards through previous metadata version files until reached the startVersion provided if any(if not then till beginning). We also need to collect all the snapshots from each traversed historical metadata version.
For each metadata version file we can take help of iceberg's RewriteTablePathUtil to rewrite absolute file paths in it from sourcePrefix -> targetPrefix and then we have to add the rewritten file to the staging location.
We should also update copy plan with staging -> final path mappings for each metadata version file rewritten.
What is the link to the Apache JIRA
HDDS-14939
How was this patch tested?
Added test cases
Green CI:
https://github.com/sreejasahithi/ozone/actions/runs/24237563462