Package com.atlassian.confluence.upgrade.upgradetask

Class SynchronyEvictionEventsPreSchemaUpgradeTask

java.lang.Object
com.atlassian.confluence.upgrade.AbstractUpgradeTask
com.atlassian.confluence.upgrade.upgradetask.SynchronyEvictionEventsPreSchemaUpgradeTask
All Implemented Interfaces:
BackupSupport, DatabaseUpgradeTask, UpgradeTask, UpgradeTaskInfo, org.springframework.beans.factory.Aware, org.springframework.beans.factory.BeanNameAware
public class SynchronyEvictionEventsPreSchemaUpgradeTask extends AbstractUpgradeTask implements DatabaseUpgradeTask
We drop synchrony tables and then recreate them from scratch instead of truncating because of the Hibernate bug that can't alter existing quoted tables.

https://hibernate.atlassian.net/browse/HHH-12106

Since:
7.0.0

  • Constructor Details

    • SynchronyEvictionEventsPreSchemaUpgradeTask

      public SynchronyEvictionEventsPreSchemaUpgradeTask(DdlExecutor ddlExecutor, com.atlassian.config.db.HibernateConfig config)

  • Method Details

    • runOnSpaceImport

      public boolean runOnSpaceImport()
      Description copied from interface: BackupSupport
      Returns true if an older Space can't be imported in a new instance without running this task. For example:
      • A task updating macro names in the BodyContent table would be blocking.
      • Tasks which updates data related to the space would be blocking.
      • A task upgrading the user table wouldn't be blocking.
      • Adding a mandatory column on space-related content breaks space import

      Note that tasks don't run on space import yet, so we just reject the import in this case.

      Specified by:
      runOnSpaceImport in interface BackupSupport

    • breaksBackwardCompatibility

      public boolean breaksBackwardCompatibility()
      Description copied from interface: BackupSupport
      Returns true if a new export can't be imported in an older instance.

      Breaking compatibility means a snapshot of the new version will not work at all with the previous version. For example:

      • A destructive operation (Some data is replaced by another) breaks backwards compatibility
      • Adding a optional column does NOT break backwards compatibility
      • Data is copied to another column doesn't breaks backwards compatibility
      • A build number incrementation doesn't breaks backwards compatibility
      The best way to test is whether a newer export can be imported (with fully working features) in an older instance.
      Specified by:
      breaksBackwardCompatibility in interface BackupSupport

    • getBuildNumber

      public String getBuildNumber()
      Specified by:
      getBuildNumber in interface UpgradeTaskInfo
      Overrides:
      getBuildNumber in class AbstractUpgradeTask
      Returns:
      The build number that this upgrade is applicable to

    • doUpgrade

      public void doUpgrade() throws Exception
      Description copied from interface: UpgradeTask
      Perform the upgrade.
      Specified by:
      doUpgrade in interface UpgradeTask
      Throws:
      Exception