[
https://issues.apache.org/jira/browse/OAK-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914407#comment-13914407
]
Julian Reschke commented on OAK-333:
------------------------------------
A few comments:
1) The limit is on bytes, not characters; thus you can have ~1000 ASCII
characters, but only ~333 Euro signs, because of UTF-8. So this may be a much
bigger problem for non-western locales
2) Another problem is that until recently, mongodb did accept the write
operation and just failed to update the index; thus the persistence problem is
obscured, and may not surface anytime soon due to caching. mongodb 2.5.5 fixes
that (see https://jira.mongodb.org/browse/SERVER-5290, I just verified with
/mongodb-win32-x86_64-2008plus-2.6.0-rc0)
> 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
> Priority: Minor
> Fix For: 0.18
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
