When Upgrading from previous versions of RED, the RED metadata, Azkaban metadata or both may need upgrading. For RED the requirement to upgrade is enforced at login when there is an application version mismatch, but it is best practice to validate and upgrade the metadata after every RED application upgrade. Refer to the Upgrading WhereScape RED section of the RED User Guide for more details.

If there are important updates to the Azkaban metadata these will be indicated in the important upgrade messages that follow. Refer to the Upgrading Azkaban section of the RED User Guide for more details.

Important Messages when upgrading to 10.1.0.2

Upgrading RED

Version 10.1.0.0 has potentially breaking changes for upgraded repositories; therefore, upgrades should be tested thoroughly before upgrading production environments. The potential issues after the upgrade are the following:

  • Default Routine Template settings might be lost. For object types other than Load and Export these settings have been moved from target connections to the Object Subtypes. During the metadata upgrade process, the first target-enabled connection found is used to populate the new settings under Object Subtypes. If you have multiple target-enabled connections in your repository, the optimal connection may not be used for the settings transfer. Ensure to check the Object Subtypes maintenance wizard after an upgrade to this version and set any missing/incorrect default routine templates as required. Note: this configuration can be exported from test to production once resolved in test.
  • [TABLEOWNER] an $OBJECT$ token expansion no longer expands empty schemas to an additional ‘.’ in table names. This means from this release onwards you must specify the actual schema name in target location settings when schema is required on your platform. Ensure to check your target location settings for target connections before upgrading and populate the schema field, if required.

Upgrading Azkaban

This version 10.1.0.1 has changes to the Azkaban components; therefore, all Azkaban Web Servers and Executor Servers need upgrading as well as the Azkaban metadata.

Upgrading Azkaban is currently a manual process, please refer to the RED User guide for detailed upgrade instructions.

Change history for Azkaban components requiring upgrades (changes are cumulative):

  • 10.1.0.1: Log4j components upgraded to log4j2 to resolve logging issues.
  • 10.1.0.0: Improvements when canceling running jobs. Component upgrades.
  • 10.0.1.0: Added procedure support and long host names fix
  • 10.0.0.0: First release

Upgrading Scheduler Integration Scripts

The default scheduler integration publish script has improved and can optionally be upgraded in RED. Refer to the RED user guide for detailed upgrade instructions.

Change history for wsl_scheduler_publish script requiring optional manual upgrade (changes are cumulative):

  • 10.0.0.3: Support for republishing when existing job not found. Improved logging.
  • 10.0.0.2: Added support for disabled tasks.
  • 10.0.0.0: First release 
  • No labels