Explicitly set mappings in SearchAfterIT#54262
Merged
romseygeek merged 1 commit intoelastic:masterfrom Mar 26, 2020
Merged
Conversation
Collaborator
|
Pinging @elastic/es-search (:Search/Mapping) |
romseygeek
added a commit
that referenced
this pull request
Mar 26, 2020
We have some very occasional failures in SearchAfterIT, where a search throws an exception because a shard does not have the mapping for the requested sort field. The field should have been added in a dynamic mapping update after an index event, but it seems that there can sometimes be a small delay in propagating this update to the shards. This commit changes the test to explicitly define the relevant field at index creation time. Fixes #51900
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We have some very occasional failures in SearchAfterIT, where a search throws
an exception because the shard does not have a mapping for the requested sort
field. The field should have been added in a dynamic mapping update after an
index event, but it seems that there can sometimes be a small delay in propagating
this update to the shards.
This commit changes the test to explicitly define the relevant field at index creation
time.
Fixes #51900