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 siblings described too :)
> On Nov 12, 2019, at 12:16, Walter Underwood <[email protected]> wrote: > > I explain it this way: > > * fq: filtering > * q: filtering and scoring > * bq: scoring > > wunder > Walter Underwood > [email protected] > http://observer.wunderwood.org/ (my blog) > >>> On Nov 12, 2019, at 9:08 AM, Erik Hatcher <[email protected]> wrote: >>> >>> >>> >>>> On Nov 12, 2019, at 12:01 PM, rhys J <[email protected]> wrote: >>> >>> On Tue, Nov 12, 2019 at 11:57 AM Erik Hatcher <[email protected]> >>> 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? >> >> That's right. Only `q` (and it's query parser associated params) are used >> for scoring. fq's narrow the result set, but don't influence score. >> >> Erik >> >
