Throw error codes bases on elastic IO exception
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? No
-
AWS -
Azure -
Google Cloud -
IBM
Does this introduce a breaking change?
- NO
What is the current behavior?
For all the elastic IO exceptions like 429 search services is throwing 500 internal error
What is the new/expected behavior?
Search service return specific error codes based on elastic exception like 429 from elastic search will be returned as 429 from search service
Have you added/updated Unit Tests and Integration Tests?
yes Added unit tests