Yes, I did observe the same on Chrome with Json response. And it seems to be a browser number parser issue.
Thanks, Kranti K. Parisa http://www.linkedin.com/in/krantiparisa On Fri, Sep 27, 2013 at 8:53 AM, Erick Erickson (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779893#comment-13779893] > > Erick Erickson commented on SOLR-5280: > -------------------------------------- > > After reproducing this in Chrome, I tried to create a quick junit test and > couldn't get it to fail there. > > So I tried Safari and it does NOT fail there, so it appears to be a > browser problem. > > Not sure there's anything we can do about it, but don't have time to > pursue it now. > > Checked the index and both the admin/schema browser and terms component > show the correct value in the index, which I could infer from the Safari > display too. > > > > Json response doesn't take long field type well > > ----------------------------------------------- > > > > Key: SOLR-5280 > > URL: https://issues.apache.org/jira/browse/SOLR-5280 > > Project: Solr > > Issue Type: Bug > > Components: Response Writers > > Affects Versions: 4.2 > > Reporter: Liu Xiang > > > > In my index, one field is defined as solr.LongField. > > After index, use solr webUI to fetch the doc. > > by default, xml response is as following, which is correct: > > <long>205840180000100338</long> > > <long>205840180000102563</long> > > Then Change "wt" to json, response is: > > [ > > 205840180000100350, > > 205840180000102560 > > ] > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
