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

Asset Name Matcher in Cleanup policy needs an extra leading "/" with PostgreSQL

    Details

    • Notability:
      3

      Description

      Problem

           With PostgreSQL or migrating database from OrientDB to PostgreSQL. Nexus Repo 3 adds a leading "/" in an Asset name, which causes the below issue:

            When creating a clean-up policy, the user needs to add an extra leading "/" in Asset Name Matcher, which according to AssetNameMatcher

      An asset name does not begin with a leading slash. This is different than the asset request path value used when evaluating Content Selector (CSEL) or Routing Rule expressions. 

           
          If the user migrates from the OrientDB to PostgreSQL, then the user may need to change all the clean-up policies with Asset Name Matcher that worked in Orient. The same cleanup policy asset name matcher may NOT work in PostgreSQL without adjustment. 

          Please see attached file for details

      Expected

      Ensure that after migrating to PostgreSQL from Orient, cleanup policies that were working, keep working without any manual changes.
      Adjust documents describing any differences in cleanup policy asset name matchers when migrating to PostgreSQL. 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              dqiu Daolong Qiu
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  tigCommentSecurity.panel-title