# Why comments field not being displayed

**URL:** <https://discuss.elastic.co/t/why-comments-field-not-being-displayed/338228>\
**Category:** Elasticsearch\
**Created:** [July 12, 2023, 1:26pm UTC](https://discuss.elastic.co/t/why-comments-field-not-being-displayed/338228 "2023-07-12T13:26:07Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [July 26, 2023, 11:16am UTC](https://discuss.elastic.co/t/why-comments-field-not-being-displayed/338228/9 "2023-07-26T11:16:40Z")

</div>

Thanks for clarifying @Dana_Pavaday. It would be useful to have a rough idea of size of the field.

I did find this [old thread](https://discuss.elastic.co/t/what-is-the-maximum-text-size-that-can-be-indexed-as-a-single-term/292697/7) and the [blog post](https://www.elastic.co/blog/find-strings-within-strings-faster-with-the-new-elasticsearch-wildcard-field) mentioned in that thread that talks about the underlying Lucene limit that I wonder if you might be hitting:

> And even if you _do_ [raise](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/ignore-above.html) the Elasticsearch limit, you cannot exceed the hard Lucene limit of 32k for a single token, and Elasticsearch certainly logs some messages that exceed this.

I would recommend having a look at setting your [`ignore_above` limit](https://www.elastic.co/guide/en/elasticsearch/reference/8.9/ignore-above.html) in line with the note at the bottom of the documentation and seeing if that helps when the document is reingested.

---

_[View the full topic](https://discuss.elastic.co/t/why-comments-field-not-being-displayed/338228)._