# Suggestions response doesnt contain index information or information about document where the suggestion was found

**URL:** <https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543>\
**Category:** Elasticsearch\
**Created:** [May 4, 2023, 11:12am UTC](https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543 "2023-05-04T11:12:41Z")\
**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:** [May 4, 2023, 11:12am UTC](https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543/1 "2023-05-04T11:12:41Z")

</div>

Hi, I am trying to trace a suggestion to its source document returned by my search suggestion query in Elasticsearch 7.9

It seems the suggest Options only returns the suggested text , frequency and score. I see that the c# nest library i am using does support few other fields like index and context but they are always returned as null. Wanted to know if there is a way to enable these fields so that we can better trace from where a particular suggestion has been suggested.

Reason i want to do this is because my suggestion query is suggesting me a word that i cannot find in the general search query throughout my index so i want to make sure if the suggested word actually exists or is this a false record returned by the suggestions api.

I am searching the word purpoes which is a wrongly typed word for 'Purpose'

and i am getting a suggestion for the word 'Purpose' and 'Purpos' out of which the second word is no where to be found in my whole 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:** [May 5, 2023, 7:35am UTC](https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543/2 "2023-05-05T07:35:08Z")

</div>

Can i get any help on this issue please ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 8, 2023, 3:52am UTC](https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543/3 "2023-05-08T03:52:56Z")

</div>

Please note that version is [EOL](https://www.elastic.co/support/eol) and no longer supported, you should be looking to upgrade as a matter of urgency.

That said, have you tried the [explain endpoint](https://www.elastic.co/guide/en/elasticsearch/reference/8.7/search-explain.html)?

---

<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:** [May 10, 2023, 2:18pm UTC](https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543/4 "2023-05-10T14:18:57Z")

</div>

Thanks for the reply. Yup i can upgrade soon.

and yes i tried to add explain in the suggest query but it only gives explanation for the main query results and nothing for the suggestions block.

---

<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:** [June 7, 2023, 2:19pm UTC](https://discuss.elastic.co/t/suggestions-response-doesnt-contain-index-information-or-information-about-document-where-the-suggestion-was-found/332543/5 "2023-06-07T14:19:47Z")

</div>

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