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.1.9 SP1 CHF 3.
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.
- Summary:
- Recursive tag based access control for Ozone keys, Apache Ranger Tagsync OFS support is
introduced.
- Previous behavior:
- Ozone keys were not recursively checked for tag based policies. Tag based policy was only
applicable for the directory level the tag is applied to. Additionally, Ranger Tagsync did not
support OFS paths, thus tag-based policies did not work for OFS paths previously.
- New behavior:
-
Ozone keys will now be recursively checked for tags and tag based policies. This means that
tags applied for parent directory will be applicable to subdirectories too. While this is an
expected behavior, this may cause behavior change in access control for customers already
using tag based policies for Ozone keys.
The behavior change will be for new keys tagged in Atlas after upgrading.
Tag based policies will now work for OFS entities too.
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.1.9 SP1 CHF3, 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.1.9 SP1 CHF3 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.
