I wonder if the idea is that fastMatchQuery provides additional
filtering to only documents that might match one of the ranges being
faceted on. As a (somewhat contrived) example, what if you were
searching over items in an ecommerce catalog that all contain an
indexed numeric "price" attribute, an
great, thanks!
Am 26.04.22 um 21:48 schrieb Michael Sokolov:
thanks, I fixed the doc!
On Tue, Apr 26, 2022 at 9:13 AM Bridger Dyson-Smith
wrote:
Hi Michael -
On Mon, Apr 25, 2022 at 5:38 PM Michael Wechner
wrote:
Hi Bridger
Inside
https://dlcdn.apache.org/lucene/java/9.1.0/lucene-9.1.0.
thanks, I fixed the doc!
On Tue, Apr 26, 2022 at 9:13 AM Bridger Dyson-Smith
wrote:
>
> Hi Michael -
>
> On Mon, Apr 25, 2022 at 5:38 PM Michael Wechner
> wrote:
>
> > Hi Bridger
> >
> > Inside
> >
> > https://dlcdn.apache.org/lucene/java/9.1.0/lucene-9.1.0.tgz
> >
> > you should find
> >
> > mo
Looking at git blame I see the current parameter was added here:
https://issues.apache.org/jira/browse/LUCENE-6648. Previous
implementations supported a BitSet rather than a Query. I'm not really
sure what the use case is for applying additional filtering when
faceting. Perhaps it can support somet
Hi Michael -
On Mon, Apr 25, 2022 at 5:38 PM Michael Wechner
wrote:
> Hi Bridger
>
> Inside
>
> https://dlcdn.apache.org/lucene/java/9.1.0/lucene-9.1.0.tgz
>
> you should find
>
> modules/lucene-core-9.1.0.jar
> modules/lucene-queryparser-9.1.0.jar
> modules/lucene-analysis-common-9.1.0.jar
> mo
