[
https://issues.apache.org/jira/browse/OAK-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587022#comment-13587022
]
Thomas Mueller commented on OAK-656:
------------------------------------
AFAIK the default node type (nt:unstructured) is orderable, so it's quite
likely that many users will run into this problem.
Can use use a different default node type in Oak?
Or we could try to fix the issue. For example, in the property ":childOrder"
just store the first 20 children, with an ellipses marker. And in the last
child, add a property ":nextSiblings" that points to the next 20.
> Large number of child nodes not working well with orderable node types
> ----------------------------------------------------------------------
>
> Key: OAK-656
> URL: https://issues.apache.org/jira/browse/OAK-656
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Thomas Mueller
> Priority: Minor
>
> When adding many child nodes to an orderable node, oak gets slower and slower
> and eventually runs out of memory. The problem seems to be the property
> ":childOrder" which gets larger and larger. The effect is the same as with
> Jackrabbit 2.x storing the list of child nodes in a node.
--
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
