Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-48294][SQL][3.5] Handle lowercase in nestedTypeMissingElementTypeError #46643

Closed

Conversation

michaelzhan-db
Copy link
Contributor

What changes were proposed in this pull request?

Backport of #46623.
Handle lowercase values inside of nestTypeMissingElementTypeError to prevent match errors.

Why are the changes needed?

The previous match error was not user-friendly. Now it gives an actionable INCOMPLETE_TYPE_DEFINITION error.

Does this PR introduce any user-facing change?

N/A

How was this patch tested?

Newly added tests pass.

Was this patch authored or co-authored using generative AI tooling?

No.

@github-actions github-actions bot added the SQL label May 17, 2024
### What changes were proposed in this pull request?

Handle lowercase values inside of nestTypeMissingElementTypeError to prevent match errors.

### Why are the changes needed?

The previous match error was not user-friendly. Now it gives an actionable `INCOMPLETE_TYPE_DEFINITION` error.

### Does this PR introduce _any_ user-facing change?

N/A

### How was this patch tested?

Newly added tests pass.

### Was this patch authored or co-authored using generative AI tooling?

No.

Closes apache#46623 from michaelzhan-db/SPARK-48294.

Authored-by: Michael Zhang <m.zhang@databricks.com>
Signed-off-by: Gengliang Wang <gengliang@apache.org>

(cherry picked from commit 59f88c3)
@gengliangwang
Copy link
Member

Thanks, merging to branch-3.5

gengliangwang pushed a commit that referenced this pull request May 17, 2024
…ypeError

### What changes were proposed in this pull request?

Backport of #46623.
Handle lowercase values inside of nestTypeMissingElementTypeError to prevent match errors.

### Why are the changes needed?

The previous match error was not user-friendly. Now it gives an actionable `INCOMPLETE_TYPE_DEFINITION` error.

### Does this PR introduce _any_ user-facing change?

N/A

### How was this patch tested?

Newly added tests pass.

### Was this patch authored or co-authored using generative AI tooling?
No.

Closes #46643 from michaelzhan-db/SPARK-48294-3.5.

Authored-by: Michael Zhang <m.zhang@databricks.com>
Signed-off-by: Gengliang Wang <gengliang@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants