-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Sub-fields should not accept include_in_all
parameter
#21971
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
318ce6a
fix bug: https://github.com/elastic/elasticsearch/issues/21710
makeyang 46cdb41
modified code according to nik9000's comments.
makeyang ce0ad4e
add test case for parse include_in_all in mulit fields
makeyang 4c79f36
1. add license declaration in class header
makeyang File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
53 changes: 53 additions & 0 deletions
53
core/src/test/java/org/elasticsearch/index/mapper/MultiFieldIncludeInAllMapperTests.java
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
package org.elasticsearch.index.mapper; | ||
|
||
import org.elasticsearch.common.compress.CompressedXContent; | ||
import org.elasticsearch.common.settings.Settings; | ||
import org.elasticsearch.common.xcontent.XContentBuilder; | ||
import org.elasticsearch.index.MapperTestUtils; | ||
import org.elasticsearch.test.ESTestCase; | ||
|
||
import java.io.IOException; | ||
|
||
import static org.elasticsearch.common.xcontent.XContentFactory.jsonBuilder; | ||
import static org.hamcrest.core.IsEqual.equalTo; | ||
|
||
/** | ||
* Created by makeyang on 2016/12/8. | ||
*/ | ||
public class MultiFieldIncludeInAllMapperTests extends ESTestCase { | ||
public void testExceptionForCopyToInMultiFields() throws IOException { | ||
XContentBuilder mapping = createMappinmgWithIncludeInAllInMultiField(); | ||
|
||
// first check that for newer versions we throw exception if copy_to is found withing multi field | ||
MapperService mapperService = MapperTestUtils.newMapperService(createTempDir(), Settings.EMPTY); | ||
try { | ||
mapperService.parse("type", new CompressedXContent(mapping.string()), true); | ||
fail("Parsing should throw an exception because the mapping contains a include_in_all in a multi field"); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We tend to use |
||
} catch (MapperParsingException e) { | ||
assertThat(e.getMessage(), equalTo("include_in_all in multi fields is not allowed. Found the include_in_all in field [c] which is within a multi field.")); | ||
} | ||
} | ||
|
||
private static XContentBuilder createMappinmgWithIncludeInAllInMultiField() throws IOException { | ||
XContentBuilder mapping = jsonBuilder(); | ||
mapping.startObject() | ||
.startObject("type") | ||
.startObject("properties") | ||
.startObject("a") | ||
.field("type", "text") | ||
.endObject() | ||
.startObject("b") | ||
.field("type", "text") | ||
.startObject("fields") | ||
.startObject("c") | ||
.field("type", "text") | ||
.field("include_in_all", false) | ||
.endObject() | ||
.endObject() | ||
.endObject() | ||
.endObject() | ||
.endObject() | ||
.endObject(); | ||
return mapping; | ||
} | ||
} |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you replace this with something descriptive of what it does or remove it?