# Not able to process large lines of log data into elasticsearch

**URL:** https://discuss.elastic.co/t/not-able-to-process-large-lines-of-log-data-into-elasticsearch/66928
**Category:** Elasticsearch
**Created:** [November 23, 2016, 2:41am UTC](https://discuss.elastic.co/t/not-able-to-process-large-lines-of-log-data-into-elasticsearch/66928 "2016-11-23T02:41:22Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)
#### Post date: [November 23, 2016, 1:26pm UTC](https://discuss.elastic.co/t/not-able-to-process-large-lines-of-log-data-into-elasticsearch/66928/4 "2016-11-23T13:26:53Z")

</div>

> [@ggajanan](#):
>
> Document contains at least one immense term

Searching for that error gave me the following two results that might help you further:

> [@UTF8 encoding is longer than the max length 32766](https://discuss.elastic.co/t/utf8-encoding-is-longer-than-the-max-length-32766/816/2):
>
> You can try ignore\_above: 256 From [the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-core-types.html#mapping-core-types); ignore\_above The analyzer will ignore strings larger than this size. Useful for generic not\_analyzed fields that should ignore long text.

> <https://stackoverflow.com/questions/24019868/utf8-encoding-is-longer-than-the-max-length-32766>

Hope this helps,  
Isabel

---

_[View the full topic](https://discuss.elastic.co/t/not-able-to-process-large-lines-of-log-data-into-elasticsearch/66928)._