fix: support UNCACHE TABLE IF EXISTS in Spark 3.3+#98
Open
yuanoOo wants to merge 2 commits intooceanbase:mainfrom
Open
fix: support UNCACHE TABLE IF EXISTS in Spark 3.3+#98yuanoOo wants to merge 2 commits intooceanbase:mainfrom
yuanoOo wants to merge 2 commits intooceanbase:mainfrom
Conversation
Add table existence check in loadTable method to support UNCACHE TABLE IF EXISTS syntax introduced in Spark 3.3+
Implemented a new test case in OBCatalogMySQLITCase to verify the behavior of the UNCACHE TABLE IF EXISTS command. The test checks both scenarios: when the table exists and when it does not, ensuring that no exceptions are thrown in either case. This enhances the test coverage for Spark 3.3+ features.
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
1 participant
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.
Summary
This PR adds support for the `UNCACHE TABLE IF EXISTS` syntax introduced in Spark 3.3+.
Changes
Testing
The change ensures that when `UNCACHE TABLE IF EXISTS` is executed, the catalog properly checks if the table exists before attempting to load it, preventing unnecessary errors when the table does not exist.