Possible bug when using fields=... on arrays

barnybug · February 28, 2012, 4:24pm

See gist:

gist.github.com

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

gistfile1.txt

curl -XPOST 'http://127.0.0.1:9200/test/a/1?pretty=true' -d '{"b": {"i": [null]}}'
curl -XPOST 'http://127.0.0.1:9200/_all/_flush?pretty=true'
curl -XGET 'http://127.0.0.1:9200/test/a/_search?q=*&fields=b&pretty=true'

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

Is this a bug?

thanks

Barnaby

barnybug · February 29, 2012, 11:27am

I've submitted a pull request for this:

On Feb 28, 4:24 pm, barnybug barny...@googlemail.com wrote:

See gist:gist:1933431 · GitHub

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

}

Is this a bug?

thanks

Barnaby

kimchy · February 29, 2012, 2:43pm

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.

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

On Feb 28, 4:24 pm, barnybug <barny...@googlemail.com (http://googlemail.com)> wrote:

See gist:gist:1933431 · GitHub

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

}

Is this a bug?

thanks

Barnaby