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

["Thomas Mueller (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368802#comment-14368802 ] 

Thomas Mueller commented on OAK-2636:
-------------------------------------

Yes, this should be fixed. I created OAK-2644 (Lift the 150 character limit on node names) to track this.

I have documented this here now: http://jackrabbit.apache.org/oak/docs/differences.html (Node Name Length Limit)

> 2) the values themselves should be OSGI properties, not System Properties

Well, it should not be needed at all, and people are not supposed to change them, so I think OSGi properties are not needed.

I will resolve the issue as duplicate of OAK-2644 (please comment if you think that's the wrong resolution).

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