Upgrading Database Catalogs and Virtual Warehouses in Cloudera Data Warehouse Private Cloud

What gets upgraded

Database Catalog in Cloudera Data Warehouse uses a Hive MetaStore (HMS) instance. The Virtual Warehouses use Apache Hive, Apache Impala, and Hue runtime images that are used in Cloudera Data Warehouse. These runtime images are different than those used on Cloudera Private Cloud. With every new Cloudera Private Cloud Data Services release, you get a new version of Apache Hive, Apache Impala, and Hue runtimes with Cloudera Data Warehouse, which includes new features and fixes.

Supported upgrade path for an in-place upgrade

In-place upgrade option is available only for upgrades from Cloudera Private Cloud Data Services 1.5.1 to a newer release.

What you should know before you upgrade

Review the Release Notes to learn about the new features, fixes, and known issues in this release, and more importantly, the upgrade-related known issues.

In-place upgrade steps

To verify a successful upgrade, check the version information on the Database Catalog or Virtual Warehouse details page by clicking > Edit on the Database Catalog or Virtual Warehouse tile.

What changes after the upgrade

• The ability to create custom Database Catalogs has been removed. After you upgrade to Cloudera Private Cloud Data Services 1.5.4, you can no longer create new custom Database Catalogs. The existing custom Database Catalogs remain until you deactivate the environment. You can continue to upgrade, refresh, and rebuild the existing Database Catalogs.
• Custom pod configurations that you have created before upgrading from the Cloudera Private Cloud Data Services 1.5.3 release to a newer release are migrated to the new resource templates as read-only settings after the upgrade. You can view the pod configurations from the Resource Templates page. You can use these as is while creating a Virtual Warehouse or modify them by creating a copy.
• The Keep current image version option has been removed from the Cloudera Data Warehouse web interface. When you rebuild the Database Catalog or Virtual Warehouse, they always retain the image version.
• In existing Data Visualization connections, you must rename the proxy user (delegation user) to "impala" user. You can rename it manually or refresh, upgrade, or rebuild the Virtual Warehouse or the Data Visualization instance after upgrading to Cloudera Private Cloud Data Services 1.5.4.
• If you had enabled the setting to copy the base cluster configurations to Cloudera Data Warehouse on the Cloudera Private Cloud Data Services 1.5.1 cluster, then the base cluster configurations will continue to get copied to Cloudera Data Warehouse after the upgrade. However, you can disable this setting from the Advanced Settings page.
• Starting with Cloudera Private Cloud Data Services 1.5.1, Data Analytics Studio (DAS) has been deprecated and completely removed from Cloudera Data Warehouse. After you upgrade the platform, any running DAS instances will be removed from the cluster. Cloudera recommends that you use Hue for querying and exploring data in Cloudera Data Warehouse.
• Starting with Cloudera Private Cloud Data Services 1.5.0, Hue in Cloudera Data Warehouse requires WebHDFS to be enabled on the Cloudera Private Cloud Base cluster. Ensure that worker nodes for both, OpenShift Container Platform (OCP) and Embedded Container Service (ECS), have access to the WebHDFS (HTTPFS) port 14000.