[SEDONA-226] Replace AnalysisException with IllegalArgumentException in GeoParquet reader since AnalysisException has breaking ABI changes between Spark 3.0 and 3.3 #771
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
… reader since AnalysisException has breaking ABI changes between Spark 3.0 and 3.3
jiayuasu
approved these changes
Feb 16, 2023
zongsizhang
pushed a commit
that referenced
this pull request
Feb 19, 2023
…in GeoParquet reader since AnalysisException has breaking ABI changes between Spark 3.0 and 3.3 (#771)
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.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject.What changes were proposed in this PR?
Resolve an ABI compatibility issue spotted by #770.
The issue we're resolving is similar to SEDONA-224. It requires some effort to make the GeoParquet implementation compatible with Spark 3.0~3.3.
How was this patch tested?
Added a python test case to verify ABI compatibility in case of invalid user input.
Did this PR include necessary documentation updates?