Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11
    • Component/s: core, jcr, mk
    • Labels:
      None

      Description

      There should be a mechanism, similar to the backup/migration tool in jackrabbit-standalone, that allows us to migrate content from existing Jackrabbit repositories to Oak.

      Content should get migrated as-is with as few changes to the content structure as possible (ideally none). Extra Oak content like pre-compiled type and ACL infromation and search indexes should be added on top of existing content, ideally by using the normal commit hooks to process the entire migrated set of content.

      It would also be useful if the migration could avoid copying large binaries from an existing DataStore that the target MK can access (see OAK-805).

        Issue Links

          Activity

            People

            • Assignee:
              Jukka Zitting
              Reporter:
              Jukka Zitting
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development