Custom created database index in AO_60DB71_LEXORANK table gets dropped during Jira startup

XMLWordPrintable

    • Type: Bug
    • Resolution: Invalid
    • Priority: Low
    • None
    • Affects Version/s: 7.13.5, 8.3.2
    • Component/s: Lexorank
    • None
    • 7.13
    • 1
    • Severity 3 - Minor

      Not a bug, this is expected behavior of the AO library, see comment below.

      Issue Summary

      Custom created database index in AO_60DB71_LEXORANK table gets dropped during Jira startup

      Steps to Reproduce

      1. Create a custom database index in Lexorank table, e.g.: 
        CREATE INDEX "index_ao_60db71_lex_Idx" ON "AO_60DB71_LEXORANK" (ID, LOCK_HASH, LOCK_TIME);
      2. Restart Jira

      Expected Results

      The index is retained in the database after the restart.

      Actual Results

      The index gets removed during the startup.

      Enabled SQL logging shows "DROP INDEX" command executed during startup in atlassian-jira.log:

      2020-02-26 12:41:46,992 active-objects-init-JiraTenantImpl{id='system'}-0 DEBUG anonymous     [n.java.ao.sql] DROP INDEX public."index_ao_60db71_lex_Idx"

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Marko Filipan (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: