# Long field causing pipeline exception

**URL:** <https://discuss.elastic.co/t/long-field-causing-pipeline-exception/71425>\
**Category:** Logstash\
**Created:** [January 12, 2017, 7:19pm UTC](https://discuss.elastic.co/t/long-field-causing-pipeline-exception/71425 "2017-01-12T19:19:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhooper](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@mhooper](https://discuss.elastic.co/u/mhooper)\
**Post date:** [January 12, 2017, 7:19pm UTC](https://discuss.elastic.co/t/long-field-causing-pipeline-exception/71425/1 "2017-01-12T19:19:32Z")

</div>

Hello. When parsing error logs once in a while we get extremely long messages (1M). Obviously this breaks the 32K index limit so I was looking at solutions. I found a rangefilter plugin that would allow me accept a range from 0-32K but when researching I realized it was based on array type which is deprecated. What are alternate solutions to this?

thank you

---

<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 9, 2017, 7:20pm UTC](https://discuss.elastic.co/t/long-field-causing-pipeline-exception/71425/2 "2017-02-09T19:20:01Z")

</div>

Closed on February 9, 2017, 7:20pm UTC

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