[
https://issues.apache.org/jira/browse/OAK-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565257#comment-13565257
]
Thomas Mueller commented on OAK-333:
------------------------------------
> couple of hundres child nodes
Yes, I also saw slightly decreased performance for this case. However, I think
the normal case is just a few child node. Actually it would make sense to
gather some statistics about that (percentage of nodes with no child nodes,
percentage of nodes with x-y child node) so we have a better picture.
> The remaining problem is where those nodes are stored on disk. But I guess
> that's something we cannot control anyway if we depend on a 3rd party storage
> mechanism like MongoDB or H2.
Well, if the key is randomly distributed, then it will be slow in any storage
engine (MongoDB, Oracle, MySQL, PostgreSQL, Cassandra, and so on), with very
few exceptions. One exception is in-memory storage, the second exception is if
the value is relatively large (a few megabytes) such that reading the value is
the bottleneck and not indexing.
> 1000 character path limit in MongoMK
> ------------------------------------
>
> Key: OAK-333
> URL: https://issues.apache.org/jira/browse/OAK-333
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 0.5
> Reporter: Mete Atamel
> Assignee: Mete Atamel
> Priority: Minor
> Attachments: OAK-333.patch
>
>
> In an infinite loop try to add nodes one under another to have N0/N1/N2...NN.
> At some point, the current parent node will not be found and the current
> commit will fail. I think this happens when the path length exceeds 1000
> characters. Is this enough for a path? I was able to create this way only 222
> levels in the tree (and my node names were really short N1, N2 ...)
> There's an automated tests for this: NodeExistsCommandMongoTest.testTreeDepth
--
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
