Behavioral Changes In Cloudera Runtime 7.2.18.500

You can review the changes in certain features or functionalities of components that have resulted in a change in behavior from the previously released version to this version of Cloudera Runtime 7.2.18.500.

Atlas

Summary:
The Exclude SubTypes and Exclude Sub-classifications filters were removed from the Table tab of entity details.
Previous behavior:
Previously, the Exclude SubTypes and Exclude Sub-classifications filters were available from the Table tab in entity details. There were no properties being passed to these filters when you visited the entity details of the page.
New behavior:
The two unused filter checkboxes Exclude SubTypes and Exclude Sub-classifications from the Table tab of entity detail page were removed.
Summary:
Special character validation was added to glossary, term and category names in Apache Atlas.
Previous behavior:
The special characters '@', '.', '<', '>' could be used in glossary, term and category name fields.
New behavior:
The special characters '@', '.', '<', '>' are no longer accepted in glossary, term and category name fields by the validation introduced. Avoid using these characters when creating glossary names, glossary terms and category names.

Ranger

Summary:
Hive authorization from Ranger for Alter Table Rename command does not require CREATE database permission on the database where the renamed table will be created.
Previous behavior:
In releases earlier than 7.2.18.500, whenever Alter Table Rename command was used across databases in Hive, authorization from Ranger required CREATE database permission for the user on the target database in which the renamed table was created.
New behavior:
In 7.2.18.500 and later releases, whenever Alter Table Rename command is used across databases in Hive, authorization from Ranger does not check for CREATE database permission for the user on the target database in which the renamed table will be created.
Summary:
Enhancement of perf-tracer to get CPU time when possible.
Previous behavior:
Earlier, PERF log prints total time spent by a thread in milliseconds.
New behavior:
This feature supports nanosecond precision when the JVM version supports it. Now, it will log elapsed cpu_time and user_time for each thread.