[SPARK-51712][SQL] Swallow non-fatal Throwables when resolving tables/views in spark.catalog.listTables() #50515
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
heyihong
changed the title
heyihong
changed the title
heyihong
force-pushed
the
SPARK-51712
branch
2 times, most recently
from
43d0f7d to
b7c40e5
Compare
heyihong
changed the title
HyukjinKwon
reviewed
Apr 7, 2025
sql/core/src/main/scala/org/apache/spark/sql/classic/Catalog.scala
Outdated
Show resolved
Hide resolved
… in spark.catalog.listTables()
cloud-fan
approved these changes
Apr 7, 2025
HyukjinKwon
approved these changes
Apr 7, 2025
|
Merged to master. |
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?
Swallow non-fatal Throwables when resolving tables/views in spark.catalog.listTables() and return tables/views with partial results instead
Why are the changes needed?
Prevent listTables from breaking easily due to a broken table/view.
Does this PR introduce any user-facing change?
No, but listTables won't break easily.
How was this patch tested?
Existing tests (e.g. HiveDDLSuite)
Was this patch authored or co-authored using generative AI tooling?
No