[
https://issues.apache.org/jira/browse/OAK-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565261#comment-13565261
]
Thomas Mueller edited comment on OAK-333 at 1/29/13 10:45 AM:
--------------------------------------------------------------
> node name limit
I wonder how big the problem is. Non-ASCII characters are converted to
{{__x0000__}} as far as I know, so 7 bytes per character. With SHA-1, 41
characters are needed for the prefix, so that a node name might contain up to
137 non-ASCII characters. When storing a title or subject (possibly user
generated) in a node name that's still a bit low I think.
was (Author: tmueller):
> node name limit
I wonder how big the problem is. Non-ASCII characters are converted to _x0000_
as far as I know, so 7 bytes per character. With SHA-1, 41 characters are
needed for the prefix, so that a node name might contain up to 137 non-ASCII
characters. When storing a title or subject (possibly user generated) in a node
name that's still a bit low I think.
> 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