Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11178

Unable to rank with any database collation that does not order all alphanumeric characters the same as ASCII

XMLWordPrintable

      Description

      This bug is caused by specific collation type such as Danish/Norwegian, Swedish/Finish treat the alphabetical ordering quite differently. For example, in Danish/Norwegian two letters "aa" are treated as a single letter, and comes after "z" in the alphabet. This causes the lexorank ordering to be wrong.

      Symptoms

      The following error message is seen in JIRA Agile when attempting an issue ranking operation.

      Diagnosis

        1. Check your collation type if it affects alphabetical ordering, ie Danish/Norwegian
        2. Run the following query : 
          SELECT 'ROWS_IN_BUCKET_0', "FIELD_ID", coalesce(COUNT(1), 0) AS rows_in_bucket FROM "AO_60DB71_LEXORANK" WHERE "RANK" LIKE '0|%' GROUP BY "FIELD_ID"
UNION
SELECT 'ROWS_IN_BUCKET_1', "FIELD_ID", coalesce(COUNT(1), 0) AS rows_in_bucket FROM "AO_60DB71_LEXORANK" WHERE "RANK" LIKE '1|%' GROUP BY "FIELD_ID"
UNION
SELECT 'ROWS_IN_BUCKET_2', "FIELD_ID", coalesce(COUNT(1), 0) AS rows_in_bucket FROM "AO_60DB71_LEXORANK" WHERE "RANK" LIKE '2|%' GROUP BY "FIELD_ID" ORDER BY "FIELD_ID";
        3. The results should show that there is a balancing going on (there will be 2 rows of results, with a number of issues in one bucket and another number in the other bucket)
        4. Enable DEBUG Logging for the balancer : com.atlassian.greenhopper.service.lexorank.balance
        5. From there, we can see that there is something wrong with the balancer. Notably, this line: 
          New rank[1|hzzzvz:] for issue[id=31321] for rank field[id=10890] already exists, retrying balance oepration

          This error shows that the Balancer is trying to insert a rank value that already exists.

      Workarounds

      Please refer to Unable to rank and/or balancer fails to complete due to incorrect database collation

        1. agile msg.png
          agile msg.png
          14 kB

            [JSWSERVER-11178] Unable to rank with any database collation that does not order all alphanumeric characters the same as ASCII

            Renata Dornelas made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 128687 ]
            Mac Przepiora (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 488140 ]
            Bugfix Automation Bot made changes -
            Minimum Version New: 6.05
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2853360 ] New: JAC Bug Workflow v3 [ 2937354 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546040 ] New: JAC Bug Workflow v2 [ 2853360 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550887 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546040 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme lexorank lexorank-perf warranty New: affects-server fixme lexorank lexorank-perf warranty
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909655 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550887 ]
            M (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 78818 ] New: This issue links to "Page (Extranet)" [ 78818 ]
            Tony Starr made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 128714 ] New: This issue links to "Page (Atlassian Documentation)" [ 128714 ]

              Unassigned Unassigned
              jtye Joe Wai Tye (Inactive)
              Affected customers:
              7 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: