Make MultiSearchItem.status optional #1320
Merged
Conversation
This file contains hidden or 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
Anaethelion
approved these changes
Jan 25, 2022
|
Opened an issue in Elasticsearch: elastic/elasticsearch#83029 |
swallez
added a commit
that referenced
this pull request
Jan 25, 2022
swallez
added a commit
that referenced
this pull request
Jan 25, 2022
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.
The
MultiSearchItem.statusproperty is always returned in multisearch responses but is missing from multisearch-template responses.This should be considered as an inconsistency/bug in the ES API, and this PR fixes it by making
statusoptional rather than creating a separate type for multisearch-template responses.Reported in elastic/elasticsearch-java#110