Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
min/max currently return NaN when there are no values for a bucket.
This is problematic in JSON format, which has no support for NaN. It becomes a bigger issue for typed support like long values where NaN doesn't make sense, and even worse for String fields, since 'NaN' is an actual valid string value. Instead, we should just omit the aggregation value altogether.