Provider - Catch exception when processing spatial filter
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- [YES]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
See issue: https://community.opengroup.org/osdu/platform/consumption/geospatial/-/issues/343
What is the new/expected behavior?
This now "just" returns a 500 error, without stopping the server