You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: