[jira] [Assigned] (RANGER-4224) Ranger Doc Site : Remove the reference to external sites ...
[
https://issues.apache.org/jira/browse/RANGER-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stalin Nadar reassigned RANGER-4224:
Assignee: Stalin Nadar
> Ranger Doc Site : Remove the reference to external sites ...
> -
>
> Key: RANGER-4224
> URL: https://issues.apache.org/jira/browse/RANGER-4224
> Project: Ranger
> Issue Type: Bug
> Components: documentation
>Reporter: Selvamohan Neethiraj
>Assignee: Stalin Nadar
>Priority: Major
>
> Please check the site - [https://whimsy.apache.org/site/check/resources] for
> errors in the Ranger doc site
> ([https://ranger.apache.org).|https://ranger.apache.org%29./]
> Apparently, it has reference to
> |[Ranger|https://whimsy.apache.org/site/project/ranger]|Found 7 external
> resources: \{"netdna.bootstrapcdn.com"=>3, "yandex.st"=>2,
> "ajax.googleapis.com"=>1, "fonts.googleapis.com"=>1}|
> !image-2023-05-04-17-35-53-417.png!
> Please fix this asap to be compliant with Apache Guidelines ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725988#comment-17725988 ] Madhan Neethiraj commented on RANGER-4251: -- [~duongnguyen] - have you considered setting up audit-filters (introduced in RANGER-3000) for Ozone service? This can be specified via service-config UI. Here is the screenshot for audit-filter for a Hive service, which skips auditing of METADATA_OPERATION and SHOW_ROLES operations. Hope this helps. !image-2023-05-24-15-14-33-403.png|width=1323,height=342! > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: image-2023-05-24-15-14-33-403.png, > ozone-load-test-flamegraph.html, ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=887,height=265! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-4251: - Attachment: image-2023-05-24-15-14-33-403.png > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: image-2023-05-24-15-14-33-403.png, > ozone-load-test-flamegraph.html, ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=887,height=265! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong updated RANGER-4251: -- Attachment: ozone-load-test-flamegraph.html > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: ozone-load-test-flamegraph.html, > ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=887,height=265! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong updated RANGER-4251: -- Attachment: ozone-ranger-flamegraph.png > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=1128,height=337! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong updated RANGER-4251: -- Attachment: (was: ozone-ranger-flamegraph.png) > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=1128,height=337! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong updated RANGER-4251: -- Description: The Ranger plugin for Ozone was implemented as per RANGER-2325. When running performance testing on Ozone, we notice that the Ranger plugin contributes significantly to Ozone latency and it gets worse when Ozone is under heavy load, i.e. 100K OPPS. !ozone-ranger-flamegraph.png|width=887,height=265! This ticket tracks the effort to improve the performance of the Ranger plugin for Ozone. Source of inefficiencies identified so far: # Ranger is logging/auditing all the requests, including reads that are accepted. This is too expensive and will be addressed by RANGER-4252. was: The Ranger plugin for Ozone was implemented as per RANGER-2325. When running performance testing on Ozone, we notice that the Ranger plugin contributes significantly to Ozone latency and it gets worse when Ozone is under heavy load, i.e. 100K OPPS. !ozone-ranger-flamegraph.png|width=542,height=162! This ticket tracks the effort to improve the performance of the Ranger plugin for Ozone. Source of inefficiencies identified so far: # Ranger is logging/auditing all the requests, including reads that are accepted. This is too expensive and will be addressed by RANGER-4252. > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: ozone-load-test-flamegraph.html, > ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=887,height=265! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4251) Performance improvement for Ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong updated RANGER-4251: -- Description: The Ranger plugin for Ozone was implemented as per RANGER-2325. When running performance testing on Ozone, we notice that the Ranger plugin contributes significantly to Ozone latency and it gets worse when Ozone is under heavy load, i.e. 100K OPPS. !ozone-ranger-flamegraph.png|width=542,height=162! This ticket tracks the effort to improve the performance of the Ranger plugin for Ozone. Source of inefficiencies identified so far: # Ranger is logging/auditing all the requests, including reads that are accepted. This is too expensive and will be addressed by RANGER-4252. was: The Ranger plugin for Ozone was implemented as per RANGER-2325. When running performance testing on Ozone, we notice that the Ranger plugin contributes significantly to Ozone latency and it gets worse when Ozone is under heavy load, i.e. 100K OPPS. !ozone-ranger-flamegraph.png|width=1128,height=337! This ticket tracks the effort to improve the performance of the Ranger plugin for Ozone. Source of inefficiencies identified so far: # Ranger is logging/auditing all the requests, including reads that are accepted. This is too expensive and will be addressed by RANGER-4252. > Performance improvement for Ozone plugin > > > Key: RANGER-4251 > URL: https://issues.apache.org/jira/browse/RANGER-4251 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Duong >Priority: Major > Attachments: ozone-ranger-flamegraph.png > > > The Ranger plugin for Ozone was implemented as per RANGER-2325. > When running performance testing on Ozone, we notice that the Ranger plugin > contributes significantly to Ozone latency and it gets worse when Ozone is > under heavy load, i.e. 100K OPPS. > !ozone-ranger-flamegraph.png|width=542,height=162! > This ticket tracks the effort to improve the performance of the Ranger plugin > for Ozone. > Source of inefficiencies identified so far: > # Ranger is logging/auditing all the requests, including reads that are > accepted. This is too expensive and will be addressed by RANGER-4252. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4165) Support SELF_OR_PREFIX resource matching scope in Ranger Authorization
[ https://issues.apache.org/jira/browse/RANGER-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated RANGER-4165: Description: Support SELF_OR_PREFIX resource matching scope in Ranger Authorization * introduced resource-element matching scope SELF_OR_PREFIX, which can be used to ask Ranger policy engine the following -- check if a user/group/role has read access in any path/file under directory /dept/hr/ -- check if a user/group/role has select access to any table having name that starts with emp_ under database name hr * moved SELF_OR_CHILD from enum resource-matching-scope to enum resource-element-matching-scope This is need to create an api which can find whether a user/group is authorized to the given operation on any resource of give type. This is needed to implement a Ranger Kafka authorizer API which checks if the caller is authorized to perform the given ACL operation on at least one resource of the given type. [https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType]) was: Support SELF_OR_PREFIX resource matching scope in Ranger Authorization This is need to create an api which can find whether a user/group is authorized to the given operation on any resource of give type. This is needed to implement a Ranger Kafka authorizer API which checks if the caller is authorized to perform the given ACL operation on at least one resource of the given type. [https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType]) > Support SELF_OR_PREFIX resource matching scope in Ranger Authorization > --- > > Key: RANGER-4165 > URL: https://issues.apache.org/jira/browse/RANGER-4165 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Ramesh Mani >Assignee: Madhan Neethiraj >Priority: Major > > Support SELF_OR_PREFIX resource matching scope in Ranger Authorization > * introduced resource-element matching scope SELF_OR_PREFIX, which can be > used to ask Ranger policy engine the following -- check if a user/group/role > has read access in any path/file under directory /dept/hr/ -- check if a > user/group/role has select access to any table having name that starts with > emp_ under database name hr > * moved SELF_OR_CHILD from enum resource-matching-scope to enum > resource-element-matching-scope > This is need to create an api which can find whether a user/group is > authorized to the given operation on any resource of give type. > This is needed to implement a Ranger Kafka authorizer API which checks if the > caller is authorized to perform the given ACL operation on at least one > resource of the given type. > [https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4165) Support SELF_OR_PREFIX resource matching scope in Ranger Authorization
[ https://issues.apache.org/jira/browse/RANGER-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723252#comment-17723252 ] Ramesh Mani edited comment on RANGER-4165 at 5/24/23 3:10 PM: -- Attached reworked Patch from [~madhan] [https://reviews.apache.org/r/74441/] [~abhayk] Please review this patch. Thanks. was (Author: rmani): Attached reworked Patch from [~madhan] [https://reviews.apache.org/r/74441/diff/2#index_header] [~abhayk] Please review this patch. Thanks. > Support SELF_OR_PREFIX resource matching scope in Ranger Authorization > --- > > Key: RANGER-4165 > URL: https://issues.apache.org/jira/browse/RANGER-4165 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Ramesh Mani >Assignee: Madhan Neethiraj >Priority: Major > > Support SELF_OR_PREFIX resource matching scope in Ranger Authorization > This is need to create an api which can find whether a user/group is > authorized to the given operation on any resource of give type. > This is needed to implement a Ranger Kafka authorizer API which checks if the > caller is authorized to perform the given ACL operation on at least one > resource of the given type. > [https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4165) Support SELF_OR_PREFIX resource matching scope in Ranger Authorization
[ https://issues.apache.org/jira/browse/RANGER-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned RANGER-4165: --- Assignee: Madhan Neethiraj (was: Ramesh Mani) > Support SELF_OR_PREFIX resource matching scope in Ranger Authorization > --- > > Key: RANGER-4165 > URL: https://issues.apache.org/jira/browse/RANGER-4165 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Ramesh Mani >Assignee: Madhan Neethiraj >Priority: Major > > Support SELF_OR_PREFIX resource matching scope in Ranger Authorization > This is need to create an api which can find whether a user/group is > authorized to the given operation on any resource of give type. > This is needed to implement a Ranger Kafka authorizer API which checks if the > caller is authorized to perform the given ACL operation on at least one > resource of the given type. > [https://kafka.apache.org/28/javadoc/org/apache/kafka/server/authorizer/Authorizer.html#authorizeByResourceType(org.apache.kafka.server.authorizer.AuthorizableRequestContext,org.apache.kafka.common.acl.AclOperation,org.apache.kafka.common.resource.ResourceType]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4119) [UI] Syntax check button missing in policy level condition
[
https://issues.apache.org/jira/browse/RANGER-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar reassigned RANGER-4119:
---
Assignee: Dhaval Rajpara
> [UI] Syntax check button missing in policy level condition
> --
>
> Key: RANGER-4119
> URL: https://issues.apache.org/jira/browse/RANGER-4119
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.4.0
>Reporter: Madhan Neethiraj
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: image-2023-03-03-00-04-10-367.png,
> image-2023-03-03-00-04-45-845.png
>
>
> Ranger policy UI provides {{Syntax check}} button that allows policy authors
> to check if condition expression entered is valid or not. This button is
> available for condition in policy-item level, but its not available for
> condition at policy level - as seen in following images:
>
> Policy-item level:
> !image-2023-03-03-00-04-45-845.png|width=661,height=453!
>
> Policy level:
> !image-2023-03-03-00-04-10-367.png|width=661,height=488!
>
> CC: [~ni3galave], [~Dhaval.Rajpara]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4132) [Ranger UI] If view policy button is clicked for a policy which is deleted, then the page gets stuck in loading state
[ https://issues.apache.org/jira/browse/RANGER-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reassigned RANGER-4132: --- Assignee: Dhaval Rajpara > [Ranger UI] If view policy button is clicked for a policy which is deleted, > then the page gets stuck in loading state > - > > Key: RANGER-4132 > URL: https://issues.apache.org/jira/browse/RANGER-4132 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Dhaval Rajpara >Priority: Major > > In Ranger Admin UI, the policies list for a specific service are not updated > automatically. > So in case a page is open for a specific service and it contains a policy, > for e.g with policy id 99, and the policy is deleted from another tab / from > an API request, > and if the user clicks on the view policy button, the server returns a 400 > bad request error, but the page gets stuck with the message "Please wait". > In such scenarios, there should be a message which states that the policy has > been deleted and it should refresh the list of policies for a specific service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4223) Policy view pop-up does not render deny-all-else toggle
[ https://issues.apache.org/jira/browse/RANGER-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reassigned RANGER-4223: -- Assignee: Dhaval Rajpara > Policy view pop-up does not render deny-all-else toggle > --- > > Key: RANGER-4223 > URL: https://issues.apache.org/jira/browse/RANGER-4223 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Madhan Neethiraj >Assignee: Dhaval Rajpara >Priority: Major > Attachments: view-policy.png > > > On clicking view button next to a policy, a pop-up windows is rendered > showing details of the policy, like the one shown in the attached image. This > pop-up does not include the toggle for denyAllElse flag, which is a critical > flag to interpret the impact of the policy. > [~nitin.galave], [~Dhaval.Rajpara] - can you please review? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4253) Left Sidebar layout for Ranger Admin UI in react code base
[ https://issues.apache.org/jira/browse/RANGER-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4253: Attachment: 0001-RANGER-4253.patch > Left Sidebar layout for Ranger Admin UI in react code base > -- > > Key: RANGER-4253 > URL: https://issues.apache.org/jira/browse/RANGER-4253 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4253.patch, home-page-screen.png, > home-page-sidebar.png, policy-listing-screen-with-zone-filter.png, > policy-listing-screen.png > > > Attached templates for left sidebar layout change to be done in react for > Ranger Admin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4187) Not able to search using muliple user filter in access audit tab
[ https://issues.apache.org/jira/browse/RANGER-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reassigned RANGER-4187: --- Assignee: Mugdha Varadkar > Not able to search using muliple user filter in access audit tab > > > Key: RANGER-4187 > URL: https://issues.apache.org/jira/browse/RANGER-4187 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Mugdha Varadkar >Priority: Major > Labels: ranger-react > > Steps > 1. Go to access audit tab > 2. Search with one user > 3. Try selecting user filter again > Note - we dont see user filter in 3 step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4253) Left Sidebar layout for Ranger Admin UI in react code base
[ https://issues.apache.org/jira/browse/RANGER-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4253: Summary: Left Sidebar layout for Ranger Admin UI in react code base (was: Update Left Sidebar layout for Ranger Admin UI in react code base) > Left Sidebar layout for Ranger Admin UI in react code base > -- > > Key: RANGER-4253 > URL: https://issues.apache.org/jira/browse/RANGER-4253 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: home-page-screen.png, home-page-sidebar.png, > policy-listing-screen-with-zone-filter.png, policy-listing-screen.png > > > Attached templates for left sidebar layout change to be done in react for > Ranger Admin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4253) Update Left Sidebar layout for Ranger Admin UI in react code base
[ https://issues.apache.org/jira/browse/RANGER-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4253: Summary: Update Left Sidebar layout for Ranger Admin UI in react code base (was: Updated Left Sidebar layout for Ranger Admin UI in react code base) > Update Left Sidebar layout for Ranger Admin UI in react code base > - > > Key: RANGER-4253 > URL: https://issues.apache.org/jira/browse/RANGER-4253 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: home-page-screen.png, home-page-sidebar.png, > policy-listing-screen-with-zone-filter.png, policy-listing-screen.png > > > Attached templates for left sidebar layout change to be done in react for > Ranger Admin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4253) Updated Left Sidebar layout for Ranger Admin UI in react code base
[ https://issues.apache.org/jira/browse/RANGER-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4253: Labels: ranger-react (was: ) > Updated Left Sidebar layout for Ranger Admin UI in react code base > -- > > Key: RANGER-4253 > URL: https://issues.apache.org/jira/browse/RANGER-4253 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: home-page-screen.png, home-page-sidebar.png, > policy-listing-screen-with-zone-filter.png, policy-listing-screen.png > > > Attached templates for left sidebar layout change to be done in react for > Ranger Admin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4253) Updated Left Sidebar layout for Ranger Admin UI in react code base
[ https://issues.apache.org/jira/browse/RANGER-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4253: Attachment: policy-listing-screen-with-zone-filter.png policy-listing-screen.png home-page-sidebar.png home-page-screen.png > Updated Left Sidebar layout for Ranger Admin UI in react code base > -- > > Key: RANGER-4253 > URL: https://issues.apache.org/jira/browse/RANGER-4253 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Brijesh Bhalala >Priority: Major > Attachments: home-page-screen.png, home-page-sidebar.png, > policy-listing-screen-with-zone-filter.png, policy-listing-screen.png > > > Attached templates for left sidebar layout change to be done in react for > Ranger Admin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
