: 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

Reply via email to