Improve Elasticsearch error handling for 404 and empty responses#192
Improve Elasticsearch error handling for 404 and empty responses#192
Conversation
Enhanced error handling in get_hysds_io() and get_job_spec() functions to properly handle: - HTTP 404 responses when algorithm specifications are not found - Other HTTP error status codes (4xx, 5xx) - Invalid JSON responses - Empty result sets from Elasticsearch queries - Network/connection errors This provides clearer error messages to users when algorithms are not registered or when ES queries fail, making it easier to diagnose issues with job submissions.
|
|
Should we merge this instead into |
|
sure, this is also something needed in UAT. So however it works. Will need to test the edge cases on the |
grallewellyn
left a comment
grallewellyn
left a comment
There was a problem hiding this comment.
Do we need this in the 2i2c API release we already did? Because we missed this PR
We can at least get this into develop and release/5.0.0
3 participants
Enhanced error handling in get_hysds_io() and get_job_spec() functions to properly handle:
This provides clearer error messages to users when algorithms are not registered or when ES queries fail, making it easier to diagnose issues with job submissions.