[RANGER-4523] Suggestion on improving logs from AtlasNotificationMapper

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Ranger
• Assignee: Unassigned
• Reporter: suja s
• Created: 10/Nov/23 04:34
• Updated: 10/Nov/23 04:34

Description

STEPS TO REPRODUCE:
Create hive db/table so that hive entities are created on atlas side
Create classifications
Create a tag policy and verify tag policy enforcement
Inspect tagsync logs

CURRENT BEHAVIOUR:
Since hive_process entity-type notifications are not handled by tagsync, there is a WARN message indicating this.
There are lot of log messages related to this

2023-10-09 08:14:02,300 WARN  org.apache.ranger.tagsync.source.atlas.AtlasNotificationMapper: [Thread-19]: Tag-sync is not enabled to handle notifications for Entity-type:[hive_process]
2023-10-09 08:14:02,300 WARN  org.apache.ranger.tagsync.source.atlas.AtlasNotificationMapper: [Thread-19]: Dropped process entity notification for Atlas-Entity [{typeName=hive_process, guid=41cffa4b-be0e-42ca-aa16-688e1b00526e, attributes={ name=qualifiedName, value=rgrtestdb.rgrtblctas@cm:1696835704000 name=clusterName, value=cm name=name, value=rgrtestdb.rgrtblctas@cm:1696835704000}]

Suggestion:
The logs related to dropping of notifications for hive_process can be logged as DEBUG/INFO rather than WARN