[ https://issues.apache.org/jira/browse/RANGER-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517858#comment-17517858 ]
Pradeep Agrawal commented on RANGER-3667: ----------------------------------------- Seems patch is committed : [https://github.com/apache/ranger/commit/d8fc10a36c9b23e807f8c8deaecec9bc0ae7ed05] If nothing is pending please close this and related RR https://reviews.apache.org/r/73903 > Improve feedback in policy creation UI when resource does not exist > ------------------------------------------------------------------- > > Key: RANGER-3667 > URL: https://issues.apache.org/jira/browse/RANGER-3667 > Project: Ranger > Issue Type: Improvement > Components: Ranger > Reporter: Dhaval Rajpara > Assignee: Dhaval Rajpara > Priority: Major > Attachments: 0001-RANGER-3667.patch, 0002-RANGER-3667.patch > > > 1. In Ranger's policy creation UI, when a resource (e.g. Hive database or > table name) is entered in the Policy Details, the autocomplete feature will > proactively present a dropdown of possible matches to known resource names > pulled from the service, which the user can then select to populate the > fields in the policy. > 2. If there is only one match to an existing resource name, then only that > single name will be presented in the dropdown. > 3. If there are no matches, then the text already entered into the field will > be presented in the autocomplete dropdown. This behavior is exactly the same > as (2) whether the resource exists or not. > 4. While there are some use cases where a policy may need to be created prior > to creating the actual resource itself, there is no validation or feedback in > the UI to indicate if a resource name already exists. In the case of a simple > typo error, this lack of feedback can result in the creation of invalid > policies that are then difficult to isolate and fix. > This request is to include some additional feedback ("not found" message or > similar) in the UI, to indicate when a resource does not exist. This would > also assist in identifying communication issues between Ranger and the > backend services. -- This message was sent by Atlassian Jira (v8.20.1#820001)