Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-4564

Use Lucene index to look for long-named nodes in JCR2 upgrade

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.12, 1.5.6, 1.6.0
    • Component/s: upgrade
    • Labels:
      None

      Description

      oak-upgrade should perform a check for presence of node with long names. One approach as suggested by Marcel Reutegger is to perform this check via Lucene index

      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.

      The expected behavior can be

      1. oak-upgrade starts and constructs the JR2 instances
      2. It performs the node name check and collects such node names.
      3. If the above list is not empty it terminates the migration providing details about the problamatic paths
      4. User then has an option to
        1. Restart the migration with --skip-name-check
        2. Fix the content and then migrate

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                tomek.rekawek Tomek Rękawek
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: