-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeometryType(geom) triggered an exception #1263
Comments
@ruanqizhen can you show me the full stacktrace? The one that is after |
This is the entire stacktrace it returned. |
@ruanqizhen I think the GeometryType might have indeterministic behavior over invalid geometries. We need to further investigate this issue. Can you run |
It is not likely caused by the invalid geometry, because I've called the ST_MakeValid() for all of the geometries. |
@ruanqizhen If both of the method still cannot fix the issue, I think you can stick to ST_GeometryType. If you don't want the |
I'm using ST_GeometryType now. But I'm wondering if there is a way to find out which row caused the problem. Is there a way that I can "try", or skip the error, to let the query continue process other rows, so that I can then check which row was skipped. |
Expected behavior
When I call "GeometryType(geom)" to my table, it triggered a java.lang.NullPointerException exception. But "ST_GeometryType(geom)" works as expected.
It just crashed, so I couldn't find out which row caused the problem.
The track stack:
Settings
Sedona version = 1.5
Apache Spark version = 3.2
Apache Flink version = ?
API type = Python
Python version = 3.10
Environment = Amazon Athena
The text was updated successfully, but these errors were encountered: