Thanks Yonik! That was fast! We switched over to XML for the moment and will switch back to JSON when 4.3 comes out. Dave
-----Original Message----- From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley Sent: Monday, April 22, 2013 8:18 PM To: solr-user@lucene.apache.org Subject: Re: Bug? JSON output changes when switching to solr cloud Thanks David, I've confirmed this is still a problem in trunk and opened https://issues.apache.org/jira/browse/SOLR-4746 -Yonik http://lucidworks.com On Sun, Apr 21, 2013 at 11:16 PM, David Parks <davidpark...@yahoo.com> wrote: > We just took an installation of 4.1 which was working fine and changed > it to run as solr cloud. We encountered the most incredibly bizarre apparent bug: > > In the JSON output, a colon ':' changed to a comma ',', which of > course broke the JSON parser. I'm guessing I should file this as a > bug, but it was so odd I thought I'd post here before doing so. Demo below: > > Here is a query on our previous single-server instance: > > Query: > ---------- > http://10.1.3.28:8081/solr/select?q=book&fl=score%2Cid%2Cunique_catalo > g_name > &start=0&rows=50&wt=json&group=true&group.field=unique_catalog_name&gr > oup.li > mit=50 > > Response: > ------------- > {"responseHeader":{"status":0,"QTime":15714,"params":{"fl":"score,id,u > nique_ > catalog_name","start":"0","q":"book","group.limit":"50","group.field": > "uniqu > e_catalog_name","group":"true","wt":"json","rows":"50"}},"grouped":{"u > nique_ > catalog_name":{"matches":106711214,"groups":[{"groupValue":"ls:2653"," > doclis > t":{"numFound":103981882,"start":0,"maxScore":4.7039795,"docs":[{"id": > "10055 > 02088784","score":4.7039795},{"id":"1005500291075","score":4.7039795},{"id": > "1000810546074","score":4.7039795},{"id":"1000611003270","score":4.703 > 9795}, > > Note this part: > ------------------ > {"unique_catalog_name":{"matches": > > > > Now we run that same query on a server that was derived from the same > build, just configuration changes to run it in distributed "solr cloud" mode. > > Query: > --------- > http://10.1.3.18:8081/solr/select?q=book&fl=score%2Cid%2Cunique_catalo > g_name > &start=0&rows=50&wt=json&group=true&group.field=unique_catalog_name&gr > oup.li > mit=50 > > Response: > -------------{"responseHeader":{"status":0,"QTime":8855,"params":{"fl" > :"scor > e,id,unique_catalog_name","start":"0","q":"book","group.limit":"50","g > roup.f > ield":"unique_catalog_name","group":"true","wt":"json","rows":"50"}}," > groupe > d":["unique_catalog_name",{"matches":106711214,"groups":[{"groupValue" > :"ls:2 > 653","doclist":{"numFound":103981882,"start":0,"maxScore":4.7042913,"d > ocs":[ > {"id":"1005502088784","score":4.7042913},{"id":"1000611003270","score" > :4.704 > 2913},{"id":"1005500291075","score":4.703668},{"id":"1000810546074","score": > 4.703668}, > > Note how it's changed: > ---------------------------- > "unique_catalog_name",{"matches": > > > >
