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/09/19 09:55:54 UTC

[jira] [Resolved] (OAK-1023) Optimize many child nodes access

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

Marcel Reutegger resolved OAK-1023.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.10

Restricted the number of documents read to 'limit' and changed a test case which assumed the childNodeCount is accurate when the number of child nodes is equal to 'limit'.

http://svn.apache.org/r1524646

Resolving as fixed.
                
> Optimize many child nodes access
> --------------------------------
>
>                 Key: OAK-1023
>                 URL: https://issues.apache.org/jira/browse/OAK-1023
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>    Affects Versions: 0.9
>            Reporter: Marcel Reutegger
>             Fix For: 0.10
>
>
> Access to many child nodes is still somewhat slow with MongoMK. One area where this surfaces quite quickly is the UUID index, where all the UUIDs are stored as sibling nodes under the :index parent.

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