To those interested, I was able to disable coord factor by overriding it in
a new CustomSimilarity jar file. This can effectively sum the scores from
multiple edismax queries.
However, I'd be interested in any other methods which are able to do
not-just-direct-sums and can work on other logics for
This does indeed reduce the time. but doesn't quite do what I wanted. This
approach penalizes the docs based on "coord" factor. In other words, for a
doc with scores=5 on just one query (and nothing on others), the resulting
score would now be 5/3 since only one clause matches.
1. I wonder why doe
maybe something like q=
({!edismax v=$q1} OR {!edismax v=$q2} OR {!edismax ... v=$q3})
and setting q1, q2, q3 as needed (or all to the same maybe with different qf’s
and such)
Erik
> On Apr 9, 2019, at 09:12, sidharth228 wrote:
>
> I did infact use "bf" parameter for ind
I did infact use "bf" parameter for individual edismax queries.
However, the reason I can't condense these edismax queries into a single
edismax query is because each of them uses different fields in "qf".
Basically what I'm trying to do is this: each of these edismax queries (q1,
q2, q3) has a
Function queries in ‘q’ score EVERY DOCUMENT. Use ‘bf’ or ‘boost’ for the
function part, so its only computed on main query matching docs.
Erik
> On Apr 9, 2019, at 03:29, Sidharth Negi wrote:
>
> Hi,
>
> I'm working with "edismax" and "function-query" parsers in Solr and have
> diffi
