[ 
https://issues.apache.org/jira/browse/RANGER-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241206#comment-17241206
 ] 

Ramesh Mani edited comment on RANGER-3094 at 12/1/20, 2:15 AM:
---------------------------------------------------------------

Before this patch, audit will show only the parent path when directory is 
created. 

!Screen Shot 2020-11-30 at 6.02.04 PM.png|width=1307,height=61!

After this patch directory information is also there in the resource field.

!Screen Shot 2020-11-30 at 6.09.52 PM.png|width=959,height=52!

Even when a file is copied/rename, file name was missing in the resource field 
and this fixes the issue.
 !Screen Shot 2020-11-30 at 6.08.49 PM.png|width=606,height=45!


was (Author: rmani):
Before this patch, audit will show only the parent path when directory is 
created. 

!Screen Shot 2020-11-30 at 6.02.04 PM.png|width=1307,height=61!

After this patch directory information is also there in the resource field.

!Screen Shot 2020-11-30 at 6.09.52 PM.png|width=959,height=52!

Even when a file is copied/rename, file name was missing in the resource field 
and this fixes the issue.
 !Screen Shot 2020-11-30 at 6.08.49 PM.png|width=1077,height=80!

> Ranger HDFS audit not capturing the correct path for write rename operations
> ----------------------------------------------------------------------------
>
>                 Key: RANGER-3094
>                 URL: https://issues.apache.org/jira/browse/RANGER-3094
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 2.2.0
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>            Priority: Major
>             Fix For: 2.2.0
>
>         Attachments: Screen Shot 2020-11-30 at 6.02.04 PM.png, Screen Shot 
> 2020-11-30 at 6.08.49 PM.png, Screen Shot 2020-11-30 at 6.09.52 PM.png
>
>
> Ranger HDFS audit not capturing the correct path for write rename operations



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to