Seems like a reasonable thing to do. Examine the debug output to insure
that there's no short-circuiting being done as far as ConstantScoreQuery...
Best
Erick
On Tue, Mar 19, 2013 at 7:05 PM, adityab <aditya_ba...@yahoo.com> wrote:
> Hi All,
>
> I want to validate my approach by the experts, just to make sure i am on
> doing anything wrong.
>
> #Docs in Solr : 25M
> Solr Versin : 4.2
>
> Our requirement is to list top download document based on user country.
> So we have a dynamic field "*numdownload.**" which is evaluate as
> *numdownloads.<countryId>*
>
> Now as sorting is an expensive and also uses large amount of java heap, I
> planned to use this field in boosting result.
>
> Old Query
> q=*:*&fq=countryId:1&sort=numdownloads.1 desc
>
> which i changed to
> q={!boost b=numdownloads.1}*:*&fq=countryId:1
>
> Is my approach correct. Any better alternate ?
>
> thanks
> Aditya
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Too-many-fields-to-Sort-in-Solr-tp4049139.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
