[
https://issues.apache.org/jira/browse/OAK-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567523#comment-13567523
]
Marcel Reutegger commented on OAK-231:
--------------------------------------
As mentioned in OAK-586, the child count is IMO more problematic because it
must be exact. This either means the implementation needs to maintain the value
somewhere and must update it whenever a node is added or removed. This requires
synchronization on this value and causes contention. On the other hand an
implementation, which choses to not store the child node count is forced to
count the potentially many child nodes. I think it would be better to get rid
of the child node count.
The JCR API specifically allows an implementation to return -1 for the size of
a RangeIterator. I think we should make use of this in Oak as well. That is,
:childNodeCount may return -1 if the implementation does not know the exact
number of child nodes and there exist more than the requested number of child
nodes.
> Support for large child node lists
> ----------------------------------
>
> Key: OAK-231
> URL: https://issues.apache.org/jira/browse/OAK-231
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mk
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
>
--
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
