[jira] [Resolved] (RANGER-2217) Ranger upgrade from 0.7.1 to 1.1.0
[ https://issues.apache.org/jira/browse/RANGER-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushruth Bharath HG resolved RANGER-2217. - Resolution: Fixed > Ranger upgrade from 0.7.1 to 1.1.0 > -- > > Key: RANGER-2217 > URL: https://issues.apache.org/jira/browse/RANGER-2217 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Sushruth Bharath HG >Priority: Blocker > Fix For: 1.1.0 > > > I upgraded Ranger from 0.7.1 to 1.1.0, after that only ranger UI is showing > up, it's not logging in. > What are the pre-requisites to upgrade ranger from 0.7.1? > Will existing policies will carry forward to upgraded version? > Does ranger 1.1 support hadoop 2.7.1 version? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (RANGER-2217) Ranger upgrade from 0.7.1 to 1.1.0
[ https://issues.apache.org/jira/browse/RANGER-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushruth Bharath HG closed RANGER-2217. --- Working fine after clearing the cache > Ranger upgrade from 0.7.1 to 1.1.0 > -- > > Key: RANGER-2217 > URL: https://issues.apache.org/jira/browse/RANGER-2217 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Sushruth Bharath HG >Priority: Blocker > Fix For: 1.1.0 > > > I upgraded Ranger from 0.7.1 to 1.1.0, after that only ranger UI is showing > up, it's not logging in. > What are the pre-requisites to upgrade ranger from 0.7.1? > Will existing policies will carry forward to upgraded version? > Does ranger 1.1 support hadoop 2.7.1 version? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2217) Ranger upgrade from 0.7.1 to 1.1.0
[ https://issues.apache.org/jira/browse/RANGER-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614339#comment-16614339 ] Nitin Galave commented on RANGER-2217: -- [~bharathhg] Can you please close the bug? > Ranger upgrade from 0.7.1 to 1.1.0 > -- > > Key: RANGER-2217 > URL: https://issues.apache.org/jira/browse/RANGER-2217 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Sushruth Bharath HG >Priority: Blocker > Fix For: 1.1.0 > > > I upgraded Ranger from 0.7.1 to 1.1.0, after that only ranger UI is showing > up, it's not logging in. > What are the pre-requisites to upgrade ranger from 0.7.1? > Will existing policies will carry forward to upgraded version? > Does ranger 1.1 support hadoop 2.7.1 version? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2224) 'drop temporary function ' command should be handled by 'global' resource and 'Temorary UDF Admin' permission.
Anuja Leekha created RANGER-2224: Summary: 'drop temporary function ' command should be handled by 'global' resource and 'Temorary UDF Admin' permission. Key: RANGER-2224 URL: https://issues.apache.org/jira/browse/RANGER-2224 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.0.0 Reporter: Anuja Leekha Fix For: 2.0.0 'drop temporary function ' command should be handled by 'global' resource and 'Temorary UDF Admin' permission. As of today, in order to drop a temporary UDF, you need a policy with Database=* , UDF=* , permission=Drop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2223) Add support for Create operation with Topic resource in Kafka.
Ramesh Mani created RANGER-2223: --- Summary: Add support for Create operation with Topic resource in Kafka. Key: RANGER-2223 URL: https://issues.apache.org/jira/browse/RANGER-2223 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.0.0 Reporter: Ramesh Mani This Jira is to support CREATE operation on Topic. Earlier `Create` operation existed only for the Cluster resource. Any user who needs to give the authorization to create any topic had to be allowed for Create operation on a Cluster resource. In 2.0, `Create` operation is added for Topic resource which allows fine-grained policies like a specific user user1 can have CREATE TOPIC permission on topic `TEST` instead of permission to create any topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2222) Apache RangerKafkaPlugin support to handle Kafka Cluster as a new resource
[ https://issues.apache.org/jira/browse/RANGER-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned RANGER-: --- Assignee: Ramesh Mani > Apache RangerKafkaPlugin support to handle Kafka Cluster as a new resource > -- > > Key: RANGER- > URL: https://issues.apache.org/jira/browse/RANGER- > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Currently, cluster resource permissions are exposed in Ranger with Topic > resource as *. This is not the right convention as cluster resource is not a > super set including topic resources. > Cluster resource permissions: > Alter > AlterConfigs > ClusterAction > Create > Describe > DescribeConfigs > IdempotentWrite > Topic resource operations: > Alter > AlterConfigs > Create > Delete > Describe > DescribeConfigs > Read > Write > Users should be able to define policies with cluster resource and topic > resource with respective permissions. Names of some of the permissions are > same in topic and cluster but they are meant for the different purpose. > Example: AlterConfigs on the topic resource is about altering configs of a > topic only but AlterConfigs permission on Custer resource is meant for > altering configs on the broker. > Upgrading cluster should upgrade existing policies in to topic and cluster > resource level policies with respective permissions. I believe that the > default policy that is getting created would address this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2222) Apache RangerKafkaPlugin support to handle Kafka Cluster as a new resource
Ramesh Mani created RANGER-: --- Summary: Apache RangerKafkaPlugin support to handle Kafka Cluster as a new resource Key: RANGER- URL: https://issues.apache.org/jira/browse/RANGER- Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.0.0 Reporter: Ramesh Mani Currently, cluster resource permissions are exposed in Ranger with Topic resource as *. This is not the right convention as cluster resource is not a super set including topic resources. Cluster resource permissions: Alter AlterConfigs ClusterAction Create Describe DescribeConfigs IdempotentWrite Topic resource operations: Alter AlterConfigs Create Delete Describe DescribeConfigs Read Write Users should be able to define policies with cluster resource and topic resource with respective permissions. Names of some of the permissions are same in topic and cluster but they are meant for the different purpose. Example: AlterConfigs on the topic resource is about altering configs of a topic only but AlterConfigs permission on Custer resource is meant for altering configs on the broker. Upgrading cluster should upgrade existing policies in to topic and cluster resource level policies with respective permissions. I believe that the default policy that is getting created would address this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2221) Apache Ranger Kafka authorizer should support new resource "DelegationToken" in Apache Kafka 2.0.0 version
Ramesh Mani created RANGER-2221: --- Summary: Apache Ranger Kafka authorizer should support new resource "DelegationToken" in Apache Kafka 2.0.0 version Key: RANGER-2221 URL: https://issues.apache.org/jira/browse/RANGER-2221 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.0.0 Reporter: Ramesh Mani Apache Ranger Kafka authorizer should support new resource "DelegationToken" in Apache Kafka 2.0.0 version Scop of this Jira is to support "DESCRIBE" permission on "DelegationToken" resource. CREATE / DELETE on the delegation token will be supported when it available in Apache Kafka in later releases. Please refer to [https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Authorizations] for Apache Kafka Authorization model and DelegationToken resource and its operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2221) Apache Ranger Kafka authorizer should support new resource "DelegationToken" in Apache Kafka 2.0.0 version
[ https://issues.apache.org/jira/browse/RANGER-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned RANGER-2221: --- Assignee: Ramesh Mani > Apache Ranger Kafka authorizer should support new resource "DelegationToken" > in Apache Kafka 2.0.0 version > -- > > Key: RANGER-2221 > URL: https://issues.apache.org/jira/browse/RANGER-2221 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Apache Ranger Kafka authorizer should support new resource "DelegationToken" > in Apache Kafka 2.0.0 version > Scop of this Jira is to support "DESCRIBE" permission on "DelegationToken" > resource. > CREATE / DELETE on the delegation token will be supported when it available > in Apache Kafka in later releases. > Please refer to > [https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Authorizations] for > Apache Kafka Authorization model and DelegationToken resource and its > operations. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2220) Admin UI loads slowly because of many small JavaScript files
Csaba Koncz created RANGER-2220: --- Summary: Admin UI loads slowly because of many small JavaScript files Key: RANGER-2220 URL: https://issues.apache.org/jira/browse/RANGER-2220 Project: Ranger Issue Type: Bug Components: admin Affects Versions: 1.1.0 Reporter: Csaba Koncz The Admin UI web page loads slowly after login (~10 seconds or more, depending on network conditions) This is due to the ~140 small JavaScript files that need to be downloaded before the UI can be presented to the user. Compressing/concatenating (=minifying) JS resources and downloading them in a single step can improve the situation. Prototyped a solution for version 0.7 (using RequireJS Optimizer), will try to port it to the master version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68211: RANGER-2157 Add NiFi Registry service definition and NiFiRegistryClient
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68211/ --- (Updated Sept. 13, 2018, 12:25 p.m.) Review request for ranger. Changes --- Removed unnecessary imports. Bugs: RANGER-2157 https://issues.apache.org/jira/browse/RANGER-2157 Repository: ranger Description --- Adding NiFi Registry service. NiFi Registry is a sub-project of NiFi. Diffs (updated) - agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java 5e74da85a agents-common/src/main/resources/service-defs/ranger-servicedef-nifi-registry.json PRE-CREATION plugin-nifi-registry/.gitignore PRE-CREATION plugin-nifi-registry/pom.xml PRE-CREATION plugin-nifi-registry/src/main/java/org/apache/ranger/services/nifi/registry/RangerServiceNiFiRegistry.java PRE-CREATION plugin-nifi-registry/src/main/java/org/apache/ranger/services/nifi/registry/client/NiFiRegistryAuthType.java PRE-CREATION plugin-nifi-registry/src/main/java/org/apache/ranger/services/nifi/registry/client/NiFiRegistryClient.java PRE-CREATION plugin-nifi-registry/src/main/java/org/apache/ranger/services/nifi/registry/client/NiFiRegistryConfigs.java PRE-CREATION plugin-nifi-registry/src/main/java/org/apache/ranger/services/nifi/registry/client/NiFiRegistryConnectionMgr.java PRE-CREATION plugin-nifi-registry/src/test/java/org/apache/ranger/services/nifi/registry/client/TestNiFiRegistryClient.java PRE-CREATION plugin-nifi-registry/src/test/java/org/apache/ranger/services/nifi/registry/client/TestNiFiRegistryConnectionMgr.java PRE-CREATION plugin-nifi-registry/src/test/resources/resources-response.json PRE-CREATION pom.xml 472199d5d src/main/assembly/admin-web.xml d0f354520 Diff: https://reviews.apache.org/r/68211/diff/5/ Changes: https://reviews.apache.org/r/68211/diff/4-5/ Testing --- Tested on local machine. In order to get NiFi Registry for integration tests, NiFi Registry needs to be built manually as the change is not released at NiFi Registry project yet. Please check [NiFi Registry Pull Request 131 for NIFIREG-186](https://github.com/apache/nifi-registry/pull/131) to do so, especially this [README](https://github.com/apache/nifi-registry/blob/29239be99a5f6275060ecbdcb16ae9a8e7abef86/nifi-registry-extensions/nifi-registry-ranger-extension/README.md) file should be a starting point. Thanks, ijokaruma...@gmail.com Koji
