gsmiller opened a new pull request, #12408:
URL: https://github.com/apache/lucene/pull/12408
This change proposes some faceting optimizations for situations where there
are no hits to facet over. While this seems like an odd scenario, at Amazon
product search we actually have some situations where this can become common
(sparse queries that don't have results in some segments, or have no results
altogether).
You could argue that the calling code should handle this optimization and
avoid faceting altogether if there are no hits, but that only solves for the
case of no results, not no results in some segments. I think it's also nice to
move this optimization into the faceting module so that every user doesn't have
to do this themselves.
Curious what people think of this idea. Happy to hear feedback,
counterarguments, etc. :)
This change covers:
* Taxonomy faceting
* FastTaxonomyFacetCounts
* TaxonomyFacetIntAssociations
* TaxonomyFacetFloatAssociations
* SSDV faceting
* SortedSetDocValuesFacetCounts
* ConcurrentSortedSetDocValuesFacetCounts
* StringValueFacetCounts
* Range faceting:
* LongRangeFacetCounts
* DoubleRangeFacetCounts
* Long faceting:
* LongValueFacetCounts
Left for a future iteration (I'll open a follow up issue if we move forward
with this one):
* RangeOnRange faceting
* FacetSet faceting
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
