Bug 19502: Add POD for max_result_window
authorJulian Maurice <julian.maurice@biblibre.com>
Mon, 25 Jun 2018 12:14:43 +0000 (14:14 +0200)
committerNick Clemens <nick@bywatersolutions.com>
Thu, 12 Jul 2018 13:04:23 +0000 (13:04 +0000)
Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Signed-off-by: Alex Arnaud <alex.arnaud@biblibre.com>
Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Koha/SearchEngine/Elasticsearch/Search.pm
Koha/SearchEngine/Zebra/Search.pm

index 6b2f2a9..a1598d7 100644 (file)
@@ -399,6 +399,15 @@ sub json2marc {
     return $marc;
 }
 
+=head2 max_result_window
+
+Returns the maximum number of results that can be fetched
+
+This directly requests Elasticsearch for the setting index.max_result_window (or
+the default value for this setting in case it is not set)
+
+=cut
+
 sub max_result_window {
     my ($self) = @_;
 
index 45c050c..576b9f5 100644 (file)
@@ -110,6 +110,14 @@ sub search_auth_compat {
     C4::AuthoritiesMarc::SearchAuthorities(@params);
 }
 
+=head2 max_result_window
+
+Returns the maximum number of results that can be fetched
+
+Zebra does not have such a limit, so it always returns undef
+
+=cut
+
 sub max_result_window { undef }
 
 1;