Fix: Handle "query_shard_exception" in OpenSearch error handling #3272
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request enhances the error handling for OpenSearch queries to include specific handling for the "query_shard_exception" error. Previously, only the "too_many_nested_clauses" error was handled explicitly. This change ensures that "query_shard_exception" is also caught, displayed to the user and logged appropriately, allowing for more informative error reporting and potential future recovery logic.
Specifically:
EventList
to include a check for the "query_shard_exception" message.This change improves the robustness of the OpenSearch integration by providing more granular error handling. It does not introduce any new functionality or change existing behavior other than improved error reporting.
It does not fix the underlying issue.