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 "Amit Jain (JIRA)" <ji...@apache.org> on 2016/07/25 04:18:20 UTC
[jira] [Closed] (OAK-4564) Use Lucene index to look for long-named
nodes in JCR2 upgrade
[ https://issues.apache.org/jira/browse/OAK-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Jain closed OAK-4564.
--------------------------
Bulk Close 1.5.6
> 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)