suja s created RANGER-4523:
------------------------------
Summary: Suggestion on improving logs from AtlasNotificationMapper
Key: RANGER-4523
URL: https://issues.apache.org/jira/browse/RANGER-4523
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: suja s
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
{noformat}
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}]
{noformat}
Suggestion:
The logs related to dropping of notifications for hive_process can be logged as
DEBUG/INFO rather than WARN
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
