In some cases, the Pinot Broker REST API returns string values [e.g. "Infinity"] as results (as part of rows) when the value cannot be represented as a JSON "number".
To improve predictability from the Python client, should we parse this output string(s) as a Python native numeric type ?
Simply parsing with float should cover many cases and allow for more "natural" handling of Pinot's results from Python.
Should we apply a similar approach to parsing for other types ? (which ones ?)
Proposition: Enhancement
In some cases, the Pinot Broker REST API returns string values [e.g. "Infinity"] as results (as part of
rows
) when the value cannot be represented as a JSON "number".To improve predictability from the Python client, should we parse this output string(s) as a Python native numeric type ?
Simply parsing with
float
should cover many cases and allow for more "natural" handling of Pinot's results from Python.Should we apply a similar approach to parsing for other types ? (which ones ?)