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

Qiang Zhang commented on RANGER-2257:
-------------------------------------

Review Requet:
https://reviews.apache.org/r/69080/

Solution patch, please see attachment:
[patch|https://issues.apache.org/jira/secure/attachment/12944656/0001-RANGER-2257-Add-policyID-to-error-message-when-click.patch]

Implementation details:
[Modified 
screenshots|https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png]

> Add policyID to error message when click the Access log of Audit
> ----------------------------------------------------------------
>
>                 Key: RANGER-2257
>                 URL: https://issues.apache.org/jira/browse/RANGER-2257
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>    Affects Versions: master
>            Reporter: Qiang Zhang
>            Assignee: Qiang Zhang
>            Priority: Minor
>              Labels: ErrorMessage, UI
>         Attachments: 
> 0001-RANGER-2257-Add-policyID-to-error-message-when-click.patch, 
> IDandTime.png, OnlyTime.png
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> Check the Access log of Audit in RangerAdmin,
> click on a log to see its corresponding policyID history,
> If the policyID does not exist, the following error will occur:
> No policy history found for given time: 2018-08-14T08:43:11Z
> Please check the following screenshots:
> https://issues.apache.org/jira/secure/attachment/12944645/OnlyTime.png
> The information given in the above error message does not give policyID 
> information, 
> which can lead to user confusion.
> Add policyID to modify the error message as follows:
> No policy history found for given policy ID: 1 and event time: 
> 2018-08-14T08:43:11Z
> Modified screenshots:
> https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to