February 26, 2025

The Cloudera Operational Database 1.49 version supports modifications to the entitlements and enhancements to the Cloudera Operational Database UI.

Configure Security-Enhanced Linux (SELinux) enforcement using the Cloudera Operational Database UI

Cloudera Operational Database UI supports configuring the SELinux enforcement while creating a new operational database.

In the Cloudera Operational Database UI, go to Create Database > Settings > Advanced > SELinux to configure the SELinux enforcement. You can configure the SELinux option as Permissive or Enforcing.

To use SELinux support, you must have the CDP_SECURITY_ENFORCING_SELINUX entitlement and the minimum runtime version of 7.2.18.700 or 7.3.1.100. Please contact Cloudera support if you do not have this entitlement.

For more information, see Setting SELinux Mode.

Cloudera Operational Database has removed the COD_USE_I8G_INSTANCE_TYPE entitlement

Cloudera Operational Database has removed the COD_USE_I8G_INSTANCE_TYPE entitlement because it is not needed anymore. The I8g instance types are now public, and you can use them while creating an AWS Graviton-based Cloudera Operational Database cluster.

For more information, see AWS Graviton instances in Cloudera Operational Database.

Storage type removal from the Cloudera Operational Database

The Cloudera Operational Database has removed the storage type Cloud Storage with Caching and Data Tiering. This type resembles cloud storage with time-based priority caching, where data within a specified time range gets a higher priority. In contrast, older data are likely to be evicted.

Now, you can use the Cloud Storage with Caching storage type to use the data tiering functionality.

You must have the COD_DATATIERING entitlement to use this functionality.

For more information, see HBase Time-based Data Tiering using Persistent BucketCache.