Improve error message by handling caused_by.reason #401
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevinwcyu
requested review from
iwysiu and
idastambuk
and removed request for
a team
idastambuk
approved these changes
May 30, 2024
This was referenced May 30, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Lucene query error responses sometimes have the error message in the
caused_by.reasonproperty. This handles that case so the user can get a more helpful error message instead of "unknown OpenSearch error response" (see #400)Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Use the provisioned "AWS OpenSearch" data source with the following query in Explore. It show the error message shown in the screenshot instead of "unknown OpenSearch error response"