Review the list of Atlas issues that are resolved in Cloudera Runtime
7.3.1, its service packs and cumulative hotfixes.
Cloudera Runtime 7.3.1.400 SP2
- CDPD-82054: UI: when server response date fields as '0', UI
shows as current time
- 7.3.1.400
- Previously, if an API response contained an invalid date
value (such as 0) intended for display on the user interface, the current
system date was shown. Currently, instead of displaying the system date when an invalid
date value is encountered in the API response, the user interface displays
NA. This issue specifically affects the Entity
Detail page, where the create time and modified time are displayed.
- Apache JIRA:
ATLAS-5015
- CDPD-34895: Investigate which HTTP security headers Atlas should
have in API responses
- 7.3.1.400
- A static header and a custom header is provided which can
be added through atlas-application.properties file. This enables
adding custom security headers.
- Use the following prefix keyword to customize the header:
In
atlas-application.properties instead of using the prefix
atlas.rest.headers use
atlas.header.
Example:
- atlas.headers.content-security-policy=default-src 'self' // content-security-policy
- CDPD-74374: Patch to replace the long strings set in
spark_process attributes
- 7.3.1.400
- As the
atlas.process.spark.attributes.update.patch is set to
TRUE by default, the spark_process entity attributes
details and sparkPlanDescription no longer cause
out-of-memory issues as they are no longer contain a large amount of data.
Cloudera Runtime 7.3.1.300 SP1 CHF 1
- CDPD-80922: Without a permission for one glossary, the /glossary
call throws exception and it does not list the remaining glossaries
- 7.3.1.300
-
The getGlossaries method in GlossaryService is
updated to ensure that the full paginated list is retrieved, even if some glossaries
are skipped. This method includes the following improvements:
-
Handling skipped glossaries: If some entities fail to load, it fetches additional
entities until the requested limit is met.
-
Efficient pagination: Keeps fetching until it gets the required number of valid
glossaries.
-
Preventing infinite loops: method stops when either the required number of
glossaries is retrieved or there are no more to fetch.
- CDPD-70450: Impala SQL queries that include the WITH clause
should populate lineage in Atlas
- 7.3.1.300
- Previously, only Impala SQL queries that don't use the
"WITH" clause could be shown with their lineage in Atlas, but queries that do use the
"WITH" clause could not be shown with lineage in Atlas.
Currently. Impala SQL queries
using the "WITH" clause are supported.
- CDPD-80160: Use the centralized commons-lang3
- 7.3.1.300
- A centralized commons-lang3 package is used to prevent
build issues and a security vulnerability.
Cloudera Runtime 7.3.1.200 SP1
- CDPD-76789: Creating tag with name description throws
java.lang.ClassCastException
- 7.3.1.200
- A validation is added to avoid creating classification
with reserved names such as "name", "description", "owner", "version", "serviceType" and
"options".
- Apache Jira:
ATLAS-4956
- CDPD-77435: RAZ: Import-hive on Cloudera Data Engineering cluster fails
- 7.3.1.200
- Running an Import-hive action on a RAZ-enabled Cloudera Data Engineering cluster no longer fails with the error
NoClassDefFoundError:
com/sun/jersey/core/spi/factory/ResponseBuilderImpl.
- CDPD-65806: Not all Iceberg table relationships are visible
after upgrade from Cloudera Public Cloud 7.2.17 to Cloudera Public Cloud 7.2.18
- 7.3.1.200
- Iceberg table relationships like Iceberg table DB, Iceberg table
SD, Iceberg DDL queries were added for Iceberg table entity. Old relationships such as
Hive table DB, Hive table SD, Hive DDL queries were removed.
Cloudera Runtime 7.3.1.100 CHF 1
- CDPD-77767: Migration status is not updated on file while
migration is in progress
- 7.3.1.100
- Previously, whenever a migration was started on any
environment and tried to update the vertex with details, the status update would fail
with a null pointer exception. This issue is fixed by using the file hash code instead
of file name causing the null pointer exception. Now, whenever a migration restarts, it
starts from last point where it was stopped or interrupted.
- Apache Jira:
ATLAS-4907
- CDPD-69910: Nullpointer exception while deleting business
metadata
- 7.3.1.100
- The migration status is stored correctly and reused to
restart migration from the point where it failed earlier.
- Apache Jira:
ATLAS-4863
- CDPD-74140: Comment for existing Hive tables can not be modified
in Atlas
- 7.3.1.100
- The comment attribute is now updated and existing
comments can be modified and the changes are reflected in the Apache Atlas UI.
- CDPD-76536: Iceberg entities created in 7.2.17 Atlas-Hook (Hive,
Impala, Spark) are not ingested by 7.2.18/7.3.1 Atlas Server
- 7.3.1.100
- The incompatibility issue between Cloudera Data Services
for CDP Public Cloud 7.2.17 Apache Hive and Apache Impala hooks with Atlas server for
CDP Public Cloud 7.2.18 and Cloudera on cloud 7.3.1 is
resolved. With this fix, Iceberg tables created in Cloudera Public Cloud 7.2.17 or older
are captured properly in Apache Atlas UI for Cloudera Public Cloud 7.2.18 and Cloudera on cloud 7.3.1.
- CDPD-65619: Iceberg tables do not show under hive_db entity when
created
- 7.3.1.100
- The UI now displays Iceberg tables if they are created
under the same Hive database (
hive_db). Iceberg table can been seen in
the Tables tab of a Hive database (hive_db) in
basic search. Both Hive table (hive_table) and Iceberg table
(iceberg_table) typenames are visible.
- CDPD-71411: Atlas Hbase import fails with jackson-databind
expection
- 7.3.1.100
- The
jackson-annotations is updated to
match jackson-databind (2.15.0) to resolve the
NoSuchFieldError error during an HBase import caused by version
mismatch (older 2.12.7 on classpath).
Cloudera Runtime 7.3.1
- CDPD-69962: fetchType as "incremental" does full export instead
of "CONNECTED"
- 7.3.1
-
Earlier, the first incremental export operation performed on a target entity used to
fetch all entities even if they were not related to the targeted entity. This affected
the performance as it imports more data than what was expected.
Now, the first incremental export will only fetch the entities which are related to
the target entity. Also, if the target entity is connected to a lineage, then only the
immediately connected entities in the lineage will get exported and not the whole
lineage.
- CDPD-67654: [Atlas] [navigator2atlas] Status of deleted table is
ACTIVE in Atlas after navigator2atlas migration
- 7.3.1
- Deleted hive tables migrated via the Navigator to Atlas transition may shown as active
in Apache Atlas. Changes done in the Nav2Atlas module to set the
relationType as hive_table_storagedesc of
relationship attribute table for every entity of
hive_storagedesc.
- CDPD-72732: [UCL] Incorrect Atlas audits generated for updates
with atlas.hook.hive.skip.dml.messages set to true/false in 7.3.0.1 Cloudera Base on premises
- 7.3.1
- The Apache Atlas property
atlas.hook.hive.skip.dml.messages = true can be used to reduce the
number of audits that are generated for any DML command executed over a hive entity.
The default value for hive.split.update is set to
true in 7.3.1 causing two audits to be generated for one update
command: one delete and one insert. This will impact Apache Atlas when
atlas.hook.hive.skip.dml.messages = false (Atlas is processing Data
Manipulation events) and atlas.entity.audit.differential = false
(Atlas logs the full entity metadata during every update).
- CDPD-71516: Temporarily disable the tasks tab on Entity Detail
page
- 7.3.1
- The Entity Detail page was showing "Something went
wrong". This is occurring because on loading the Entity Detail page, an API call
(/api/atlas/admin/tasks) is made to get all the tasks that are
created when deferred actions features are enabled. The Entity Detail page task tab and
task API will display in UI depending upon the server side property
atlas.tasks.ui.tab.enabled. Initially, this is set to
false. Therefore, temporarily the task tab on entity detail page in
UI is disabled.Apache Jira:
ATLAS-4880
- OPSAPS-64385: Atlas's client.auth.enabled configuration is not
configurable
- In customer environments where user certifications are
required to authenticate to services, the Apache Atlas web UI will constantly prompt for
certifications. To solve this, the
client.auth.enabled parameter is set
to true by default. If it is needed to set it false,
then you need to override the setting from safety-valve with a configuration snippet.
Once it set to false, then no more certificate prompts will be
displayed.
- CDPD-53176: Partition Specification data for Iceberg Table is
not sent to Atlas in Hook context
- When an Iceberg table is created with partition spec,
partition specification data is sent to Apache Atlas in Hook context. In case of Hive,
Atlas is also getting the Partition Transform Information or Table
parameters.default-partition-spec from Hook context. When using the
Hive compute engine for partition evolution, the lineage is captured by Atlas.
- OPSAPS-68461: Update GC and JVM options for Atlas service for
supporting JDK17 in main Atlas CSD
- The issue of existing ATLAS OPTS not working for JDK17 is
fixed.
