To add bq in there makes it query parser specific. But I’m being pedantic
since most folks are using edismax where that applies (along with a bunch of
other params that would also deserve mention, like boost and bf). q and fq,
agreed for the explanation. bq mentioned only if specifics and sib
I explain it this way:
* fq: filtering
* q: filtering and scoring
* bq: scoring
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Nov 12, 2019, at 9:08 AM, Erik Hatcher wrote:
>
>
>
>> On Nov 12, 2019, at 12:01 PM, rhys J wrote:
>>
>> On Tue, Nov
> On Nov 12, 2019, at 12:01 PM, rhys J wrote:
>
> On Tue, Nov 12, 2019 at 11:57 AM Erik Hatcher
> wrote:
>
>> fq is a filter query, and thus narrows the result set provided by the q
>> down to what also matches all specified fq's.
>>
>>
> So this can be used instead of scoring? Or alongsid
On Tue, Nov 12, 2019 at 11:57 AM Erik Hatcher
wrote:
> fq is a filter query, and thus narrows the result set provided by the q
> down to what also matches all specified fq's.
>
>
So this can be used instead of scoring? Or alongside scoring?
> You gave it a query, "cat_ref_no", which literally l
fq is a filter query, and thus narrows the result set provided by the q down to
what also matches all specified fq's.
You gave it a query, "cat_ref_no", which literally looks for that string in
your default field. Looking at your q parameter, cat_ref_no looks like a
field name, and your fq sh
