[es/kibanaIndex] use unmapped_type rather than ignore_unmapped #6463
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
spalger
force-pushed
the
fix/useOfIgnUnmapped
branch
from
23e488e to
ed021d5
Compare
spalger
force-pushed
the
fix/useOfIgnUnmapped
branch
from
ed021d5 to
af5ab8a
Compare
|
Tests failed, in case you're not watching the PR |
|
jenkins, test it |
|
Pending the tests passing, this LGTM |
rashidkpc
pushed a commit
that referenced
this pull request
Mar 8, 2016
[es/kibanaIndex] use unmapped_type rather than ignore_unmapped
|
💃 |
|
🎉 |
|
@spalger Can you try to backport this to 4.7? |
|
You got it #8968 |
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.
Fixes #6461
https://www.elastic.co/guide/en/elasticsearch/reference/1.6/search-request-sort.html#_ignoring_unmapped_fields