[
https://issues.apache.org/jira/browse/RANGER-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Gupta updated RANGER-5212:
---------------------------------
Description:
In the {*}Ranger Admin UI and Auditor UI{*}, under *Users/Groups/Roles → Roles*
tab, the result table displays four columns:
* Role Name
* Users
* Groups
* Roles
The search bar currently offers filters for:
* Role Name
* User Name
* Group Name
*Issue:*
When using the *Role Name* filter, it only matches values from the *Role Name*
column. It does *not* match values from the *Roles* column, even though that
column contains the role for Role Admin and Role Auditor
*Example:*
Given the following role data:
||*Role Name*||*Users*||*Groups*||*Roles*||
|role_first|-|-|-|
|role_second|test|-|role_first|
If the user searches using the *Role Name* filter with the keyword
\{{role_first. }}The table does *not* show the role_second entry, even though
role_first is listed under its *Roles* column.
*Expected Behavior:*
The *Role Name* filter should match values from *both* the *Role Name* and
*Roles* columns. In the above case, searching for role_first should return:
* role_first (from Role Name)
* role_second (because role_first appears under its Roles column)
*Reference Behavior:*
In the Role {*}User{*}, searching by a role name is working correctly.
*Steps to Reproduce:*
1.Go to {*}Ranger Admin UI / Auditor UI -> Users/Groups/Roles -> Roles{*}.
2. Create two roles:
* role_first (no members)
* role_second with user test and assigned role role_first
3. Use the *Role Name* search filter with the value role_first
4. Observe that role_second is *not* returned, even though it references
role_first under the *Roles* column.
was:
In the {*}Ranger Admin UI{*}, under *Users/Groups/Roles → Roles* tab, the
result table displays four columns:
* Role Name
* Users
* Groups
* Roles
The search bar currently offers filters for:
* Role Name
* User Name
* Group Name
*Issue:*
When using the *Role Name* filter, it only matches values from the *Role Name*
column. It does *not* match values from the *Roles* column, even though that
column contains the role
*Example:*
Given the following role data:
||Role Name||Users||Groups||Roles||
|role_first|-|-|-|
|role_second|test|-|role_first|
If the user searches using the *Role Name* filter with the keyword
{{role_first. }}The table does *not* show the {{role_second}} entry, even
though {{role_first}} is listed under its *Roles* column.
*Expected Behavior:*
The *Role Name* filter should match values from *both* the *Role Name* and
*Roles* columns. In the above case, searching for {{role_first}} should return:
* {{role_first}} (from Role Name)
* {{role_second}} (because {{role_first}} appears under its Roles column)
*Reference Behavior:*
In the {*}User UI{*}, searching by a role name is working correctly.
*Steps to Reproduce:*
1.Go to {*}Ranger Admin UI -> Users/Groups/Roles -> Roles{*}.
2. Create two roles:
*
** {{role_first}} (no members)
*
** {{role_second}} with user {{test}} and assigned role {{role_first}}
3. Use the *Role Name* search filter with the value {{role_first}}
4. Observe that {{role_second}} is *not* returned, even though it references
{{role_first}} under the *Roles* column.
> Search filter in Roles tab does not consider all relevant role columns
> ----------------------------------------------------------------------
>
> Key: RANGER-5212
> URL: https://issues.apache.org/jira/browse/RANGER-5212
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Rakesh Gupta
> Assignee: Rakesh Gupta
> Priority: Major
> Attachments: RANGER-5212.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In the {*}Ranger Admin UI and Auditor UI{*}, under *Users/Groups/Roles →
> Roles* tab, the result table displays four columns:
> * Role Name
> * Users
> * Groups
> * Roles
> The search bar currently offers filters for:
> * Role Name
> * User Name
> * Group Name
> *Issue:*
> When using the *Role Name* filter, it only matches values from the *Role
> Name* column. It does *not* match values from the *Roles* column, even though
> that column contains the role for Role Admin and Role Auditor
> *Example:*
> Given the following role data:
>
> ||*Role Name*||*Users*||*Groups*||*Roles*||
> |role_first|-|-|-|
> |role_second|test|-|role_first|
>
> If the user searches using the *Role Name* filter with the keyword
> \{{role_first. }}The table does *not* show the role_second entry, even though
> role_first is listed under its *Roles* column.
> *Expected Behavior:*
> The *Role Name* filter should match values from *both* the *Role Name* and
> *Roles* columns. In the above case, searching for role_first should return:
> * role_first (from Role Name)
> * role_second (because role_first appears under its Roles column)
> *Reference Behavior:*
> In the Role {*}User{*}, searching by a role name is working correctly.
> *Steps to Reproduce:*
> 1.Go to {*}Ranger Admin UI / Auditor UI -> Users/Groups/Roles -> Roles{*}.
> 2. Create two roles:
> * role_first (no members)
> * role_second with user test and assigned role role_first
> 3. Use the *Role Name* search filter with the value role_first
> 4. Observe that role_second is *not* returned, even though it references
> role_first under the *Roles* column.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
