[
https://issues.apache.org/jira/browse/OAK-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587054#comment-13587054
]
Marcel Reutegger commented on OAK-656:
--------------------------------------
There is no such thing as a repository wide default node type in JCR. Adding a
node without explicit node type name will consult the node type definition of
the parent node for matching child node definitions. It is however true that
once you have a nt:unstructured node, the default node type for child nodes is
again nt:unstructured.
> 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
