By the way, I was wrong when saying that using bf instead of !boost did not
work either. I probably hit more than one problem at the same time when I first
tested that.
I've retested now and this works:
/select?q=+id:12345^0.01 +_query_:"{!dismax
v=$qq}"&bf=recip(ms(NOW/DAY,published_date),
Hi,
The query is generated dynamically and can be more or less complex depending on
different parameters. I'm also not free to give many details of our
implementation, but I'll give you the minimal query string that fails and the
relevant pieces of the config.
The query string is:
/select?q=+i
: As I said in my previous message, if I issue:
: q=+field1:range +field2:value +_query_:{!dismax v=$qq}
: highlighting works. I've just discovered the problem is not just with
{!boost...}. If I just add a bf parameter to the previous query, highlighting
also fails.
: Anybody knows what can be h
Hi,
I need to boost newer documents in my dismax queries.
As I've been able to read in the wiki, it's best to use a multiplicative
boost. The only way I know to do this with the dismax (not edismax)
query parser is via a {!boost b=$dateboost v=$qq defType=dismax} query.
To make things more complic
