RANGER-4914: Tagsync support for Ozone OFS paths #385
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
fateh288
force-pushed
the
RANGER-4914
branch
from
1debaa5
to
bad1f24
Compare
mneethiraj
approved these changes
Sep 12, 2024
mneethiraj
pushed a commit
that referenced
this pull request
Sep 20, 2024
(cherry picked from commit 6b77713)
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?
OFS support in tagsync allowing OFS entities to be tagged in Atlas.
Currently only o3fs entities are supported.
Various configurations such as reverting to old behavior or configuring a custom delimiter for key or bucket have been added for future fixes when done by atlas.
Limitations of the patch:
No "." in volume name (this is because of how atlas is creating qualifiedName for ofs bucket entites)
How was this patch tested?
Unit tests have been added for the addressed scenarios. Manual testing in cluster was also done.