6.3.0 Yellowbrick Release Notes ​

Date: June 23, 2023

Yellowbrick Version 6.3.0 Release Notes ​

Yellowbrick Data Warehouse Version 6.3.0 is supported for AWS and Microsoft Azure cloud deployments. This version of Yellowbrick Data Warehouse is installed on Cloud Data Warehouse Manager (CDWM) Version 3.63.x.

Upgrade and Compatibility Requirements ​

Read the following information before beginning an upgrade to Version 6.3.0. Contact Customer Support to review the process and schedule the upgrade.

Upgrades from Version 6.2.x ​

Upgrades from 6.2.x to Version 6.3.0 are supported. These upgrades apply to both CDWM and data warehouse instances.

• AWS: Version 6.3.0 requires EKS Version 1.23. You must use the EKS migration tool to upgrade from EKS 1.22 to 1.23 before upgrading to Version 6.3.0. Also, you must upgrade from Version 6.2.0 to Version 6.2.1 first, then upgrade to 6.3.0.
  For each Yellowbrick upgrade, update the CloudFormation stack, then upgrade CDWM, then upgrade your data warehouse instances.
• Azure: You can upgrade directly from Version 6.2.0 or 6.2.1 to Version 6.3.0. Note that Version 6.3.0 requires AKS Version 1.24, but this version is supplied as part of the Yellowbrick upgrade.

Note: Before upgrading data warehouse instances, make sure they are running. You cannot upgrade a suspended instance.

Upgrades from Version 5.x (Not Supported) ​

You cannot upgrade from Version 5.x to Version 6.3.0. However, you can replicate databases from some older releases to Version 6.3.0; see BAR2 and Replication Compatibility.

ybtools Compatibility ​

Yellowbrick recommends that you always upgrade ybtools to match the Yellowbrick server version you are running (for example, upgrade to ybtools Version 6.3 before connecting to a Version 6.3 database). In most cases, using an older version of ybtools, such as 5.2 or 6.2, to connect to a Version 6.3 database will work but is not recommended.

Using Version 6.3 of ybtools with an older server version (such as Version 6.2 or 5.2) may result in error messages for some commands or a mismatch between client and server features.

The Version 5.2 and 5.4 ybtools packages install two sets of backup and restore tools: legacy tools (BAR1) and current versions of the tools (BAR2). The legacy tools are deprecated and have been removed from the 6.x releases.

BAR2 and Replication Compatibility ​

Important: The source and target systems used for database backup and restore (BAR2) and database replication must be compatible. To support full functionality, the source and target systems should both be running a 6.3 version of Yellowbrick software.

Nonetheless, you can back up and restore a database, or replicate a database, from:

• 5.2.x to 6.3.x
• 5.4.3 or later to 6.3.x
• 6.1.x to 6.3.x
• 6.2.x to 6.3.x
• 6.3.x to 6.3.x

Although you can start replication from a 5.2, 5.4, 6.1, or 6.2 source to a 6.3 target, and you can fail over to the 6.3 target, you cannot fail back to the 5.2, 5.4, 6.1, or 6.2 source. In general, you cannot fail back to a Yellowbrick version with a catalog version that is earlier than the current catalog version.

What's New in Version 6.3.0 ​

Version 6.3.0 provides the following new features, some bug fixes for critical issues reported by customers, and fixes for some CVEs. See Issues Fixed in Version 6.3.0.

Standard or Scaled Shared Services ​

Version 6.3 on AWS gives customers the flexibility to install Yellowbrick into a smaller cloud hardware footprint. The Standard Shared Services option creates fewer AWS node groups to run Yellowbrick software. The Scaled Shared Services option is intended for larger data warehouse environments that anticipate more than 100 active users and need more than 5TB of primary data storage.

This feature is supported on AWS only; it is not yet supported for Azure deployments.

Proxy Support for Azure Deployments ​

During Yellowbrick deployment on Azure, you can set options to route AKS-required network traffic through HTTP/HTTPS proxies.

Changes in Behavior ​

Default Time Zone for Data Warehouse Instances ​

In Version 6.3.0, the timezone and log_timezone configuration settings default to UTC for all new data warehouse instances.

Behavior of the CHAR Data Type ​

The CHAR data type implementation has changed in Version 6.x. The pg_char_compatibility_mode parameter is now set to FULL and cannot be set to any other value. See Upcoming Behavioral Changes to the CHAR Data Type.

Default Behavior of WLM Restart Rules ​

By default, a subset of recoverable error codes triggers an attempted restart, and an attempted restart occurs only once per query. For details, see "Restarting Queries" in the Version 6.3 documentation.

ybtools Clients on Ubuntu ​

Version 6.3.0 supports ybtools on Ubuntu 16.04 LTS, 18.04 LTS, and 20.04 LTS.

Fixed Issues in Version 6.3.0 ​

The following issues are fixed in Version 6.3.0.

Parent topic:Change History