[ 
https://issues.apache.org/jira/browse/SOLR-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974635#action_12974635
 ] 

Johannes Goll commented on SOLR-2295:
-------------------------------------

from Chris Hostetter

: I am getting a mal-formatted json response when using the
: stats component with a facet that returns a stddev value of NaN ,e.g

I'm not a JSON expert, but i suspect NaN just isn't legal JSON, and the
JSON response writer has a bug.

quick google search...
http://stackoverflow.com/questions/1423081/json-left-out-infinity-and-nan-json-status-in-ecmascript
...suggests that the only valid value is "null"

please file a bug.

-Hoss

> stats component | mal-formatted json response
> ---------------------------------------------
>
>                 Key: SOLR-2295
>                 URL: https://issues.apache.org/jira/browse/SOLR-2295
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Johannes Goll
>
> I am getting a mal-formatted json response when using the
> stats component with a facet that returns a stddev value of NaN ,e.g
>                   "facet-1":{
>                      "min":0.0604898,
>                      "max":0.0604898,
>                      "sum":1.209796,
>                      "count":20,
>                      "missing":0,
>                      "sumOfSquares":0.0731803180808,
>                      "mean":0.0604898,
>                      "stddev":NaN
>                   },
> I have submitted my complete response to
> http://jsonformatter.curiousconcept.com
> and got the following exception:
> Warning:Invalid quotes on string for the line with  "stddev":NaN
> The Solr response broke my PHP code; replacing "NaN" with 0.0 solved the 
> issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to