Fixed Issues in Atlas
Review the list of Atlas issues that are resolved in Cloudera Runtime 7.3.1.
- CDPD-69962: fetchType as "incremental" does full export instead of "CONNECTED"
-
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
- 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
ashive_table_storagedesc
of relationship attributetable
for evey entity ofhive_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 CDP Private Cloud Base
- 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 totrue
in 7.3.1 causing two audits to be generated for one update command: one delete and one insert. This will impact Apache Atlas whenatlas.hook.hive.skip.dml.messages = false
(Atlas is processing Data Manipulation events) andatlas.entity.audit.differential = false
(Atlas logs the full entity metadata during every update). - CDPD-71516: Temporarily disable the tasks tab on Entity Detail page
- 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 tofalse
. Therefore, temporarily the task tab on entity detail page in UI is disabled.Apache Jira:ATLAS-4880
- OPSAPS-71089: 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 totrue
by default. If it is needed to set itfalse
, then you need to override the setting from safety-valve with a configuration snippet. Once it set tofalse
, then no more certificate prompts will be displayed. - 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.