You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/03/28 11:19:15 UTC

[jira] [Created] (OAK-726) Implement KernelNodeState.hasChildNode()

Marcel Reutegger created OAK-726:
------------------------------------

             Summary: 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


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