[#145][#146] feat(client): add client side schema/table manipulation support #202
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
Code Coverage Report
Files
|
yuqi1129
reviewed
Aug 10, 2023
client-java/src/main/java/com/datastrato/graviton/client/RelationalCatalog.java
Show resolved
Hide resolved
client-java/src/main/java/com/datastrato/graviton/client/RelationalCatalog.java
Show resolved
Hide resolved
client-java/src/main/java/com/datastrato/graviton/client/ErrorHandlers.java
Outdated
Show resolved
Hide resolved
|
@yuqi1129 please help to review again. |
|
LGTM, I would merge it |
yuqi1129
approved these changes
Aug 10, 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.
What changes were proposed in this pull request?
This PR adds the support of schema and table operations for Graviton client.
Why are the changes needed?
With this, user could manipulate schema and tables through Java client.
Fix: #145
Fix: #146
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add new UTs to cover the code.