Analyzed text fields take term positions
into account, in order to be able to support
proximity or phrase queries.
When indexing text fields with multiple values a "fake" gap is added between
the values to prevent most phrase queries from matching across the values. The
size of this gap is configured using
position_increment_gap and defaults to
This phrase query doesn’t match our document which is totally expected.
This phrase query matches our document, even though
position_increment_gap can be specified in the mapping. For instance:
The first term in the next array element will be 0 terms apart from the last term in the previous array element.
The phrase query matches our document which is weird, but its what we asked for in the mapping.
position_increment_gap setting is allowed to have different settings
for fields of the same name in the same index. Its value can be updated on
existing fields using the PUT mapping API.