[
https://issues.apache.org/jira/browse/DIRSERVER-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141213#comment-16141213
]
Sebastian Roland edited comment on DIRSERVER-2207 at 8/25/17 5:27 AM:
----------------------------------------------------------------------
What kind of effect does changing the sizelimit using
{code:java}
searchContext.setSizeLimit( <your limit> );
{code}
has?
was (Author: seroland86):
What kind of effect does changing the sizelimit using
{quote}searchContext.setSizeLimit( <your limit> );{quote} has?
> DefaultSearchEngine does not consider sizelimit
> -----------------------------------------------
>
> Key: DIRSERVER-2207
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2207
> 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
(v6.4.14#64029)
