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

NuGet Component fetch from group repo does not respect repository ordering

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0-m5
    • Component/s: Browse Storage, CMA, Search
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      Sprint 48, Sprint 49

      Description

      The expectation is that if a component is present in more than one repository, the ordering of group members will determine which one is returned. Presently we just return the first matching record, regardless of the configuration, although the query executed is indeed different.
      Given a hosted repository to which I've published a component downloaded from a proxy, both of these queries return the same result regardless of the group membership configuration:

      select from asset where (component.name = 'jQuery' AND component.version = '2.1.4') and (bucket.repository_name = 'nuget.org-proxy' or bucket.repository_name = 'nuget-hosted') GROUP BY name
      select from asset where (component.name = 'jQuery' AND component.version = '2.1.4') and (bucket.repository_name = 'nuget-hosted' or bucket.repository_name = 'nuget.org-proxy') GROUP BY name
      

      Similarly, browsing a group repository will show the same component regardless of the group membership ordering.

      Test for this condition is presently @Ignore in NugetGroupIT, and should be re-enabled to confirm this when fixed.

        Attachments

          Activity

            People

            Assignee:
            mprescott Michael Prescott
            Reporter:
            krobinson Kelly Robinson
            Last Updated By:
            Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title