You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2010/06/02 20:03:40 UTC

[jira] Commented: (DIRSERVER-1219) Review and make sure eagar loading of target entries in OperationContexts occurs at most once

    [ https://issues.apache.org/jira/browse/DIRSERVER-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874709#action_12874709 ] 

Emmanuel Lecharny commented on DIRSERVER-1219:
----------------------------------------------

The eagerPopulate() method is now used, and works well when necessary The Add, Delete, and Modify operations are using it. On the other hand, Search and Lookup operations don't call this method.

I still have to review the Moddn and Compare operations

> Review and make sure eagar loading of target entries in OperationContexts occurs at most once
> ---------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1219
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1219
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Alex Karasulu
>            Assignee: Emmanuel Lecharny
>             Fix For: 2.0.0-RC1
>
>
> We have added an entry property to all operation contexts as well as a superior (entry) field to MoveOperationContext.  This was done so we do not have redundant lookups occurring.  It's to facilitate performance in the server.  The problem is this feature is not being used at all. The interceptors doing lookups are not stuffing the entry back into the opctx.  Neither are they checking to see if the entry was already looked up and reusinig it.  
> This requires a kind of audit and review.  Perhaps best done during RC releases before 2.0 while optimizations are being investigated.  Note that this should be done after the following issue is dealt with to prevent problems with entries that are looked up and empty with no attributes: DIRSERVER-1218

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.