# Handling unmapped fields with Suggest feature

**URL:** <https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937>\
**Category:** Elasticsearch\
**Created:** [September 22, 2022, 11:17am UTC](https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937 "2022-09-22T11:17:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![schawla](https://avatars.discourse-cdn.com/v4/letter/s/87869e/32.png) [@schawla](https://discuss.elastic.co/u/schawla)\
**Post date:** [September 22, 2022, 11:17am UTC](https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937/1 "2022-09-22T11:17:21Z")

</div>

I am trying to implement suggest feature - [Suggest Usage | Elasticsearch .NET Client [8.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/suggest-usage.html) for handling misspelled words in my search implementation.

My search query is executed across multiple indices but while trying to use the suggest functionality , i am running into failures due to unmappaed fields.

Suppose i have an index named People which has a field - "name". Another index named news which has a field named - "title". My query was executed across both indices at the same time and search query had rules defined for both name and title fields. But while using suggest, i only want to return suggestions for name field in person index as part of the same query. As a result of this my news index is returning a failure that no mapping found for field name.

Is there a work- around in the suggest functionality via which i can specify an index name for the field mentioned in suggest - [Suggest Usage | Elasticsearch .NET Client [8.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/suggest-usage.html) OR can i ignore unmapped fields and continue to return search results from the other index (news) without returning any suggestions for misspelled words for that index.

---

<div class="post-metadata">

**Author:** ![schawla](https://avatars.discourse-cdn.com/v4/letter/s/87869e/32.png) [@schawla](https://discuss.elastic.co/u/schawla)\
**Post date:** [September 23, 2022, 10:31am UTC](https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937/2 "2022-09-23T10:31:06Z")

</div>

Can someone help on the above issue

---

<div class="post-metadata">

**Author:** ![schawla](https://avatars.discourse-cdn.com/v4/letter/s/87869e/32.png) [@schawla](https://discuss.elastic.co/u/schawla)\
**Post date:** [September 26, 2022, 2:32pm UTC](https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937/3 "2022-09-26T14:32:40Z")

</div>

Still looking for help on the above issue

---

<div class="post-metadata">

**Author:** ![schawla](https://avatars.discourse-cdn.com/v4/letter/s/87869e/32.png) [@schawla](https://discuss.elastic.co/u/schawla)\
**Post date:** [October 4, 2022, 2:36pm UTC](https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937/4 "2022-10-04T14:36:45Z")

</div>

Can anyone assist on this issue ?

---

<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:** [November 1, 2022, 2:36pm UTC](https://discuss.elastic.co/t/handling-unmapped-fields-with-suggest-feature/314937/5 "2022-11-01T14:36:48Z")

</div>

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