Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-2338

Cloud import fails when digest or network attributes in the Notifications table are exported as null.

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      Cloud import fails when the digest or network columns in the Confluence NOTIFICATIONS table are exported with null values. These attributes are mapped to primitive boolean fields in Cloud, which cannot accept nulls, causing a Hibernate error during import.

      Steps to Reproduce

      1. In a Confluence Server/DC instance, locate rows in the NOTIFICATIONS table where digest or network is null.
      1. Run a server-to-cloud migration using CCMA.
      1. Observe the Cloud import logs.

      Expected Results

      The rows from the NOTIFICATIONS table are exported and imported into the Cloud environment without error, regardless of null values in digest or network.

      Actual Results

      Cloud import fails with the following error:
      org.springframework.orm.hibernate5.HibernateSystemException:
      Null value was assigned to a property of primitive type setter
      of com.atlassian.confluence.mail.notification.Notification.digest;
      nested exception is org.hibernate.PropertyAccessException:
      Null value was assigned to a property of primitive type setter
      of com.atlassian.confluence.mail.notification.Notification.digest
       

      Workaround

      Manually update the source database prior to export to ensure digest and network are never null:
      UPDATE NOTIFICATIONS SET network = false WHERE network IS NULL;
      UPDATE NOTIFICATIONS SET digest = false WHERE digest IS NULL;
       
       

              d585ec0afd35 David Bertrand
              76c30476c174 Daniel Tavares
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: