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 2015/03/19 11:08:38 UTC

[jira] [Resolved] (OAK-2636) Issues with Maximum node name size and path size

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

Thomas Mueller resolved OAK-2636.
---------------------------------
    Resolution: Duplicate

> Issues with Maximum node name size and path size
> ------------------------------------------------
>
>                 Key: OAK-2636
>                 URL: https://issues.apache.org/jira/browse/OAK-2636
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: doc, mongomk
>    Affects Versions: 1.1.7
>            Reporter: Will McGauley
>             Fix For: 1.3.0
>
>
> I ran across the maximum allowed node name and path lengths in "Utils.java" by getting an exception when attempting to create nodes which violated the policy.  I believe this is a backwards compatibility issue and the following should occur:
> 1) there should be documentation about this.  Why are there maximums? Can the default maximums be increased?  Is this only applicable to some MKs like Mongo or are they enforced globally?  
> 2) the values themselves should be OSGI properties, not System Properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)