Hello Solr experts,
I'm writing a query expansion QueryComponent which takes web-app
parameters (e.g. profile information) and turns them into a solr query.
Thus far I've used lucene TermQuery-ies with success.
Now, I would like to use something a bit more elaborate. Either I write
it with
: My current expansion expands from the
:user-query
: to the
:+user-query favouring-query-depending-other-params overall-favoring-query
: (where the overall-favoring-query could be computed as a function).
: With the boost parameter, i'd do:
:(+user-query
Doug Turnbull wrote:
I'm not sure if you mean organizing function queries under the hood in a
query component or externally.
Externally, I've always followed John Berryman's great advice for working
with Solr when dealing with complex/reusable function queries and boosts
The boost parameter is part of the edismax query parser. If you have your
own query parser you could introduce your own argument boost and
interpret it as a value source. Here's the code that parses the external
function query in edismax
I'm not sure if you mean organizing function queries under the hood in a
query component or externally.
Externally, I've always followed John Berryman's great advice for working
with Solr when dealing with complex/reusable function queries and boosts
