Advanced configurations in Cloudera Data Warehouse on premises
You can access advanced configurations in Cloudera Data Warehouse on premises from the left navigation pane on the Cloudera Data Warehouse web interface. Some of these configurations must be enabled before you activate an environment and some can be applied by refreshing the environment, Database Catalog, and Virtual Warehouses.
| Configuration | Description | Enabled by default? | Condition for applying the configuration |
|---|---|---|---|
| Use dedicated executor nodes | Allows you to schedule executors only to certain nodes. To select a node, you need to label it with cdw.cloudera.com/dedicated-executor-host | No | Enable to schedule Hive and Impala executor and coordinator pods only on labeled worker nodes. |
| Use deterministic namespace names | Makes the namespace names deterministic, that is, given the same input, a client can get to the same name every time. Enable this option if you need to create Kerberos principals and keytabs. | Yes | Enable before activating an environment in Cloudera Data Warehouse. |
| Enable ADLS as a storage provider | Enables you to use Azure Data Lake Storage (Gen1 and Gen2) for storing tables. | Yes | Refresh |
| Copy configurations from base cluster to Cloudera Data Warehouse | Configurations such as default file format, compression type, and transactional type are copied from the base cluster to Cloudera Data Warehouse to aid cluster setup and workload migration. | Yes | Refresh* |
| Enable customization of Kerberos service principal | Allows you to specify a custom hostname when activating the Cloudera Data Warehouse environment, which will be used in the hostname component of Kerberos service principal used by Cloudera Data Warehouse Runtime. | No | Establish the custom Kerberos service principal before activating the environment. |
| Back up Virtual Warehouse namespaces before an upgrade | Cloudera Data Warehouse backs up namespace-related data using the Data Recovery Service before upgrading the Virtual Warehouse. | Yes | Refresh* |
| Store logs on HDFS | Enables you to store Cloudera Data Warehouse logs to HDFS on the base cluster. | Yes | Refresh* |
| Enable Observability | Enables you to monitor and analyze the performance of your Cloudera Data Warehouse environment. | No | You must enable Telemetry Publisher and add the Altus Credentials on the Cloudera Base on premises cluster. For more information, see Enabling the telemetry network communication for Cloudera Observability. |
| Enable S3 and S3-compatible object store providers | Enables you to use AWS S3 and other similar, compatible, on-premises object stores that support the S3 protocol for storing tables. | Yes | Refresh* |
| Disable automatic overwrite of configurations on update | Allows you to prevent the copying of HDFS, Ozone, Databus Producer, and Third Party Object Store configurations from Cloudera Base on premises. By default, if there is a change in the Cloudera Base configuration values, the changes are copied to Cloudera Data Warehouse and the previous values are overwritten. If this setting is selected and if any of the above configurations are already present in Cloudera Data Warehouse, new configuration values from Cloudera Base are not copied over. You have to manually update the values in the Database Catalog or Virtual Warehouse. | No | Refresh* |
| Skip cluster validation during environment activation | Skips the cluster validation? step during environment activation. Select this option if you want to proceed with the environment activation even after seeing false positive errors in the logs. | No | Enable before activating an environment in Cloudera Data Warehouse. |
