# Is it necessary an extra mapping for Percolate queries in ES5?

**URL:** <https://discuss.elastic.co/t/is-it-necessary-an-extra-mapping-for-percolate-queries-in-es5/73207>\
**Category:** Elasticsearch\
**Created:** [January 30, 2017, 12:24pm UTC](https://discuss.elastic.co/t/is-it-necessary-an-extra-mapping-for-percolate-queries-in-es5/73207 "2017-01-30T12:24:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jasl](https://avatars.discourse-cdn.com/v4/letter/j/9fc348/32.png) [@jasl](https://discuss.elastic.co/u/jasl)\
**Post date:** [January 30, 2017, 12:24pm UTC](https://discuss.elastic.co/t/is-it-necessary-an-extra-mapping-for-percolate-queries-in-es5/73207/1 "2017-01-30T12:24:50Z")

</div>

Following new ES5 doc:

[https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-percolate-query.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-percolate-query.html)

says 2 mapping must be defined: doctype, queries

doctype mapping is there to set what fields can be used in percolate query, if I want to be able to use every field available for an index, Can I re-use the index mapping or I need to duplicate the mapping?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 31, 2017, 9:37am UTC](https://discuss.elastic.co/t/is-it-necessary-an-extra-mapping-for-percolate-queries-in-es5/73207/2 "2017-01-31T09:37:47Z")

</div>

Hey,

so `doctype` is just used as an example here, you can replace it with your own type.

--Alex

---

<div class="post-metadata">

**Author:** ![jasl](https://avatars.discourse-cdn.com/v4/letter/j/9fc348/32.png) [@jasl](https://discuss.elastic.co/u/jasl)\
**Post date:** [January 31, 2017, 11:36am UTC](https://discuss.elastic.co/t/is-it-necessary-an-extra-mapping-for-percolate-queries-in-es5/73207/3 "2017-01-31T11:36:13Z")

</div>

great, Thanks!

I supposed it, but the documentation kind of suggest otherwise, even some examples have same confusion:

> **[Using the new elasticsearch 5 percolator - Luminis Amsterdam](https://amsterdam.luminis.eu/2016/10/13/using-the-new-elasticsearch-5-percolator/)**
>
> In the upcoming version 5 of elasticsearch the implementation for the percolator has changed a lot. They moved the percolator from being a separate endpoint and API to being a member of the search API. In the new version you can execute a percolator...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 28, 2017, 11:36am UTC](https://discuss.elastic.co/t/is-it-necessary-an-extra-mapping-for-percolate-queries-in-es5/73207/4 "2017-02-28T11:36:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
