# Possible bug when using fields=... on arrays

**URL:** <https://discuss.elastic.co/t/possible-bug-when-using-fields-on-arrays/6833>\
**Category:** Elasticsearch\
**Created:** [February 28, 2012, 4:24pm UTC](https://discuss.elastic.co/t/possible-bug-when-using-fields-on-arrays/6833 "2012-02-28T16:24:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![barnybug](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@barnybug](https://discuss.elastic.co/u/barnybug)\
**Post date:** [February 28, 2012, 4:24pm UTC](https://discuss.elastic.co/t/possible-bug-when-using-fields-on-arrays/6833/1 "2012-02-28T16:24:26Z")

</div>

See gist:

> <https://gist.github.com/barnybug/1933431>

produces:  
{  
error: "NullPointerException[null]",  
status: 500  
}

Is this a bug?

thanks

Barnaby

---

<div class="post-metadata">

**Author:** ![barnybug](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@barnybug](https://discuss.elastic.co/u/barnybug)\
**Post date:** [February 29, 2012, 11:27am UTC](https://discuss.elastic.co/t/possible-bug-when-using-fields-on-arrays/6833/2 "2012-02-29T11:27:43Z")

</div>

I've submitted a pull request for this:

> <https://github.com/elastic/elasticsearch/pull/1746>
>
> see:
> https://groups.google.com/group/elasticsearch/browse\_thread/thread/9a38f64e…e43ffdca/0301e877640a46f1

On Feb 28, 4:24 pm, barnybug [barny...@googlemail.com](mailto:barny...@googlemail.com) wrote:

> See gist:[gist:1933431 · GitHub](https://gist.github.com/1933431)
> 
> produces:  
> {  
> error: "NullPointerException[null]",  
> status: 500
> 
> }
> 
> Is this a bug?
> 
> thanks
> 
> Barnaby

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [February 29, 2012, 2:43pm UTC](https://discuss.elastic.co/t/possible-bug-when-using-fields-on-arrays/6833/3 "2012-02-29T14:43:09Z")

</div>

Cool, I will push fix similar to what you suggested (just checking to null in the writeValue so it applies to all cases). Here is the opened issue: [NullPointerException when asking for null valued json field when fetching search request · Issue #1749 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1749).

On Wednesday, February 29, 2012 at 1:27 PM, barnybug wrote:

> I've submitted a pull request for this:  
> [Issue mentioned on list "Possible bug when using fields=... on arrays" by barnybug · Pull Request #1746 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/1746)
> 
> On Feb 28, 4:24 pm, barnybug \<[barny...@googlemail.com](mailto:barny...@googlemail.com) ([http://googlemail.com](http://googlemail.com))\> wrote:
> 
> > See gist:[gist:1933431 · GitHub](https://gist.github.com/1933431)
> > 
> > produces:  
> > {  
> > error: "NullPointerException[null]",  
> > status: 500
> > 
> > }
> > 
> > Is this a bug?
> > 
> > thanks
> > 
> > Barnaby

---

<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:** [July 6, 2017, 3:37am UTC](https://discuss.elastic.co/t/possible-bug-when-using-fields-on-arrays/6833/4 "2017-07-06T03:37:49Z")

</div>

Closed on July 6, 2017, 3:37am UTC