[SEDONA-659] Upgrade JTS version to 1.20.0 #1655
Merged
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
github-actions
bot
added
sedona-python
sedona-flink
sedona-common
sedona-spark
sedona-snowflake
root
labels
|
PR for running snowflake tests: wherobots#38 |
jiayuasu
approved these changes
Oct 25, 2024
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?
Upgrade JTS from 1.19.0 to 1.20.0.
Most of the changes are made to the tests due to different computation results obtained from 1.20.0. The following functions are affected from the observations of broken tests:
ST_MaximumIncribedCircleST_VoronoiPolygonsST_TriangulatePolygonST_BufferST_ConcaveHullST_MaximumIncribedCirclehas significant changes, while other functions only introduce slight coordinate value changes.How was this patch tested?
Passing tests.
Did this PR include necessary documentation updates?