[filesystem] Correct the gson dependency after rolling back from jindo sdk to oss sdk #2516
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
JingsongLi
approved these changes
Dec 17, 2023
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.
Purpose
When rolling back oss sdk from jindo sdk to the old one through #2435 we missed to roll back the gson related dependency, and this PR aims to fix this up. More details refer to #2290
Tests
Manually test and make sure the
META-INF/NOTICEfile correctly reflect the dependencies of thepaimon-filesystems/paimon-oss-implandpaimon-filesystems/paimon-hadoop-shadedmodules.API and Format
No API or storage format change involved.
Documentation
No documentation required.