# String query - exact string

**URL:** <https://discuss.elastic.co/t/string-query-exact-string/176883>\
**Category:** Kibana\
**Created:** [April 15, 2019, 10:47am UTC](https://discuss.elastic.co/t/string-query-exact-string/176883 "2019-04-15T10:47:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![monfera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/monfera/32/26467_2.png) [@monfera](https://discuss.elastic.co/u/monfera)\
**Post date:** [April 15, 2019, 1:29pm UTC](https://discuss.elastic.co/t/string-query-exact-string/176883/2 "2019-04-15T13:29:04Z")

</div>

Hello Astarandel, it's more of an ES question than a Kibana one - is it an analyzed field, and is it using the standard analyzer? If so, is it also a multi-field, eg. also using `keyword`? Please refer to the links below as to why these matter:

> [@Exact match search on field with "standard" analyzer](https://discuss.elastic.co/t/exact-match-search-on-field-with-standard-analyzer/9617/5):
>
> You cannot achieve what you require by using the standard analyzer. The standard analyzer is tokenizing the string and creating two tokens: "good" and "one". You can see the results by using the analysis API: curl ' [http://localhost:9200/\_analyze?text=good@one&analyzer=standard&pretty=true](http://localhost:9200/_analyze?text=good@one&analyzer=standard&pretty=true)' The field would need to be not\_analyzed in order for it to have an exact match, or at the very least, an analyzer that creates only one token (use case dependent). If the field needs to be analyzed fo…

> **[Field data types | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html#_multi_fields)**

---

_[View the full topic](https://discuss.elastic.co/t/string-query-exact-string/176883)._