# Elasticsearch case insensitive to not\_analyzed index

**URL:** <https://discuss.elastic.co/t/elasticsearch-case-insensitive-to-not-analyzed-index/52979>\
**Category:** Elasticsearch\
**Created:** [June 16, 2016, 11:03am UTC](https://discuss.elastic.co/t/elasticsearch-case-insensitive-to-not-analyzed-index/52979 "2016-06-16T11:03:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [June 16, 2016, 2:57pm UTC](https://discuss.elastic.co/t/elasticsearch-case-insensitive-to-not-analyzed-index/52979/6 "2016-06-16T14:57:31Z")

</div>

Hi @tarlok,

the suggested approach is to use multiple fields as I [suggested in my first answer in that post](https://discuss.elastic.co/t/searching-not-analyzed-term-name-and-value-in-case-insensitive-manner/50537/2?u=danielmitterdorfer). Queries will be fast then but of course the additional field will require additional disk space in the index.

Daniel

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-case-insensitive-to-not-analyzed-index/52979)._