[
https://issues.apache.org/jira/browse/DIRSERVER-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623698#action_12623698
]
Alex Karasulu commented on DIRSERVER-1212:
------------------------------------------
The problem is we may be in an index scan for some time while conducting the
search. For example a SubstringCursor on ou=*foo might scan the entire ou
index looking for a match when the cursor.first() method is called. The
partition will not be able to intervene to stop this scan if the time limits
are up.
The reason for this is because in cursor.first() you're basically stuck in a
loop that is going through the index and checking for matches based on the
index. To get out of this loop in time you need the loop in the Cursor to
check a variable to see if it should stop or if it has been closed() or
canceled().
Does this make more sense?
> Size time limits on SearchControls broken in core-jndi
> ------------------------------------------------------
>
> Key: DIRSERVER-1212
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1212
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.4
>
>
> I commented out some tests in SearchIT.java in core-integ that rely on the
> correct operation of search size and time limits through paramters in a
> SearchControls object. This is not working any longer. Fix it and remove
> @Ignore tags.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
