Merged
Conversation
geruh
approved these changes
Sep 4, 2025
Contributor
There was a problem hiding this comment.
This looks good to me @rambleraptor! It aligns with the removal in java library just needs a rebase
Can you take a look @kevinjqliu
Contributor
|
@rambleraptor could you rebase and resolve the conflicts here? |
rambleraptor
force-pushed
the
remove-schemas
branch
from
9a9a9f0 to
55b0478
Compare
Contributor
Author
|
@kevinjqliu rebased! |
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
3 participants
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.
Rationale for this change
This is the last non-view related TableMetadata update event missing from Java. It allows users to remove schemas, as long as they exist and aren't the default.
Are these changes tested?
Added unit tests.
Are there any user-facing changes?