[OAK-2636] Issues with Maximum node name size and path size

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.1.7
• Fix Version/s: 1.3.0, 1.4
• Component/s: doc, mongomk
• Assignee: Unassigned
• Reporter: Will McGauley
• Created: 16/Mar/15 16:22
• Updated: 02/Mar/16 15:38
• Resolved: 19/Mar/15 10:07

Description

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

Issue Links

• duplicates: OAK-2644 Lift the 150 character limit on node names
• is related to: OAK-2644 Lift the 150 character limit on node names
• relates to: SLING-4509 Job creation fails if combination of topic and name is too long on OAK
• relates to: OAK-333 1000 byte path limit in MongoMK