# NullPointerException when settings "es.read.field.as.array.include" options

**URL:** <https://discuss.elastic.co/t/nullpointerexception-when-settings-es-read-field-as-array-include-options/63223>\
**Category:** Elasticsearch\
**Tags:** es-hadoop\
**Created:** [October 17, 2016, 8:41pm UTC](https://discuss.elastic.co/t/nullpointerexception-when-settings-es-read-field-as-array-include-options/63223 "2016-10-17T20:41:48Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [February 24, 2017, 12:06pm UTC](https://discuss.elastic.co/t/nullpointerexception-when-settings-es-read-field-as-array-include-options/63223/7 "2017-02-24T12:06:30Z")

</div>

Hello,

Nop, there are plenty issues with array (latest I found =\> [Bug when reading if a field has no mapping (empty array by ex.)](https://discuss.elastic.co/t/bug-when-reading-if-a-field-has-no-mapping-empty-array-by-ex/76393) drive me crazy ^^).

So, I removed array for flat structure, no problem like that.

(having fields like toto\_1:, toto\_2: , toto\_3 instead of toto: [])

---

_[View the full topic](https://discuss.elastic.co/t/nullpointerexception-when-settings-es-read-field-as-array-include-options/63223)._