Bug 39173 - maxRecordsForFacets doesn't seem to apply to Elasticsearch, only to Zebra, the docs should clarify that
Summary: maxRecordsForFacets doesn't seem to apply to Elasticsearch, only to Zebra, th...
Status: Needs documenting
Alias: None
Product: Koha
Classification: Unclassified
Component: Documentation (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-19 20:05 UTC by Michał
Modified: 2025-02-20 10:12 UTC (History)
1 user (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał 2025-02-19 20:05:56 UTC
As in title, the "maxRecordsForFacets" pref has a scary warning about performance. But the setting seems to be wholly ignored by Elasticsearch (and it makes sense, you can test by setting the value to some ridiculously low number while showing facets and then see the counts are much higher, if searching for "*").

So the pref should mention it's only for Zebra.



And then ALSO, as #2 thing, displayFacetCount, it has this mention:

1. "The relevance of these numbers highly depends on the value of the maxRecordsForFacets preference."

2. "Showing these numbers can potentially affect the performance of your searching, so test your system with different values for this preference to see what works best."


Fix:

1. Only with Zebra. Clarify that with ES, the full proper real number of facet count will be displayed.

2. Only with Zebra. Explicitly clarify that on ES there's no performance hit to showing facet counts.