I noticed you have an ‘&’ immediately preceding the "geodist() asc" at the very end of the query/URL; that’s supposed to be a comma since group.sort is a comma delimited list of sorts.
~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Mon, Mar 16, 2015 at 7:51 AM, kumarraj <rajitpro2...@gmail.com> wrote: > Hi, > > I am using group.sort to internally sort the values first based on > store(using function),then stock and finally distance and sort the output > results based on price, but solr does not return the correct results after > sorting. > Below is the sample query: > > q=*:*&start=0&rows=200&sort=pricecommon_double > > desc&d=321&spatial=true&sfield=store_location&fl=geodist(),*&pt=37.1037311,-76.5104751& > > > group.ngroups=true&group.limit=1&group.facet=true&group.field=code_string&group=true&group.sort=max(if(exists(query({!v='storeName_string:212'})),2,0),if(exists(query({!v='storeName_string:203'})),1,0)) > desc,inStock_boolean desc&geodist() asc > > > I am expecting all the docs to be sorted by price from high to low after > grouping, but i see the records not matching the order, Do you see any > issues with the query or having functions in group.sort is not supported in > solr? > > > > > Regards, > Raj > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-returns-incorrect-results-after-sorting-tp4193266.html > Sent from the Solr - User mailing list archive at Nabble.com. >
