[SPARK-54573][SQL] Add test for CONSTRAINTS in case of source with less nested struct field than target #53291
+48
−0
Conversation
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
…ss nested struct field than target
Member
Author
|
this test was suggested by @aokolnychyi , but not urgent to include it in Spark 4.1, as the test works. |
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.
What changes were proposed in this pull request?
Adding a test if CONSTRAINTS work in this case.
Why are the changes needed?
Test-only, as this feature is going out in Spark 4.1.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Run the test
Was this patch authored or co-authored using generative AI tooling?
No