in-place upgrade job does not catch 3.13 to 4.0 data schema changes

XMLWordPrintable

    • Type: Bug
    • Resolution: Answered
    • Priority: Low
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      The JIRA 4.0 Database Schema Changes for MySQL and Oracle are not captured during the "in-place" upgrade.

      The error message looks like:

      2011-04-05 22:29:44,248 Thread-1 ERROR      [core.entity.jdbc.DatabaseUtil] WARNING: Column "PROPERTYVALUE" of table "propertytext" of entity "OSPropertyText" is of type "TEXT" in the database, but is defined as type "LONGTEXT" in the entity definition.
2011-04-05 22:29:44,263 Thread-1 ERROR      [core.entity.jdbc.DatabaseUtil] WARNING: Column "REQCONTENT" of table "searchrequest" of entity "SearchRequest" is of type "TEXT" in the database, but is defined as type "LONGTEXT" in the entity definition.
2011-04-05 22:29:46,432 Thread-1 INFO      [atlassian.jira.startup.JiraStartupLogger]

      The workaround is described in the link above.

            Assignee:
            Unassigned
            Reporter:
            Jeremy Largman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: