directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-2207) DefaultSearchEngine does not consider sizelimit
Date Thu, 24 Aug 2017 21:38:00 GMT


Emmanuel Lecharny commented on DIRSERVER-2207:

Regarding the {{sizeLimit}} handling, currently we only check the global server limit and
the request limit. You can change the request {{sizeLimit}} in any interceptor by calling
{{searchContext.setSizeLimit( <your limit> );}}. Be aware that is changing the semantic
of this value.

> DefaultSearchEngine does not consider sizelimit
> -----------------------------------------------
>                 Key: DIRSERVER-2207
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0-M24
>         Environment: independent
>            Reporter: Sebastian Roland
>            Priority: Minor
>             Fix For: 2.0.0
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> The DefaultSearchEngine is not considering the sizelimit set within the SearchOperationContext
as specified in the SearchEngine interface. As it is the only SearchEngine implementation
for Partitions so far all Partitions are affected.
> This is problematic in the sense that custom interceptors that would like to restrict
the sizelimit based upon certain conditions cannot easily do so by setting the sizelimit on
the SearchOperationContext.
> Currently only the sizelimit set by the client / server is considered. doSimpleSearch()
within the SearchRequestHandler triggers the interceptor processing ending with the call against
the partition which is using the DefaultSearchEngine to obtain the result set (ignoring the
sizelimit). When the result is returned back to the call within doSimpleSearch() the result
set is stripped to the sizelimit set by the client / server (whichever is less).
> To fix the issue the DefaultSearchEngine should consider the sizelimit set within the
SearchOperationContext. Stripping the result set is then obsolete.

This message was sent by Atlassian JIRA

View raw message