-
Notifications
You must be signed in to change notification settings - Fork 1.2k
BoxPlotAggregate - JsonParsingException: expected:'Number Token', actual:'"NaN"', at offset:318 #6050
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for raising this @smissingham and my apologies for the very slow response from my side. We have a potential solution for the |
@smissingham I've decided on the cleanest solution which is to use the |
Good point @stevejgordon using double constants. Maybe double.NaN is a better fit as well for the NaN values, than null? |
Yep, that should be in place with the change. |
NEST/Elasticsearch.Net version: 7.15
Elasticsearch version: 8.0.0-alpha2
.NET runtime version: .NETFramework v4.8
Operating system version: Windows 11
Description of the problem including expected versus actual behavior:
Json deserializer throws
expected:'Number Token', actual:'"NaN"', at offset:318
whenBoxPlotAggregate
results returns "NaN".Same for other potential non-numeric values "Infinity", "-Infinity"
Steps to reproduce:
Run the below BoxPlotAggregate query with NEST, it will fail to deserialize the "NaN" for "lower" prop
Expected behavior
I think these non-numeric results should deserialize to null (but I'm sure there's some debate to be had here).
Stack Trace
The text was updated successfully, but these errors were encountered: