-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Support returning requestId in case opensearch is handled by AWS #71
Labels
enhancement
New feature or request
Comments
Oh, you mean you don't have access to the request ID response header from a high level client? Which language are you using? Care to post your code please? |
[Weekly Catch All Triage - 1] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
A clear and concise description of what the problem is, e.g. I'm always frustrated when [...].
NO
What solution would you like?
A clear and concise description of what you want to happen.
Currently, while making calls to an index inside a collection created with AWS using SDKs, the responses doesn't contains the aws request id, which difficult the debugging process with Opensearch team of AWS. Ideally, the response should contain all the metadata returned normally for an AWS SDK.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
A workaround for this is to make raw HTTP calls, but this leave away all the benefit provided by any SDK.
Do you have any additional context?
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: