Possible bug when using fields=... on arrays

Elastic Stack Elasticsearch
1

See gist:

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

Is this a bug?

thanks

Barnaby

2

I've submitted a pull request for this:

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

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

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

}

Is this a bug?

thanks

Barnaby

3

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: 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:
https://github.com/elasticsearch/elasticsearch/pull/1746

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

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

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

}

Is this a bug?

thanks

Barnaby

4