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

Dongying Jiao edited comment on RANGER-1067 at 7/11/16 9:22 AM:
----------------------------------------------------------------

New patch according to Pradeep Agrawal's comments in review board.
Thanks a lot.


was (Author: dongying jiao):
New patch according to review comments.

> admin audit logging is not correct when add and delete the configuration from 
> the service repo.
> -----------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1067
>                 URL: https://issues.apache.org/jira/browse/RANGER-1067
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 0.5.2
>            Reporter: Dongying Jiao
>             Fix For: 0.6.0
>
>         Attachments: 
> 0001-RANGER-1067-admin-audit-logging-is-not-correct-when-.patch, 
> RANGER-1067.patch, addconfiguration.png, addconfiguration_afterpatch.png, 
> deleteconfiguration.png, deleteconfiguration_afterpatch.png
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Scenario:
> 1. Go to default hdfs repo config.
> 2. Add a configuration.
> 3. Check the admin audit log.
> 4. Then delete the configuration. 
> 5. Check the admin audit log.
> Error:
> When adding configuration, there are some fields that are not changed 
> recorded in the audit log. The old value and new value are all null.
> When deleting the configuration, the audit log is recorded not correctly.
> For example:I added only one configuration, name is "TestConfig", value is 
> "abc". In the audit log, "TestConfig" is correctly recorded, but several 
> other fields are also recorded, with old value and new value are all null. 
> Then delete it, abc is recorded as the value of other fields other than 
> "TestConfig" in audit log.
> Screenshot is attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to