# Recommendation on very large text fields

**URL:** <https://discuss.elastic.co/t/recommendation-on-very-large-text-fields/216079>\
**Category:** Elasticsearch\
**Created:** [January 22, 2020, 2:45pm UTC](https://discuss.elastic.co/t/recommendation-on-very-large-text-fields/216079 "2020-01-22T14:45:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jimmy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimmy/32/55277_2.png) [@Jimmy](https://discuss.elastic.co/u/Jimmy)\
**Post date:** [January 22, 2020, 2:45pm UTC](https://discuss.elastic.co/t/recommendation-on-very-large-text-fields/216079/1 "2020-01-22T14:45:38Z")

</div>

Hi,

I have an index which one of the fields can contain thousands of characters, it's a field which an user can input some html information, and in some cases a base64 encoded image.

This field does not need to be searched, however it needs to be returned on request. What's the recommended approach when working with such large fields?

Thanks!

---

<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:** [February 19, 2020, 2:45pm UTC](https://discuss.elastic.co/t/recommendation-on-very-large-text-fields/216079/2 "2020-02-19T14:45:43Z")

</div>

Closed on February 19, 2020, 2:45pm UTC

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