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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2013/02/26 14:42:12 UTC

[jira] [Resolved] (OAK-656) Large number of child nodes not working well with orderable node types

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

Thomas Mueller resolved OAK-656.
--------------------------------

    Resolution: Won't Fix

OK, so let's resolve this issue as WONTFIX.
                
> 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