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.
Description
This PR is for review purposes only – once it's approved, I will close it and push this branch version to our codeartifact.
Currently, the upstream opensearch connector fails at runtime while parsing OS 2.x server responses. This is happening because the Osearch high level rest client is out of sync with OS 2.x (specifically, the client expects a
type
field that is no longer included in the response body). This has been removed from the rest client in version 2.3.There's an open PR for the issue upstream with the exact same change: #4. Until this is sorted, this will have to do.
Validation
Security Considerations
Are there any security or data concerns to consider? If so, please describe them below.
This may include, but is not limited to:
Type of change
Documentation
If yes, how is the feature documented?
Checklists
DE-XXXX: Summary
where DE is the JIRA project short code, XXXX is the number, and Summary is the JIRA summary.