# Does URI Search support the unmapped\_type parameter?

**URL:** <https://discuss.elastic.co/t/does-uri-search-support-the-unmapped-type-parameter/1402>\
**Category:** Elasticsearch\
**Created:** [May 27, 2015, 2:52pm UTC](https://discuss.elastic.co/t/does-uri-search-support-the-unmapped-type-parameter/1402 "2015-05-27T14:52:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GlennV](https://avatars.discourse-cdn.com/v4/letter/g/ce7236/32.png) [@GlennV](https://discuss.elastic.co/u/GlennV)\
**Post date:** [May 27, 2015, 2:52pm UTC](https://discuss.elastic.co/t/does-uri-search-support-the-unmapped-type-parameter/1402/1 "2015-05-27T14:52:58Z")

</div>

When you execute a [URI search](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-uri-request.html), but have unmapped fields in an index, ES will log an error.

If you use a [Request Body Search](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-sort.html#_ignoring_unmapped_fields), you can specify the unmapped\_type argument to tell ES how it has to interprete such fields and you can get rid of the errors. In my case I only have the option to use the URI search and am wondering if there still is a way to avoid the errors.

How can I use the "unmapped\_type" argument with a URI search? What about the "missing" argument? If these are not possible, is there another way?

Thanks,  
Glenn

---

<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, 12:11am UTC](https://discuss.elastic.co/t/does-uri-search-support-the-unmapped-type-parameter/1402/2 "2017-07-06T00:11:35Z")

</div>

Closed on July 6, 2017, 12:11am UTC