[ 
https://issues.apache.org/jira/browse/OAK-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger resolved OAK-726.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7
    
> Implement KernelNodeState.hasChildNode()
> ----------------------------------------
>
>                 Key: OAK-726
>                 URL: https://issues.apache.org/jira/browse/OAK-726
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 0.7
>
>
> During tests I frequently see KernelNodeState.getChildPath() and 
> KernelNodeState.getChildNode() as hot spots. Some of those calls can be 
> avoided when KernelNodeState implements hasChildNode(). Currently it will 
> just fall back to the generic implementation in AbstractNodeState, which 
> attempts to load the child node. In most cases this is unnecessary when the 
> node state is a KernelNodeState because this implementation keeps the child 
> node names in a set (up to MAX_CHILD_NODE_NAMES).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to