August 30, 2023
Cloudera Operational Database 1.34 version supports different JDK versions during Cloudera Operational Database creation and deploying Cloudera Operational Database on GCS.
Cloudera Operational Database supports creating an operational database using JDK8 and JDK11
Cloudera Operational Database now added a new CLI option, –java-version which can be used to configure a major Java version on your Cloudera Operational Database cluster. The new CLI option can be used along with the create-database command to specify the Java version. The supported Java versions are JDK8 and JDK11. In case the parameter is not specified, JDK8 is used. Following is a sample command.
cdp opdb create-database --environment-name <environment_name> --database-name <database_name> --java-version <value>
cdp opdb create-database --environment-name cod7215 --database-name testenv --java-version 11
For more information, see CDP CLI beta.
Cloudera Operational Database is available as a Technical Preview feature on Google Cloud Storage (GCS)
Cloudera Operational Database on Google Cloud Platform (GCP) can now be deployed by using Google Cloud Storage (GCS)
easily, similar to what is available for Amazon Web Services (AWS) S3 storage and Microsoft
Azure blob storage. The use of GCS for such a setup requires the COD_ON_GCS
entitlement.
Cloudera Operational Database also now supports a large ephemeral block cache while deploying on GCP. The use of
ephemeral storage along with any cloud storage still requires the
OPDB_USE_EPHEMERAL_STORAGE
entitlement.
Cloudera Operational Database has removed the COD_ON_GCP
entitlement
COD_ON_GCP
entitlement has been removed from Cloudera Operational Database because it is not needed
anymore. From this version onwards, customers can create Cloudera Operational Database clusters on Google Cloud Platform
(GCP) without it.