[
https://issues.apache.org/jira/browse/OAK-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996762#comment-14996762
]
Tomek Rękawek commented on OAK-3111:
------------------------------------
I created a [branch|https://github.com/trekawek/jackrabbit-oak/tree/OAK-3111]
with the new
[LongNameTest|https://github.com/trekawek/jackrabbit-oak/blob/OAK-3111/oak-upgrade/src/test/java/org/apache/jackrabbit/oak/upgrade/LongNameTest.java].
Apparently, migrating a node with a long name may cause an exception. I'll
look into this.
> Reconsider check for max node name length
> -----------------------------------------
>
> Key: OAK-3111
> URL: https://issues.apache.org/jira/browse/OAK-3111
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: upgrade
> Reporter: Julian Sedding
> Priority: Minor
>
> In OAK-2619 the necessity of a check for node name length was briefly
> discussed. It may be worthwhile to write a test case for upgrading long node
> names and find out what happens with and without the check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
