You can review the changes in certain features or functionalities of Cloudera Manager that have resulted in a change in behavior from the previously
released version to this version of Cloudera Manager 7.13.1.
Cloudera Manager 7.13.1 CHF8 (7.13.1.800)
Cloudera Manager disables the login
"Remember Me" option by default
Previous behavior:
In previous versions, the Cloudera Manager login user interface (UI) displayed the
Remember Me checkbox by default. When users selected this
option during login, Cloudera Manager granted them an extended, persistent session
lasting up to two weeks. This allowed users to access the console without
re-authenticating, even after closing their browsers or experiencing standard session
timeouts.
New behavior:
To prevent unintended persistent sessions and improve security, Cloudera Manager now
hides the Remember Me checkbox by default. Consequently, users
no longer see this checkbox on the login screen, and the system enforces the standard
30-minute session timeout. Users must re-authenticate once their session expires.
To restore the checkbox to the login UI and allow the two-week persistent session,
administrators must manually enable the session_remember_me parameter
by navigating to Administration > Settings within the Cloudera Manager Server Configuration settings.
Summary: Default value of
hive.iceberg.allow.datafiles.in.table.location.only
synchronized to true.
Previous behavior:
Previously, the
hive.iceberg.allow.datafiles.in.table.location.only property was
set to true by default in the Cloudera Manager user interface, but the
HiveServer2 (HS2) instance displayed the value as false.
New behavior:
The hive.iceberg.allow.datafiles.in.table.location.only property
is now consistently set to true across both the Cloudera Manager user
interface and the HiveServer2 instances.
Summary: Default value of
hive.load.data.use.native.api changed to false.
Previous behavior:
Previously, the hive.load.data.use.native.api property was set to
true by default. When both this property and
hive.iceberg.allow.datafiles.in.table.location.only were enabled,
the LOAD query for Iceberg tables did not move data files into the
table directory.
New behavior:
The default value for the hive.load.data.use.native.api property
is now false. This change ensures that the LOAD query correctly moves
data files into the Iceberg table directory, maintaining data consistency and preventing
errors during selection.
Cloudera Manager 7.13.1 CHF7 (7.13.1.710)
There are no behavioral changes in this release.
Cloudera Manager 7.13.1 CHF6 (7.13.1.600)
There are no behavioral changes in this release.
Cloudera Manager 7.13.1 CHF5 (7.13.1.500)
Summary: Hive SYSDB creation failures
Previous behavior:
Any failure during the Create SYSDB command in Hive was treated as
a fatal error, which would stop the entire Cloudera
installation.
New behavior:
Now, Cloudera Manager treats failures during the creation of SYSDB
in Hive as non-fatal. This allows the Cloudera
installation to proceed even if the command fails. If users find that SYSDB does not
exist, they can still create or recreate it manually from the
Actions menu of the Hive Metastore Server role.
Cloudera Manager 7.13.1 CHF4 (7.13.1.400)
There are no behavioral changes in this release.
Cloudera Manager 7.13.1 CHF3 (7.13.1.300)
There are no behavioral changes in this release.
Cloudera Manager 7.13.1 CHF2 (7.13.1.200)
There are no behavioral changes in this release.
Cloudera Manager 7.13.1 CHF1 (7.13.1.100)
There are no behavioral changes in this release.
Cloudera Manager 7.13.1
Summary: Added ability in the Cloudera Manager Agent's config.ini file to
disable filesystem checks.
In Cloudera Manager Agent 7.13.1 and higher versions, a new
optional configuration flag is available. The new flag is
monitor_filesystems, which you can set up in the Cloudera Manager Agent config.ini file (found
in /etc/cloudera-scm-agent/config.ini).
You can add the following lines in the config.ini file before
upgrading Cloudera Manager Agent to disable monitoring of
filesystems:
The flag monitor_filesystems is used to determine if the
agent has to monitor the filesystems.
If the flag is set to True, Cloudera Manager Agent monitors the filesystems.
If the flag is set to False, Cloudera Manager Agent will not monitor any filesystems. If the
flag is not included in the file, it will default to
True, and Cloudera Manager Agent
behavior will match previous versions.
Summary: Added a new Cloudera Manager
configuration parameter spark_pyspark_executable_path to Livy for
Spark 3.
In Cloudera Manager Agent 7.13.1 and higher versions, a new Cloudera Manager configuration parameter
spark_pyspark_executable_path is added to Livy for Spark 3
service.
The value of spark_pyspark_executable_path for Livy must sync with
the value of the Spark 3 service's spark_pyspark_executable_path
parameter in Cloudera Manager.
Summary: The Livy proxy user is taken from Livy for Spark
3's configuration.
Previous behavior:
The custom Kerberos principal configuration was updated via the Livy service.
New behavior:
The Livy proxy user is taken from Livy for Spark 3's configuration, as the Livy
service has been replaced with Livy for Spark3 in Cloudera Base on premises and Cloudera on cloud version 7.3.1.
