2016-03-13 16:17:48 -04:00
|
|
|
[[breaking_50_percolator]]
|
|
|
|
=== Percolator changes
|
|
|
|
|
|
|
|
==== Percolator is near-real time
|
|
|
|
|
|
|
|
Previously percolators were activated in real-time, i.e. as soon as they were
|
2016-04-19 09:59:09 -04:00
|
|
|
indexed. Now, changes to the `percolate` query are visible in near-real time,
|
2016-03-13 16:17:48 -04:00
|
|
|
as soon as the index has been refreshed. This change was required because, in
|
|
|
|
indices created from 5.0 onwards, the terms used in a percolator query are
|
|
|
|
automatically indexed to allow for more efficient query selection during
|
|
|
|
percolation.
|
|
|
|
|
2016-03-15 10:07:53 -04:00
|
|
|
==== Percolate and multi percolator APIs
|
|
|
|
|
|
|
|
Percolator and multi percolate APIs have been deprecated and will be removed in the next major release. These APIs have
|
2016-04-19 09:59:09 -04:00
|
|
|
been replaced by the `percolate` query that can be used in the search and multi search APIs.
|
2016-03-15 10:07:53 -04:00
|
|
|
|
2016-04-05 05:53:28 -04:00
|
|
|
==== Percolator field mapping
|
|
|
|
|
|
|
|
The `.percolator` type can no longer be used to index percolator queries.
|
|
|
|
|
|
|
|
Instead a <<percolator,percolator field type>> must be configured prior to indexing percolator queries.
|
|
|
|
|
|
|
|
Indices with a `.percolator` type created on a version before 5.0.0 can still be used,
|
|
|
|
but new indices no longer accept the `.percolator` type.
|
|
|
|
|
|
|
|
==== Percolate document mapping
|
2016-03-13 16:17:48 -04:00
|
|
|
|
2016-04-19 09:59:09 -04:00
|
|
|
The `percolate` query no longer modifies the mappings. Before the percolate API
|
2016-03-13 16:17:48 -04:00
|
|
|
could be used to dynamically introduce new fields to the mappings based on the
|
|
|
|
fields in the document being percolated. This no longer works, because these
|
|
|
|
unmapped fields are not persisted in the mapping.
|
|
|
|
|
|
|
|
==== Percolator documents returned by search
|
|
|
|
|
|
|
|
Documents with the `.percolate` type were previously excluded from the search
|
|
|
|
response, unless the `.percolate` type was specified explicitly in the search
|
|
|
|
request. Now, percolator documents are treated in the same way as any other
|
|
|
|
document and are returned by search requests.
|
|
|
|
|
2016-03-15 10:07:53 -04:00
|
|
|
==== Percolating existing document
|
2016-03-13 16:17:48 -04:00
|
|
|
|
2016-03-15 10:07:53 -04:00
|
|
|
When percolating an existing document then also specifying a document as source in the
|
2016-04-19 09:59:09 -04:00
|
|
|
`percolate` query is not allowed any more. Before the percolate API allowed and ignored
|
2016-03-15 10:07:53 -04:00
|
|
|
the existing document.
|
2016-03-13 16:17:48 -04:00
|
|
|
|
2016-03-15 10:07:53 -04:00
|
|
|
==== Percolate Stats
|
2016-03-13 16:17:48 -04:00
|
|
|
|
2016-04-19 09:59:09 -04:00
|
|
|
Percolate stats have been replaced with `percolate` query cache stats in nodes stats and cluster stats APIs.
|