https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39173 Bug ID: 39173 Summary: maxRecordsForFacets doesn't seem to apply to Elasticsearch, only to Zebra, the docs should clarify that Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation Assignee: koha-bugs@lists.koha-community.org Reporter: schodkowy.omegi-0r@icloud.com QA Contact: testopia@bugs.koha-community.org CC: aude.charillon@ptfs-europe.com, philip.orr@lmscloud.de 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. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.