From 9cf7350c02df1f4a2c213942edb62d89b468a568 Mon Sep 17 00:00:00 2001 From: Galen Charlton Date: Fri, 23 Oct 2015 17:18:19 +0000 Subject: [PATCH] LP#1505286: add release notes Signed-off-by: Galen Charlton Signed-off-by: Ben Shum --- .../OPAC/Limit_number_of_facets_retrieved.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt b/docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt new file mode 100644 index 0000000000..bd0c7ea13f --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt @@ -0,0 +1,14 @@ +Limit number of facets retrieved during search +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Catalog search now sets a limit on the number of facets retrieved +per defined facet field. Setting a limit is useful so that +`open-ils.cstore backends don't end up needlessly consuming +memory when fetching facets for a large result set; if a broad +search retrieves over 10,000 author facets (say), even the most +persistant user is not going to actually look at all of them. Fetching +fewer facets can also slightly speed up generation of search results. + +The limit is controlled by a new global flag, `search.max_facets_per_field`, +whose label is "Search: maximum number of facet values to retrieve for +each facet field". The default limit value is 1,000, but lower values +(e.g., 100) are perhaps even better for most catalogs. -- 2.43.2