# Kibana - Controls - Fuzziness/Case sensitive

**URL:** <https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101>\
**Category:** Kibana\
**Created:** [March 27, 2019, 11:05am UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101 "2019-03-27T11:05:23Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [March 27, 2019, 11:05am UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/1 "2019-03-27T11:05:23Z")

</div>

Hello,  
There is a way to add fuzziness/Case sensitive in my controls in Kibana? Because when I type "a" no results are presented, but if I type "A" the results appears.  
Any idea?  
Thank you,  
Francisca

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [March 27, 2019, 4:12pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/2 "2019-03-27T16:12:55Z")

</div>

Hey @Francisca_Lima, are you referring to the behavior of the query/filter bar displayed below?

 ![20%20AM](https://us1.discourse-cdn.com/elastic/original/3X/d/d/dd6c16c30261c15bb3781e1423c042968941988d.png)

---

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [March 27, 2019, 5:00pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/3 "2019-03-27T17:00:35Z")

</div>

No, it's in controls visualization.

 ![Captura%20de%20Ecr%C3%A3%20(60)](https://us1.discourse-cdn.com/elastic/original/3X/a/6/a6cd6ddcb61bba9147c9269f32fa9a4cc719bea7.png) ![Captura%20de%20Ecr%C3%A3%20(61)_LI](https://us1.discourse-cdn.com/elastic/original/3X/e/c/ece54f59c064828507e5b9428cf71c2d0801ef79.jpeg)

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [March 27, 2019, 5:43pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/4 "2019-03-27T17:43:48Z")

</div>

@Francisca_Lima, the controls visualization works with "aggregatable" fields, and is tied to the way that the field is stored in Elasticsearch itself.

When storing a string in Elasticsearch, we have a choice between storing it as "text" which allows you to perform free-text search and a "keyword" which is by default aggregatable. [https://www.elastic.co/blog/strings-are-dead-long-live-strings](https://www.elastic.co/blog/strings-are-dead-long-live-strings) is a good article on this topic.

When determining which values to display in the Controls visualization, we perform a [terms aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html) on the specified field. By default, we can only do so against a "keyword" field, and in this situation there is no analysis or normalization done on the strings which are being indexed, and as such there is no support for "fuzziness". It's possible to specify a [normalizer](https://www.elastic.co/guide/en/elasticsearch/reference/current/normalizer.html) for a "keyword" field which can be used to turn convert everything to lower-case to improve this situation.

It's also possible to enable [fielddata](https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html) for a "text" field, which will allow us to perform a terms aggregation on all of the tokens within the analyzed text, which could potentially be useful for your situation as well.

---

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [March 28, 2019, 9:55am UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/5 "2019-03-28T09:55:17Z")

</div>

Thank you for the explanation! Very helpful!

---

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [March 28, 2019, 5:45pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/6 "2019-03-28T17:45:37Z")

</div>

Meanwhile one question came up: even transforming a "text" field with analyser, only "keyword" fields can be used in controls visualization? I tried to add an analyser to the "text" field, but this "text" field do not appear in controls visualization. I tried to add an analyser to the "keyword" field, however my search was not improved (some results even do not appear).

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [March 28, 2019, 5:59pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/7 "2019-03-28T17:59:48Z")

</div>

You can use a "text" field with [fielddata](https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html) enabled with the controls visualization.

---

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [March 29, 2019, 12:13pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/8 "2019-03-29T12:13:10Z")

</div>

Thank you! However this does not solve my problem because I have more than 1 word and I want to improve search query, to easily type some letters and appear the results (keywords/more than one word, like a name) that have the same letters.  
The fielddata separate each word individually.

This is strange because if I type in controls (using a keyword field) sometimes the results appears but other times they do not but they exist. Using the filter bar above, doing the same thing, the result appears.

---

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [March 29, 2019, 12:24pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/9 "2019-03-29T12:24:40Z")

</div>

In another attribute, year of a date, something strange happens:  
If I type in controls, the result does not match, but typing in filter bar, the results match.

 ![Captura%20de%20Ecr%C3%A3%20(62)_LI](https://us1.discourse-cdn.com/elastic/original/3X/d/c/dc6966ed65cda3965a06d3bae7f40d70d9a18e62.jpeg) ![Captura%20de%20Ecr%C3%A3%20(63)](https://us1.discourse-cdn.com/elastic/original/3X/3/f/3f20c1983633da51374d5adf1a006bd7bba14b8f.png)  
Any idea? Controls does not work properly?

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [March 29, 2019, 3:01pm UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/10 "2019-03-29T15:01:27Z")

</div>

The "Controls" visualization is not a direct replacement for the filter bar, and it offers a limited subset of this functionality. If you're looking for true fuzzy search, you'll have to continue using the filter bar.

---

<div class="post-metadata">

**Author:** ![Francisca\_Lima](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@Francisca\_Lima](https://discuss.elastic.co/u/Francisca_Lima)\
**Post date:** [April 1, 2019, 8:55am UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/11 "2019-04-01T08:55:23Z")

</div>

Thank you. I though that controls were a more user friendly way to use filter bar.  
That it an disadvantage, because if it is limited, I never know if I am transmitting wrong information to the person that it is using the dashboard.

---

<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:** [April 29, 2019, 8:55am UTC](https://discuss.elastic.co/t/kibana-controls-fuzziness-case-sensitive/174101/12 "2019-04-29T08:55:43Z")

</div>

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