[SEDONA-501] ST_Split maps to wrong Java-call

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.5.2
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Niklas Loevenholdt Petersen
• Created: 22/Feb/24 14:58
• Updated: 28/Apr/24 08:15
• Resolved: 28/Apr/24 08:15

Description

When using the Python ST_Split (from sedona.sql.st_functions) you get quite a different result then using ST_Split in a SQL statement. The ST_Split seems to be mapped to the wrong Java-call (ST_SymDifference).

I am happy to have a go on fixing this: 

https://github.com/apache/sedona/pull/1252

Issue Links

• links to: GitHub Pull Request #1252