Core: Enable metadata tables support for REST scan planning#14881
Merged
Conversation
nastra
approved these changes
Dec 18, 2025
nastra
left a comment
nastra
left a comment
Contributor
There was a problem hiding this comment.
makes sense to fallback to a non-REST table with metadata tables
sfc-gh-prsingh
force-pushed
the
metadata-only
branch
from
f67e4b1 to
5bc192c
Compare
huaxingao
approved these changes
Dec 18, 2025
dramaticlly
approved these changes
Dec 18, 2025
Contributor
Author
|
Thanks @nastra @huaxingao @dramaticlly for the reviews :) |
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
5 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.
About the change
This PR enables the metadata to be read by spark, check this commit f67e4b1 for exact fix
caught via #14822