Details
-
New Feature
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
Description
When a sedona ST function throws an exception, it can be exceptionally difficult to figure out which geometry is causing the error. In a non-spark application a user could just catch the exception and log the geometry, but this is not easy to do in sedon/spark.
Returning the geometry with the exception will allow users to more quickly root cause exception and failures in their application.
