Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-11879

Mapping rules order is wrong on Backends

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +

      There is a regression that appeared between 2.15.3 and 2.15.4.

      When making API calls (through APIcast), the metrics that are expected to be reported 1 time are reported twice.

      Investigation shows that the configuration of the mapping rules (the JSON that APIcast fetches from system) has the mapping rules (at backend level) in a different order.

      Even in the UI, the mapping rules appear in a different order, see the screenshots old.png and new.png.

      The position seems to be the same, but in the "old" version they are sorted by position in ascending order, and in the "new" - in descending.

        1. new.png
          new.png
          28 kB
        2. old.png
          old.png
          28 kB

              Unassigned Unassigned
              rhn-support-dmayorov Daria Mayorova
              Matej Dujava Matej Dujava
              Daria Mayorova Daria Mayorova
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: