# Dropdown control on non-.keyword text field in v6.4.5

**URL:** <https://discuss.elastic.co/t/dropdown-control-on-non-keyword-text-field-in-v6-4-5/178985>\
**Category:** Kibana\
**Created:** [April 29, 2019, 8:10pm UTC](https://discuss.elastic.co/t/dropdown-control-on-non-keyword-text-field-in-v6-4-5/178985 "2019-04-29T20:10:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![EtienneDemers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/etiennedemers/32/23474_2.png) [@EtienneDemers](https://discuss.elastic.co/u/EtienneDemers)\
**Post date:** [April 29, 2019, 8:10pm UTC](https://discuss.elastic.co/t/dropdown-control-on-non-keyword-text-field-in-v6-4-5/178985/1 "2019-04-29T20:10:09Z")

</div>

I'm using kibana 6.5.4 and i'd like to create a case-insensitive control dropdown.

I'm using a logstash jdbc ingestion pipeline with a basic dynamic mappiing from ES (all automatic stuff).

After reading a bit trough the doc i found out that (to my understanding) .keyword field needs exact values (case-sensitive) while normal text fields are case-insensitive. So i guess that if i was able to get my dropdown control to use the not .keyword version of my field, i would be able to use the dropdown in a case-insensitive way But i only see the .keyword versions of my tyext fields in the available fields to use for my dropdown.

Maybe there's a work around by tweaking the mapping manually or a workaround in the logstash ingestion i'm using? maybe it's simply a limitation and i can't work around it. Any insight on this would be welcome.

---

<div class="post-metadata">

**Author:** ![Catherine\_Liu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catherine_liu/32/34294_2.png) [@Catherine\_Liu](https://discuss.elastic.co/u/Catherine_Liu)\
**Post date:** [April 30, 2019, 5:57pm UTC](https://discuss.elastic.co/t/dropdown-control-on-non-keyword-text-field-in-v6-4-5/178985/2 "2019-04-30T17:57:04Z")

</div>

One workaround you could explore is to enable [`fielddata`](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/fielddata.html#_fielddata_is_disabled_on_literal_text_literal_fields_by_default) on the analyzed text field in your Logstash index pattern. However, it is intentionally disabled by default because enabling `fielddata` on an analyzed text field can use up a significant amount of memory.

Alternatively, you could configure your Logstash pipeline to lowercase all of the values in your .keyword field to use with the case-sensitive dropdown control. See [Mutate filter plugin - lowercase](https://www.elastic.co/guide/en/logstash/current/plugins-filters-mutate.html#plugins-filters-mutate-lowercase)

---

<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:** [May 28, 2019, 5:57pm UTC](https://discuss.elastic.co/t/dropdown-control-on-non-keyword-text-field-in-v6-4-5/178985/3 "2019-05-28T17:57:14Z")

</div>

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