[ https://issues.apache.org/jira/browse/OAK-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379207#comment-15379207 ]
Tomek Rękawek commented on OAK-4564: ------------------------------------ Fixed for trunk in [r1752815|https://svn.apache.org/r1752815]. > Use Lucene index to look for long-named nodes in JCR2 upgrade > ------------------------------------------------------------- > > Key: OAK-4564 > URL: https://issues.apache.org/jira/browse/OAK-4564 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: upgrade > Reporter: Tomek Rękawek > Fix For: 1.6, 1.5.6 > > > oak-upgrade should perform a check for presence of node with long names. One > approach as suggested by [~mreutegg] is to perform this check via Lucene index > {quote} > we could use the lucene index of the source repository. the node name > is indexed and a scan of those terms with a length check would be > quite efficient. > {quote} > The expected behavior can be > # oak-upgrade starts and constructs the JR2 instances > # It performs the node name check and collects such node names. > # If the above list is not empty it terminates the migration providing > details about the problamatic paths > # User then has an option to > ## Restart the migration with {{--skip-name-check}} > ## Fix the content and then migrate -- This message was sent by Atlassian JIRA (v6.3.4#6332)