Bug 19502: Add POD for max_result_window

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>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
(cherry picked from commit c3576b1ade)
Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com>
This commit is contained in:
Julian Maurice 2018-06-25 14:14:43 +02:00 committed by Fridolin Somers
parent 9b5202cc1e
commit 4e87e8bb74
2 changed files with 17 additions and 0 deletions

View 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) = @_;

View 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;