Thanks for the reply. I figured there is no simple solution here. I am parsing the query in my code separating out negations, assertions and such and building the final SOLR query to issue. I simply ue the boost as given by the user. If none given, I use a default boost for title & url matches.
- ashok hossman wrote: > > > : Query (can be quite complex, as it gets built from an advanced search > form): > : term1^2.0 OR term2 OR "term3 term4" > ... > : Any matches in the title or url fields should be weighed more. I can > specify > > if i'm understanding you correctly: the client app can provide any > arbitrary lucene syntax query, and you want to (server side) specify > additional information about how specific fields (if specified) should be > boosted ... is that correct? > > there is no way to do this with standard request handler out of the box > ... but you could subclass the LuceneQParser, and use your own QueryParser > subclass that knows about your field boosts and adds them -- don't forget > you'll have to decide what to do when the client specifies a boost on a > field you've got a configured boost for (add them? ... multiply them? ...) > > > > > -Hoss > > > -- View this message in context: http://www.nabble.com/Boost-a-query--by-field-at-query-time---Standard-Request-Handler-tp20842675p20920307.html Sent from the Solr - User mailing list archive at Nabble.com.
