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

Database migrator does not migrate Repository Export or Import tasks

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.38.1, 3.40.1
    • Fix Version/s: None
    • Component/s: Database Migrator
    • Labels:
    • Notability:
      4

      Description

      The database migrator will currently exclude migrating Repository Import and Repository Export tasks.

      This appears to be an unintentional side effect of implementing NEXUS-25498.

      Customers are currently expecting all tasks to migrate to SQL database. There is no documentation stating what will be excluded. Also there is no known reason why it is preferred not to migrate the export / import tasks.

      Expected

      Provide option? to migrate Export / Import tasks for supported repo formats. It still might require these tasks be edited after the migration since the paths defined to either export or import may not exist on the ultimate instance that will end up using the new database. However there is no way for us to know for sure.

      Document what scheduled tasks are deliberately excluded from migration and why.

      Alter the log statements that indicate a task is excluded to include the clear reason WHY it was excluded.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Michael Oliverio Michael Oliverio
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                tigCommentSecurity.panel-title