# Storing long fields in ELK

**URL:** <https://discuss.elastic.co/t/storing-long-fields-in-elk/192875>\
**Category:** Elasticsearch\
**Created:** [July 30, 2019, 10:54am UTC](https://discuss.elastic.co/t/storing-long-fields-in-elk/192875 "2019-07-30T10:54:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![elk11](https://avatars.discourse-cdn.com/v4/letter/e/45deac/32.png) [@elk11](https://discuss.elastic.co/u/elk11)\
**Post date:** [July 30, 2019, 10:54am UTC](https://discuss.elastic.co/t/storing-long-fields-in-elk/192875/1 "2019-07-30T10:54:52Z")

</div>

Hi,

I have few very large fields, in order of few MB's. When i query for something on that index i used to get "length of the field crossed max allowed for highlighting". To work around this problem, i started indexing those very long fields with 'index\_options: offset' as suggested by error message.

Now i started getting, request time out error (which is currently set to 90000) on Kibana discover tab. All this happening even when i'm not querying that large fields. Although all queries seem to work fine on console ('dev-tools' tab of Kibana)

So what's the proper way to store those very long fields such that i don't hit timeout error?

Thanks

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 30, 2019, 12:18pm UTC](https://discuss.elastic.co/t/storing-long-fields-in-elk/192875/2 "2019-07-30T12:18:08Z")

</div>

The discover app loads full documents and deserialising very large documents can be very slow. Why are your documents so large?

---

<div class="post-metadata">

**Author:** ![elk11](https://avatars.discourse-cdn.com/v4/letter/e/45deac/32.png) [@elk11](https://discuss.elastic.co/u/elk11)\
**Post date:** [July 30, 2019, 12:42pm UTC](https://discuss.elastic.co/t/storing-long-fields-in-elk/192875/3 "2019-07-30T12:42:30Z")

</div>

Thanks for you response.

We are storing some part of the console log which we find very useful. We would like to have it around. I think we are okay with our queries being a bit slow, but right now, the queries are throwing the above described error. Hope I'm clear.

---

<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:** [August 27, 2019, 12:42pm UTC](https://discuss.elastic.co/t/storing-long-fields-in-elk/192875/4 "2019-08-27T12:42:35Z")

</div>

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