Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-30059

documented limitations of going back to OrientDB from PostgreSQL/H2 migration are not clear enough

    Details

    • Notability:
      3

      Description

      According to the documentation it should be possible to revert back to OrientDB following a migration to Postgres

      https://help. sonatype.com/repomanager3/installation-and-upgrades/migrating-to-a-new-database

      However given the Reconcile from blobstore implementation for OrientDB task does not consume blobs created when on the new DB platform, then in actuality, reverting back from PostgreSQL is only feasible if the migrated instance has not created new blobs in the original blobstore - basically if the new migrated instance has not been actually used for anything other than blobstore reads. Since blobs can sometimes get deleted and replaced, the exact semantics of read-only is not well understood for each format and blobstore type.

      Expected

      Make it very clear in documentation that reverting back to using OrientDB is only possible using blobstores and OrientDB databases backed up immediately before upgrading to postgreSQL or H2. ONE CANNOT DO THIS:

      1. Migrate from OrientDB to PostgreSQL/H2
      2. Use PostgreSQL/H2 for some period of time
      3. Stop PostgreSQL/H2 and use OrientDB again against the same blobstores that PostgreSQL/H2 had used, and expect blobs that new DB created to be available.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              dkane Daniel Kane
              Last Updated By:
              Michael Oliverio Michael Oliverio
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  tigCommentSecurity.panel-title