# Transformation d'une matchPhraseQuery en filter

**URL:** <https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183>\
**Category:** Discussions en français\
**Created:** [December 2, 2015, 2:08pm UTC](https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183 "2015-12-02T14:08:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blured\_Derulb](https://avatars.discourse-cdn.com/v4/letter/b/848f3c/32.png) [@Blured\_Derulb](https://discuss.elastic.co/u/Blured_Derulb)\
**Post date:** [December 2, 2015, 2:08pm UTC](https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183/1 "2015-12-02T14:08:35Z")

</div>

Bonjour,

Afin d'accélérer mes traitement je cherche à transformer le maximum de requêtes en filtres.

Je me demande si il est possible de transformer ce matchPhraseQuery en filtre :

QueryBuilder allTerms = matchPhraseQuery("text", query.originalText).operator(org.elasticsearch.index.query.MatchQueryBuilder.Operator.AND).fuzziness(Fuzziness.ZERO).minimumShouldMatch("100%");

Pour info, le champ text est "analysé", je ne sais pas si c'est possible d'utiliser ce type de champs dans des filtres.

Avez-vous une idée ? C'est vraiement du 0 ou 1 que je cherche en résultat je me fiche du scoring réel.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 2, 2015, 3:13pm UTC](https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183/2 "2015-12-02T15:13:09Z")

</div>

Si tu utilises elasticsearch 2.0, cela devrait se faire automatiquement si tu mets ta condition dans un filtre.

[https://www.elastic.co/guide/en/elasticsearch/reference/2.1/query-filter-context.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.1/query-filter-context.html)

---

<div class="post-metadata">

**Author:** ![Blured\_Derulb](https://avatars.discourse-cdn.com/v4/letter/b/848f3c/32.png) [@Blured\_Derulb](https://discuss.elastic.co/u/Blured_Derulb)\
**Post date:** [December 2, 2015, 3:19pm UTC](https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183/3 "2015-12-02T15:19:22Z")

</div>

En 1.7 ce n'est pas possible ?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 2, 2015, 3:31pm UTC](https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183/4 "2015-12-02T15:31:57Z")

</div>

Tu peux toujours faire ça: [https://www.elastic.co/guide/en/elasticsearch/reference/1.7/query-dsl-query-filter.html](https://www.elastic.co/guide/en/elasticsearch/reference/1.7/query-dsl-query-filter.html)

Supprimé en 2.0 car inutile.

---

<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:** [July 6, 2017, 1:50pm UTC](https://discuss.elastic.co/t/transformation-dune-matchphrasequery-en-filter/36183/5 "2017-07-06T13:50:23Z")

</div>