[#6147] improve(CLI): Refactor fileset commands in Gavitino CLI #6191
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
TungYuChiang
changed the title
|
@TungYuChiang the changes look good to me, you'll just have to fix the conflicts. |
TungYuChiang
force-pushed
the
refactor/fileset
branch
from
21d4244 to
079e3f2
Compare
TungYuChiang
force-pushed
the
refactor/fileset
branch
from
079e3f2 to
4c7df5b
Compare
Abyss-lord
pushed a commit
to Abyss-lord/gravitino
that referenced
this pull request
Jan 14, 2025
apache#6191) ### What changes were proposed in this pull request? Refactor fileset commands in cli client ### Why are the changes needed? Fix: apache#6147 ### Does this PR introduce _any_ user-facing change? None ### How was this patch tested? Tested locally
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?
Refactor fileset commands in cli client
Why are the changes needed?
Fix: #6147
Does this PR introduce any user-facing change?
None
How was this patch tested?
Tested locally