: 1. Each piece is still subject to the IDF component of the score,
: requiring me to make each individual category have a boost factoring
: that in. For example, if I want meta:promote to be twice as boosted as
: category:featured, I can't simply boost the first to 2 and the second to
: 1
On 4/5/2011 1:17 PM, Chris Hostetter wrote:
the boost param of edismax is probably a lot better choice then either
bq/bf -- but it really depends on wether you want an additive boost or a
multiplicitive one (of course with teh function query syntax add(),
product() and (query() can be combined
On Wed, Apr 6, 2011 at 12:00 PM, Shawn Heisey s...@elyograg.org wrote:
We aren't yet using dismax in production, but I've had it in my config for a
while now. I've changed it to edismax in the 3.1 setup I'm putting together
now. It has the following in the bf parameter:
On Apr 5, 2011, at 3:17 PM, Chris Hostetter wrote:
one of the original use cases for bq was for artificial keyword boosting,
in which case it still comes in handy...
bq=meta:promote^100 text:new^10 category:featured^100 (*:*
-category:accessories)^10
Yeah I thought of this specific
Short answer: the existence is entirely historic. I added bq because i
needed it, and then i added bf because the _val_:... syntax was anoying.
: can't think of a useful case when I want to both *add* a component to
: the ultimate score, and for that component to be a non-function query
:
As I was reviewing the boosting capabilities of the dismax edismax query
parsers, it's not clear to me that the boost query has much use. The value
of boost functions, particularly with a multiplied boost that edismax supports,
is very clear -- there are a variety of uses. But I can't think
