-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Handle runtime subfields when shadowing dynamic mappings #75595
Changes from all commits
dce4894
337041d
fea7ddb
f176ee0
4767a31
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -308,7 +308,7 @@ public void testDualingQueries() throws IOException { | |
String source = "{\"foo\": " + values + "}"; | ||
XContentParser parser = createParser(JsonXContent.jsonXContent, source); | ||
SourceToParse sourceToParse = new SourceToParse("test", "test", new BytesArray(source), XContentType.JSON); | ||
DocumentParserContext ctx = new TestDocumentParserContext(null, null, null, null, sourceToParse) { | ||
DocumentParserContext ctx = new TestDocumentParserContext(MappingLookup.EMPTY, null, null, null, sourceToParse) { | ||
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. There is another 0-argument ctor in TestDocumentParserContext that seems unused, maybe we should delete it or otherwise also use MappingLookup.EMPTY as first argument there to avoid suprises later. 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. Good catch - that's actually causing some percolator failures, will switch it to always use MappingLookup.EMPTY |
||
@Override | ||
public XContentParser parser() { | ||
return parser; | ||
|
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.
I don't know if its useful to keep this assertion, no strong opinion, just curious if you deleted it for some specific reason.
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.
I think it was an extra check that this was definitely a runtime field. I don't think it's necessary any longer because we now know where the shadowing logic is pulling fields from.