What's new in Cloudera Data Warehouse Private Cloud
Review the new features in this release of Cloudera Data Warehouse Private Cloud service.
Hue supports natural language query processing (Preview)
- To learn more about the supported models and services, limitations, and what data is shared with the LLMs, see About the SQL AI Assistant in Cloudera Data Warehouse.
- To set up and enable the SQL AI Assistant, see About setting up the SQL AI Assistant in Cloudera Data Warehouse.
- To see how to generate, edit, explain, optimize, and fix queries, see Starting the SQL AI Assistant in Hue.
Improvements to custom pod configuration (now known as Resource Templates)
Resource Templates.
- A new menu option Resource Templates has been added to the left navigation pane on the Cloudera Data Warehouse web interface.
- You can now configure the allocation of Kubernetes resources to the pods for Hive, Data Visualization, and Database Catalog in addition to Impala.
- The Impala pod configuration feature is moved from the Environment Details page to the Resource Templates page.
Flexibility to enable and disable quota management for Cloudera Data Warehouse entities
Earlier, you were required to enable the quota management option before activating an environment to use quota-managed resource pools for environments, Data Catalogs, Virtual Warehouses, and Cloudera Data Visualization instances in Cloudera Data Warehouse. Starting with Cloudera Private Cloud Data Services 1.5.4, you can enable or disable the quota management option at any time during the lifecycle of the Cloudera Data Warehouse entities. To learn more about the behavioral aspects, see Quota Management in Cloudera Data Warehouse Private Cloud.
A new option called --resource-pool
(string) has been added to the CDP CLI
commands for Cloudera Data Warehouse
Private Cloud using which you can specify the resource pool for
the Cloudera Data Warehouse entity (Virtual Warehouse, cluster/environment, Cloudera Data Visualization instance).
Added support for authentication between Cloudera Data Warehouse and HMS database using mTLS
Cloudera Data Warehouse and the Hive MetaStore (HMS) database on the base cluster can mutually authenticate each other during the SSL/TLS handshake using mTLS for all supported backend databases (Oracle, MySQL, MariaDB, and Postgres). To set up mTLS, you must upload the database client certificate and the private key files in PEM format while activating an environment in Cloudera Data Warehouse. See Enabling mTLS between the HMS database and Cloudera Data Warehouse Private Cloud.
Ability to enable active-passive configuration for HiveServer2 pods
Cloudera Data Warehouse provides an option to enable active-passive configuration for HiveServer2 (HS2) pods in Private Cloud. By enabling this feature, two HS2 pods run simultaneously–one active and the other inactive. When one pod terminates, the inactive pod becomes active, providing High Availability. See HiveServer2 High Availability in Cloudera Data Warehouse Private Cloud. The most likely cause of a pod's termination is node failure.
Improvements to backup and restore Cloudera Data Warehouse
- Using Data Recovery Service (DRS)
- Using the Cloudera Data Warehouse’s Cloudera CLI cluster management commands
Both these methods use Cloudera CLI commands. The Cloudera Management Console also provides a graphical user interface to perform backup and restore operations. See DRS automatic backups and Using DRS with Cloudera Data Warehouse.
To learn about the different backup and restore methods, objects and configurations that are included in the backup, deciding which method to use, see Backup and restore in Cloudera Data Warehouse Private Cloud.
New advanced configuration option to backup Virtual Warehouse namespaces before an upgrade
By default, Cloudera Data Warehouse backs up namespace-related data before starting the upgrade process using the Data Recovery Service. A new option has been added to disable the automatic backup process on the Advanced Configuration page in the Cloudera Data Warehouse web interface.
Cloudera Data Warehouse no longer has a dependency on YARN
Environment activation in Cloudera Data Warehouse no longer depends on or fails if the YARN service is not installed on the Cloudera Private Cloud Base cluster.