Incompatibility with ElasticSearch 1.0 when using .Fields()

[khaledh]

According to elastic/elasticsearch#4542 there has been a change to the JSON returned by ES when using the fields search option. The change forces all fields to be returned as an array, even if the field is single-valued. This causes a JSON deserialization exception: Error reading integer. Unexpected token: StartArray. because the deserializer expects a single value, but actually encounters an array.

In a way this is similar to the issue in #227, but in that issue it was the opposite problem: expecting an array but sometimes encountering single values.

It looks like this can be worked around by adding a custom JSON converter to handle the case when fields are returned as arrays, but I think this should be handled internally by NEST. No?

[Mpdreamz]

Hi @khaledh this is very true, the upcoming release that adds support for the 1.0 elasticsearch release has support for this and the new source include/exclude (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-source-field.html#include-exclude) which sort of take the place of the old fields mechanism (only better).

NEST 0.9.12.0 is NOT compatible with 1.0.

Thanks for reporting, keep'm comming 👍

[khaledh]

Thanks for the update @Mpdreamz. I managed to work-around the problem by writing a custom JSON converter for now.

Keep up the good work!