On 4/4/2014 12:48 AM, Alvaro Cabrerizo wrote: > By default solr is using the sort parameter over the "score field". So if > you overwrite it using other sort field, yes solr will use the parameter > you've provided. Remember, you can use multiple fields for > sorting<http://wiki.apache.org/solr/CommonQueryParameters#sort> so > you can make something like: sort score desc, your_field1 asc, your_field2 > desc.... > > The score of documents is calculated on every query (it does not depend on > the sort parameter or the debugQueryParameter) and the debubQuery is only a > mechanism for showing (or hidding) how score was calculated. If you want to > see a document score for a particular query (apart from the debugQuery) you > can ask for it in the solr response adding the parameter *fl=*,score* to > your request.
These are things that I already know. What I want to know is whether Solr has code in place that will avoid wasting CPU cycles calculating the score that will never be displayed or used, *especially* the complex boost parameter that's in the request handler definition (solrconfig.xml). <str name="boost">min(recip(abs(ms(NOW/HOUR,registered_date)),1.92901e-10,1.5,1.5),0.85)</str> Do I need to send 'boost=' as a parameter (along with my sort) to get it to avoid that calculation? Thanks, Shawn
