[SPARK-48688][SQL] Return reasonable error when calling SQL to_avro and from_avro functions but Avro is not loaded by default#47063
Closed
dtenedor wants to merge 2 commits into
Closed
Conversation
HyukjinKwon
approved these changes
Jun 23, 2024
Member
|
Merged to master. |
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
2 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.
What changes were proposed in this pull request?
This PR updates the new
to_avroandfrom_avroSQL functions added in #46977 to return reasonable errors when Avro is not loaded by default.Why are the changes needed?
According to the Apache Spark Avro Data Source Guide, Avro is not loaded into Spark by default. With this change, users get reasonable error messages if they try to call the
to_avroorfrom_avroSQL functions in this case with instructions telling them what to do, rather than obscure JavaClassNotFoundExceptions.Does this PR introduce any user-facing change?
Yes, see above.
How was this patch tested?
This PR adds golden file based test coverage.
Was this patch authored or co-authored using generative AI tooling?
No GitHub copilot this time.