[SPARK-45807][SQL] Improve ViewCatalog API #44330
Closed
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
|
@cloud-fan can you please review this one? This is related to #43677 (comment) |
nastra
force-pushed
the
SPARK-45807-api-improvements
branch
from
b26d181 to
48cc0b0
Compare
HyukjinKwon
reviewed
Dec 13, 2023
sql/catalyst/src/main/java/org/apache/spark/sql/connector/catalog/ViewInfo.java
Outdated
Show resolved
Hide resolved
nastra
force-pushed
the
SPARK-45807-api-improvements
branch
3 times, most recently
from
f7a5eda to
fd0fde2
Compare
nastra
force-pushed
the
SPARK-45807-api-improvements
branch
from
fd0fde2 to
fa808d1
Compare
|
thanks, merging to master! |
|
Thanks @nastra @cloud-fan @HyukjinKwon ! |
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?
Follow-up API improvements based on comments from #43677
Why are the changes needed?
Required for DataSourceV2 view support.
Does this PR introduce any user-facing change?
No
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
N/A