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
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
