[jira] [Reopened] (RANGER-4142) Update Apache Ranger website with 2.4.0
[ https://issues.apache.org/jira/browse/RANGER-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reopened RANGER-4142: -- > Update Apache Ranger website with 2.4.0 > > > Key: RANGER-4142 > URL: https://issues.apache.org/jira/browse/RANGER-4142 > Project: Ranger > Issue Type: Sub-task > Components: Ranger > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-RANGER-4142-added-docs-update-for-2.4.0-release-in-r.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4214) Build broken on JDK11 -
[
https://issues.apache.org/jira/browse/RANGER-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj reassigned RANGER-4214:
Assignee: Selvamohan Neethiraj
> Build broken on JDK11 -
>
>
> Key: RANGER-4214
> URL: https://issues.apache.org/jira/browse/RANGER-4214
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
> Reporter: Selvamohan Neethiraj
> Assignee: Selvamohan Neethiraj
>Priority: Blocker
>
> see message from builds.apache.org - Ranger Build
> {code:java}
> INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[23,23]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[24,23]
> error: cannot find symbol
> [ERROR] symbol: class PreDestroy
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[41,2]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: class ServiceManager
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[56,2]
> error: cannot find symbol
> [INFO] 4 errors {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4214) Build broken on JDK11 -
Selvamohan Neethiraj created RANGER-4214:
Summary: Build broken on JDK11 -
Key: RANGER-4214
URL: https://issues.apache.org/jira/browse/RANGER-4214
Project: Ranger
Issue Type: Bug
Components: build-infra
Reporter: Selvamohan Neethiraj
see message from builds.apache.org - Ranger Build
{code:java}
INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[23,23]
error: cannot find symbol
[ERROR] symbol: class PostConstruct
location: package javax.annotation
/home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[24,23]
error: cannot find symbol
[ERROR] symbol: class PreDestroy
location: package javax.annotation
/home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[41,2]
error: cannot find symbol
[ERROR] symbol: class PostConstruct
location: class ServiceManager
/home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[56,2]
error: cannot find symbol
[INFO] 4 errors {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4214) Build broken on JDK11 -
[
https://issues.apache.org/jira/browse/RANGER-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717381#comment-17717381
]
Selvamohan Neethiraj commented on RANGER-4214:
--
Added Dependency to resolve the issue -
d64f578c177e86712a55713098f136bb487a7f31
> Build broken on JDK11 -
>
>
> Key: RANGER-4214
> URL: https://issues.apache.org/jira/browse/RANGER-4214
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
> Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
>Priority: Blocker
>
> see message from builds.apache.org - Ranger Build
> {code:java}
> INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[23,23]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[24,23]
> error: cannot find symbol
> [ERROR] symbol: class PreDestroy
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[41,2]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: class ServiceManager
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[56,2]
> error: cannot find symbol
> [INFO] 4 errors {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4214) Build broken on JDK11 -
[
https://issues.apache.org/jira/browse/RANGER-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717402#comment-17717402
]
Selvamohan Neethiraj commented on RANGER-4214:
--
The issue is fixed now after applying the patch.
[https://ci-builds.apache.org/job/Ranger/job/ranger-master-mvn-build/803/]
> Build broken on JDK11 -
>
>
> Key: RANGER-4214
> URL: https://issues.apache.org/jira/browse/RANGER-4214
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
> Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
>Priority: Blocker
>
> see message from builds.apache.org - Ranger Build
> {code:java}
> INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[23,23]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[24,23]
> error: cannot find symbol
> [ERROR] symbol: class PreDestroy
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[41,2]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: class ServiceManager
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[56,2]
> error: cannot find symbol
> [INFO] 4 errors {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-4214) Build broken on JDK11 -
[
https://issues.apache.org/jira/browse/RANGER-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj resolved RANGER-4214.
--
Fix Version/s: 3.0.0
Resolution: Fixed
> Build broken on JDK11 -
>
>
> Key: RANGER-4214
> URL: https://issues.apache.org/jira/browse/RANGER-4214
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
> Reporter: Selvamohan Neethiraj
> Assignee: Selvamohan Neethiraj
>Priority: Blocker
> Fix For: 3.0.0
>
>
> see message from builds.apache.org - Ranger Build
> {code:java}
> INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[23,23]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[24,23]
> error: cannot find symbol
> [ERROR] symbol: class PreDestroy
> location: package javax.annotation
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[41,2]
> error: cannot find symbol
> [ERROR] symbol: class PostConstruct
> location: class ServiceManager
> /home/jenkins/jenkins-agent/workspace/Ranger/ranger-master-snapshot-publish/ranger-common-ha/src/main/java/org/apache/ranger/ha/service/ServiceManager.java:[56,2]
> error: cannot find symbol
> [INFO] 4 errors {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4020) ranger-authn is required by security-admin but not compiled before it
[ https://issues.apache.org/jira/browse/RANGER-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719324#comment-17719324 ] Selvamohan Neethiraj commented on RANGER-4020: -- [~kirbyzhou] - The maven dependency should automatically build this module - even if it is not listed. Can you please reverify and provide details on the exact error message that is displayed? > ranger-authn is required by security-admin but not compiled before it > - > > Key: RANGER-4020 > URL: https://issues.apache.org/jira/browse/RANGER-4020 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: kirby zhou >Priority: Major > > [WARNING] The POM for org.apache.ranger:ranger-authn:jar:3.0.0-SNAPSHOT is > missing, no dependency information available > The POM for org.apache.ranger:ranger-authn:jar:3.0.0-SNAPSHOT is missing, no > dependency information available > > In root pom.xml, profile "all", ranger-authn module is not listed here. > It should be compiled before security-admin. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4224) Ranger Doc Site : Remove the reference to external sites ...
Selvamohan Neethiraj created RANGER-4224:
Summary: 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
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] [Resolved] (RANGER-4142) Update Apache Ranger website with 2.4.0
[ https://issues.apache.org/jira/browse/RANGER-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-4142. -- Resolution: Fixed > Update Apache Ranger website with 2.4.0 > > > Key: RANGER-4142 > URL: https://issues.apache.org/jira/browse/RANGER-4142 > Project: Ranger > Issue Type: Sub-task > Components: Ranger > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-RANGER-4142-added-docs-update-for-2.4.0-release-in-r.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4142) Update Apache Ranger website with 2.4.0
[ https://issues.apache.org/jira/browse/RANGER-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707160#comment-17707160 ] Selvamohan Neethiraj edited comment on RANGER-4142 at 5/5/23 1:23 AM: -- Update the release information in SVN repo [https://svn.apache.org/repos/asf/ranger/site/trunk] and Pushed the changes. Waiting to get the updates on [https://ranger.apache.org|https://ranger.apache.org/] was (Author: sneethiraj): Update the release information in SVN repo https://svn.apache.org/repos/asf/ranger/site/trunk and Pushed the changes. Waiting to get the updates on [https://ranger.apache.prg|https://ranger.apache.prg/] > Update Apache Ranger website with 2.4.0 > > > Key: RANGER-4142 > URL: https://issues.apache.org/jira/browse/RANGER-4142 > Project: Ranger > Issue Type: Sub-task > Components: Ranger > Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-RANGER-4142-added-docs-update-for-2.4.0-release-in-r.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4616) Updated to committer info
Selvamohan Neethiraj created RANGER-4616: Summary: Updated to committer info Key: RANGER-4616 URL: https://issues.apache.org/jira/browse/RANGER-4616 Project: Ranger Issue Type: Task Components: documentation Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3111) Presto UI 8443 cannot be configured with permissions
[ https://issues.apache.org/jira/browse/RANGER-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3111: - Fix Version/s: (was: 2.10) 2.2.0 > Presto UI 8443 cannot be configured with permissions > > > Key: RANGER-3111 > URL: https://issues.apache.org/jira/browse/RANGER-3111 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: wangfei >Priority: Major > Fix For: 2.2.0 > > > When I configure the Presto plug-in, I can only view presto Web's query > details with my own account. What if I configure Presto Web to view details? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3217) Ranger's Atlas plugin throws unexpected errors
[ https://issues.apache.org/jira/browse/RANGER-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3217: - Fix Version/s: (was: 2.1.0) 2.1.1 > Ranger's Atlas plugin throws unexpected errors > -- > > Key: RANGER-3217 > URL: https://issues.apache.org/jira/browse/RANGER-3217 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.1.0 >Reporter: Hisham Ismail >Priority: Blocker > Fix For: 2.1.1 > > > After deploying atlas with ranger plugin enabled, we receive the following > errors in the logs: > 2021-03-22 08:10:26,633 ERROR - [main:] ~ > addResourceIfReadable(ranger-atlas-policymgr-ssl.xml): couldn't find resource > file location (RangerConfiguration:63) > │ > │ 2021-03-22 08:10:26,643 ERROR - [main:] ~ > addResourceIfReadable(ranger-atlas-atlas-audit.xml): couldn't find resource > file location (RangerConfiguration:63) > │ > │ 2021-03-22 08:10:26,644 ERROR - [main:] ~ > addResourceIfReadable(ranger-atlas-atlas-security.xml): couldn't find > resource file location (RangerConfiguration:63) > > In our install.properties file we used service_name = atlas and this error > changes on different values of service_name. On the ranger webui the plugin > is green with 200 and if i reinstall and use an invalid service name atlas > crashes. Therefore, i assume that the plugin is somehow working (I also > tested a simple feature) but i am not sure if these errors are causing harm > or making the plugin not fully functional. Can you please advise? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3031) Optimize authentication by cancelling setup when optimized for retrieval is false
[ https://issues.apache.org/jira/browse/RANGER-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3031: - Fix Version/s: (was: 2.1.0) 2.1.1 > Optimize authentication by cancelling setup when optimized for retrieval is > false > - > > Key: RANGER-3031 > URL: https://issues.apache.org/jira/browse/RANGER-3031 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.0.0, 1.2.0, 2.1.0 >Reporter: JieMin >Priority: Major > Labels: performance, pull-request-available > Fix For: 2.1.1 > > Original Estimate: 4h > Remaining Estimate: 4h > > when the optimized for retrieval is false , the process of setting up > wildcard policies will be postponed to authentication, which will slow down > the authentication. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
[
https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436258#comment-17436258
]
Selvamohan Neethiraj commented on RANGER-2994:
--
[~mollonado] - Do you see any problem in upgrading the kylin version to 3.1.2
to avoid this issue?
{code}
-2.6.4
+3.1.2
{code}
> ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
> -
>
> Key: RANGER-2994
> URL: https://issues.apache.org/jira/browse/RANGER-2994
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Georgi Ivanov
>Priority: Major
>
> Ranger 2.1.0 release cannot compile due to broken kylin maven dependency.
> the kylin version is set to 2.6.4 in the main project pom.xml
>
> 2.6.4
>
> plugin-kylin/pom.xml
> ranger-kylin-plugin-shim/pom.xml
> both reference kylin-server-base which has dependency on kylin-datasource-sdk
> which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is
> not available.
>
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy
> -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2
> -DoutputDirectory=./
> fails
> and
> [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4]
>
> shows the broken dependency.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
[ https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-2994: Assignee: Selvamohan Neethiraj > ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency > - > > Key: RANGER-2994 > URL: https://issues.apache.org/jira/browse/RANGER-2994 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Georgi Ivanov > Assignee: Selvamohan Neethiraj >Priority: Major > > Ranger 2.1.0 release cannot compile due to broken kylin maven dependency. > the kylin version is set to 2.6.4 in the main project pom.xml > > 2.6.4 > > plugin-kylin/pom.xml > ranger-kylin-plugin-shim/pom.xml > both reference kylin-server-base which has dependency on kylin-datasource-sdk > which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is > not available. > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy > -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2 > -DoutputDirectory=./ > fails > and > [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4] > > shows the broken dependency. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
[ https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2994: - Affects Version/s: 2.1.0 > ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency > - > > Key: RANGER-2994 > URL: https://issues.apache.org/jira/browse/RANGER-2994 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.1.0 >Reporter: Georgi Ivanov > Assignee: Selvamohan Neethiraj >Priority: Major > > Ranger 2.1.0 release cannot compile due to broken kylin maven dependency. > the kylin version is set to 2.6.4 in the main project pom.xml > > 2.6.4 > > plugin-kylin/pom.xml > ranger-kylin-plugin-shim/pom.xml > both reference kylin-server-base which has dependency on kylin-datasource-sdk > which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is > not available. > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy > -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2 > -DoutputDirectory=./ > fails > and > [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4] > > shows the broken dependency. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
[ https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2994: - Attachment: 0001-RANGER-2994-kylin-library-version-is-updated-to-a-li.patch > ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency > - > > Key: RANGER-2994 > URL: https://issues.apache.org/jira/browse/RANGER-2994 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.1.0 >Reporter: Georgi Ivanov > Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-RANGER-2994-kylin-library-version-is-updated-to-a-li.patch > > > Ranger 2.1.0 release cannot compile due to broken kylin maven dependency. > the kylin version is set to 2.6.4 in the main project pom.xml > > 2.6.4 > > plugin-kylin/pom.xml > ranger-kylin-plugin-shim/pom.xml > both reference kylin-server-base which has dependency on kylin-datasource-sdk > which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is > not available. > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy > -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2 > -DoutputDirectory=./ > fails > and > [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4] > > shows the broken dependency. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
[ https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2994: - Fix Version/s: 2.1.1 3.0.0 > ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency > - > > Key: RANGER-2994 > URL: https://issues.apache.org/jira/browse/RANGER-2994 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.1.0 >Reporter: Georgi Ivanov > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.1.1 > > Attachments: > 0001-RANGER-2994-kylin-library-version-is-updated-to-a-li.patch > > > Ranger 2.1.0 release cannot compile due to broken kylin maven dependency. > the kylin version is set to 2.6.4 in the main project pom.xml > > 2.6.4 > > plugin-kylin/pom.xml > ranger-kylin-plugin-shim/pom.xml > both reference kylin-server-base which has dependency on kylin-datasource-sdk > which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is > not available. > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy > -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2 > -DoutputDirectory=./ > fails > and > [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4] > > shows the broken dependency. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3547) Upgrade to use log4j 2.15.0+ version to ensure that we are using supported version of log4j
Selvamohan Neethiraj created RANGER-3547: Summary: Upgrade to use log4j 2.15.0+ version to ensure that we are using supported version of log4j Key: RANGER-3547 URL: https://issues.apache.org/jira/browse/RANGER-3547 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.2.0, 1.2.0 Reporter: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (RANGER-3547) Upgrade to use log4j 2.15.0+ version to ensure that we are using supported version of log4j
[ https://issues.apache.org/jira/browse/RANGER-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457680#comment-17457680 ] Selvamohan Neethiraj commented on RANGER-3547: -- Thanks [~brahmareddy]. However, we need to upgrade the log4j to 2.x as log4j 1 is no longer supported. > Upgrade to use log4j 2.15.0+ version to ensure that we are using supported > version of log4j > --- > > Key: RANGER-3547 > URL: https://issues.apache.org/jira/browse/RANGER-3547 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0, 2.2.0 > Reporter: Selvamohan Neethiraj >Priority: Blocker > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (RANGER-3560) Upgrade kylin version to 2.6.6
[ https://issues.apache.org/jira/browse/RANGER-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471255#comment-17471255 ] Selvamohan Neethiraj commented on RANGER-3560: -- Patch Approved and Committed - https://gitbox.apache.org/repos/asf?p=ranger.git;a=commit;h=c644abfd54cdb92019f54dd468d0240100da5451 After commit, the master branch codebase has been able to build in https://ci-builds.apache.org/ after 6+ months of build failure. https://ci-builds.apache.org/job/Ranger/job/ranger-master-mvn-build/431/ > Upgrade kylin version to 2.6.6 > -- > > Key: RANGER-3560 > URL: https://issues.apache.org/jira/browse/RANGER-3560 > Project: Ranger > Issue Type: Wish > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-3560-Upgrade-kylin-version-to-2.6.6.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
[ https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-2994. -- Resolution: Duplicate Duplicate of RANGER-3560 ... > ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency > - > > Key: RANGER-2994 > URL: https://issues.apache.org/jira/browse/RANGER-2994 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.1.0 >Reporter: Georgi Ivanov > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.1.1, 2.2.0 > > Attachments: > 0001-RANGER-2994-kylin-library-version-is-updated-to-a-li.patch > > > Ranger 2.1.0 release cannot compile due to broken kylin maven dependency. > the kylin version is set to 2.6.4 in the main project pom.xml > > 2.6.4 > > plugin-kylin/pom.xml > ranger-kylin-plugin-shim/pom.xml > both reference kylin-server-base which has dependency on kylin-datasource-sdk > which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is > not available. > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy > -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2 > -DoutputDirectory=./ > fails > and > [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4] > > shows the broken dependency. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (RANGER-3636) Plugin classloader should use classloader of shim class as parent
[ https://issues.apache.org/jira/browse/RANGER-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564253#comment-17564253 ] Selvamohan Neethiraj commented on RANGER-3636: -- [~madhan] - This commit did not seems to make it to 2.3.0 release, should we remove the fix version 2.3.0 out of the release to have cleaner Release Notes ? cc: [~rmani] > Plugin classloader should use classloader of shim class as parent > - > > Key: RANGER-3636 > URL: https://issues.apache.org/jira/browse/RANGER-3636 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: RANGER-3636.patch > > > Ranger uses plugin-classloader to avoid libraries needed by plugin > implementation to be visible in component's CLASSPATH (RANGER-586). For > classes/resources that are not found in plugin-impl directory, the > classloader uses component's (service's) classloader. Currently, current > thread's classloader is used as the component's classloader. However, this > may not work for services that use class isolation themselves, in which case > the current thread's classloader might be different from component's > classloader. A better option will be to use the classloader that loaded the > plugin shim class as the component classloader. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3730) log4j dependency is not completely removed
[
https://issues.apache.org/jira/browse/RANGER-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564258#comment-17564258
]
Selvamohan Neethiraj commented on RANGER-3730:
--
[~rmani] - I see the commit in 2.3.0 release. Closing this issue as Resolved.
{code:java}
$ git log --grep RANGER-3730
commit ce3339c8ab653d99382caba9b2e5f306a7118561 (HEAD, tag:
release-ranger-2.3.0, tag: release-2.3.0-rc3, origin/ranger-2.3)
Author: Kirby Zhou
Date: Fri Jun 24 22:51:51 2022 -0700
RANGER-3730: use reload4j to replace log4j-1.2
Signed-off-by: Ramesh Mani
{code}
> log4j dependency is not completely removed
> --
>
> Key: RANGER-3730
> URL: https://issues.apache.org/jira/browse/RANGER-3730
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Bhavik Patel
>Assignee: kirby zhou
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 0001-RANGER-3730-use-reload4j-to-replace-log4j.patch
>
>
> log4j dependency is present in parent pom file -
> [https://github.com/apache/ranger/blob/master/pom.xml#L166]
>
> [~madhan] [~ma3mansoori123]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-3730) log4j dependency is not completely removed
[ https://issues.apache.org/jira/browse/RANGER-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-3730. -- Resolution: Fixed > log4j dependency is not completely removed > -- > > Key: RANGER-3730 > URL: https://issues.apache.org/jira/browse/RANGER-3730 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.3.0 >Reporter: Bhavik Patel >Assignee: kirby zhou >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: 0001-RANGER-3730-use-reload4j-to-replace-log4j.patch > > > log4j dependency is present in parent pom file - > [https://github.com/apache/ranger/blob/master/pom.xml#L166] > > [~madhan] [~ma3mansoori123] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3832) Unable to Build Ranger due to dependecy library issue
[
https://issues.apache.org/jira/browse/RANGER-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568562#comment-17568562
]
Selvamohan Neethiraj commented on RANGER-3832:
--
I was able to simulate the error on Windows Platform (Win 11) and not on
(ubuntu) linux or Mac.
My Dig command on the Linux returns the following:
{code}
repository.cloudera.com. 3600 IN CNAME
repository-cloudera-com.customers.jfrog.net.
repository-cloudera-com.customers.jfrog.net. 59 IN CNAME
endpointdns-prod-2-use1-lb.jfrog.io.
endpointdns-prod-2-use1-lb.jfrog.io. 59 IN CNAME
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com.
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 54.209.76.115
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 44.206.156.170
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 34.225.85.2
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 54.81.245.86
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 44.193.105.247
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 3.209.39.191
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 52.3.143.22
a730a7a4f324d4c569f6ee42bbb07626-2037148396.us-east-1.elb.amazonaws.com. 59 IN
A 54.152.119.203
{code}
Does anyone knows if the NSLOOKUP command on windows have an issue with the DNS
setup here?
> Unable to Build Ranger due to dependecy library issue
> -
>
> Key: RANGER-3832
> URL: https://issues.apache.org/jira/browse/RANGER-3832
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Ajit S
>Priority: Blocker
>
> I am new to Apache Ranger and am trying to build using the standard maven
> command and I got the following error.
> {code:java}
> [ERROR] Failed to execute goal on project ranger-knox-plugin: Could not
> resolve dependencies for project
> org.apache.ranger:ranger-knox-plugin:jar:3.0.0-SNAPSHOT: Failed to collect
> dependencies at org.apache.knox:gateway-test-release-utils:jar:1.4.0 ->
> org.apache.knox:gateway-release:jar:1.4.0 ->
> org.apache.knox:gateway-discovery-cm:jar:1.4.0 ->
> com.cloudera.api.swagger:cloudera-manager-api-swagger:jar:7.0.3: Failed to
> read artifact descriptor for
> com.cloudera.api.swagger:cloudera-manager-api-swagger:jar:7.0.3: Could not
> transfer artifact
> com.cloudera.api.swagger:cloudera-manager-api-swagger:pom:7.0.3 from/to
> Cloudera (https://repository.cloudera.com/artifactory/cloudera-repos):
> transfer failed for
> https://repository.cloudera.com/artifactory/cloudera-repos/com/cloudera/api/swagger/cloudera-manager-api-swagger/7.0.3/cloudera-manager-api-swagger-7.0.3.pom:
> Unknown host No such host is known (repository.cloudera.com) -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-3832) Unable to Build Ranger due to dependecy library issue
[
https://issues.apache.org/jira/browse/RANGER-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj resolved RANGER-3832.
--
Resolution: Won't Fix
This problem seems to be specific to Windows platform and will not fix for now.
> Unable to Build Ranger due to dependecy library issue
> -
>
> Key: RANGER-3832
> URL: https://issues.apache.org/jira/browse/RANGER-3832
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Ajit S
>Priority: Blocker
>
> I am new to Apache Ranger and am trying to build using the standard maven
> command and I got the following error.
> {code:java}
> [ERROR] Failed to execute goal on project ranger-knox-plugin: Could not
> resolve dependencies for project
> org.apache.ranger:ranger-knox-plugin:jar:3.0.0-SNAPSHOT: Failed to collect
> dependencies at org.apache.knox:gateway-test-release-utils:jar:1.4.0 ->
> org.apache.knox:gateway-release:jar:1.4.0 ->
> org.apache.knox:gateway-discovery-cm:jar:1.4.0 ->
> com.cloudera.api.swagger:cloudera-manager-api-swagger:jar:7.0.3: Failed to
> read artifact descriptor for
> com.cloudera.api.swagger:cloudera-manager-api-swagger:jar:7.0.3: Could not
> transfer artifact
> com.cloudera.api.swagger:cloudera-manager-api-swagger:pom:7.0.3 from/to
> Cloudera (https://repository.cloudera.com/artifactory/cloudera-repos):
> transfer failed for
> https://repository.cloudera.com/artifactory/cloudera-repos/com/cloudera/api/swagger/cloudera-manager-api-swagger/7.0.3/cloudera-manager-api-swagger-7.0.3.pom:
> Unknown host No such host is known (repository.cloudera.com) -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
Selvamohan Neethiraj created RANGER-3866:
Summary: Ranger Build based on Docker is failing with HTTP 503
error ...
Key: RANGER-3866
URL: https://issues.apache.org/jira/browse/RANGER-3866
Project: Ranger
Issue Type: Bug
Components: build-infra
Reporter: Selvamohan Neethiraj
Assignee: Selvamohan Neethiraj
{code:java}
=> ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
=> CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa 0.0s
=> CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c 0.0s
=> [ 2/26] RUN mkdir /tools 0.2s
--
>
http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
--
failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
[
https://issues.apache.org/jira/browse/RANGER-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-3866:
-
Attachment: 0001-RANGER-3866-updated-build-script-to-use-latest-cento.patch
> Ranger Build based on Docker is failing with HTTP 503 error ...
> ---
>
> Key: RANGER-3866
> URL: https://issues.apache.org/jira/browse/RANGER-3866
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
> Reporter: Selvamohan Neethiraj
> Assignee: Selvamohan Neethiraj
>Priority: Major
> Attachments:
> 0001-RANGER-3866-updated-build-script-to-use-latest-cento.patch
>
>
> {code:java}
> => ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
> => CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa
> 0.0s
> => CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c
> 0.0s
> => [ 2/26] RUN mkdir /tools
> 0.2s
> --
> >
> http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
> --
> failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
[
https://issues.apache.org/jira/browse/RANGER-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-3866:
-
Attachment: (was:
0001-RANGER-3866-updated-build-script-to-use-latest-cento.patch)
> Ranger Build based on Docker is failing with HTTP 503 error ...
> ---
>
> Key: RANGER-3866
> URL: https://issues.apache.org/jira/browse/RANGER-3866
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
>Affects Versions: 3.0.0
> Reporter: Selvamohan Neethiraj
> Assignee: Selvamohan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> RANGER-3866-updated-build-script-to-use-latest-cento-wo-debug.diff
>
>
> {code:java}
> => ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
> => CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa
> 0.0s
> => CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c
> 0.0s
> => [ 2/26] RUN mkdir /tools
> 0.2s
> --
> >
> http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
> --
> failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
[
https://issues.apache.org/jira/browse/RANGER-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-3866:
-
Attachment:
RANGER-3866-updated-build-script-to-use-latest-cento-wo-debug.diff
> Ranger Build based on Docker is failing with HTTP 503 error ...
> ---
>
> Key: RANGER-3866
> URL: https://issues.apache.org/jira/browse/RANGER-3866
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
>Affects Versions: 3.0.0
> Reporter: Selvamohan Neethiraj
> Assignee: Selvamohan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> RANGER-3866-updated-build-script-to-use-latest-cento-wo-debug.diff
>
>
> {code:java}
> => ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
> => CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa
> 0.0s
> => CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c
> 0.0s
> => [ 2/26] RUN mkdir /tools
> 0.2s
> --
> >
> http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
> --
> failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-707) Redesign of Apache Ranger Website
[ https://issues.apache.org/jira/browse/RANGER-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-707: Affects Version/s: (was: 0.5.0) 1.1.0 > Redesign of Apache Ranger Website > - > > Key: RANGER-707 > URL: https://issues.apache.org/jira/browse/RANGER-707 > Project: Ranger > Issue Type: Improvement > Components: documentation, Ranger >Affects Versions: 1.1.0 > Reporter: Selvamohan Neethiraj >Assignee: Gautam Borad >Priority: Critical > Attachments: Logo01.jpg, Logo02.jpg, Logo03.jpg, Logo04.jpg, > Logo06.jpg > > > The Apache Ranger website (http://ranger.incubator.apache.org/) needs to > re-organized to have all of the information available to developers and > end-users in an easier manner. > Example Site: > http://cordova.apache.org/ > http://hawq.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2316) Incorrect path in Quick State Guide at http://ranger.apache.org/quick_start_guide.html
Selvamohan Neethiraj created RANGER-2316: Summary: Incorrect path in Quick State Guide at http://ranger.apache.org/quick_start_guide.html Key: RANGER-2316 URL: https://issues.apache.org/jira/browse/RANGER-2316 Project: Ranger Issue Type: Bug Components: documentation Affects Versions: 1.2.0 Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix For: 2.0.0, 1.2.1 Since GIT was moved from [https://git-wip-us.apache.org/repos/asf/ranger.git] to [https://gitbox.apache.org/repos/asf/ranger.git], we need to update the documentation for Quick Start Guide. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2316) Incorrect path in Quick State Guide at http://ranger.apache.org/quick_start_guide.html
[ https://issues.apache.org/jira/browse/RANGER-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730037#comment-16730037 ] Selvamohan Neethiraj commented on RANGER-2316: -- committed to master branch to update docs site - https://gitbox.apache.org/repos/asf?p=ranger.git;a=commit;h=00ffa900695c842f95a5e9366768f670b041bde4 > Incorrect path in Quick State Guide at > http://ranger.apache.org/quick_start_guide.html > -- > > Key: RANGER-2316 > URL: https://issues.apache.org/jira/browse/RANGER-2316 > Project: Ranger > Issue Type: Bug > Components: documentation >Affects Versions: 1.2.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.0.0, 1.2.1 > > Attachments: > 0001-RANGER-2316-fixed-git-repo-path-after-moving-to-gitb.patch > > > Since GIT was moved from [https://git-wip-us.apache.org/repos/asf/ranger.git] > > to [https://gitbox.apache.org/repos/asf/ranger.git], we need to update the > documentation for Quick Start Guide. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2316) Incorrect path in Quick State Guide at http://ranger.apache.org/quick_start_guide.html
[ https://issues.apache.org/jira/browse/RANGER-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-2316. -- Resolution: Fixed Deployed the changes. > Incorrect path in Quick State Guide at > http://ranger.apache.org/quick_start_guide.html > -- > > Key: RANGER-2316 > URL: https://issues.apache.org/jira/browse/RANGER-2316 > Project: Ranger > Issue Type: Bug > Components: documentation >Affects Versions: 1.2.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.0.0, 1.2.1 > > Attachments: > 0001-RANGER-2316-fixed-git-repo-path-after-moving-to-gitb.patch > > > Since GIT was moved from [https://git-wip-us.apache.org/repos/asf/ranger.git] > > to [https://gitbox.apache.org/repos/asf/ranger.git], we need to update the > documentation for Quick Start Guide. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2316) Incorrect path in Quick State Guide at http://ranger.apache.org/quick_start_guide.html
[ https://issues.apache.org/jira/browse/RANGER-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2316: - Attachment: 0001-RANGER-2316-fixed-git-repo-path-after-moving-to-gitb.patch > Incorrect path in Quick State Guide at > http://ranger.apache.org/quick_start_guide.html > -- > > Key: RANGER-2316 > URL: https://issues.apache.org/jira/browse/RANGER-2316 > Project: Ranger > Issue Type: Bug > Components: documentation >Affects Versions: 1.2.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.0.0, 1.2.1 > > Attachments: > 0001-RANGER-2316-fixed-git-repo-path-after-moving-to-gitb.patch > > > Since GIT was moved from [https://git-wip-us.apache.org/repos/asf/ranger.git] > > to [https://gitbox.apache.org/repos/asf/ranger.git], we need to update the > documentation for Quick Start Guide. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-542) Remove MPL license text from license file
[ https://issues.apache.org/jira/browse/RANGER-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-542: --- Assignee: Don Bosco Durai Since it is closed as part of another issue, assigning this to reporter (Bosco) > Remove MPL license text from license file > - > > Key: RANGER-542 > URL: https://issues.apache.org/jira/browse/RANGER-542 > Project: Ranger > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Don Bosco Durai >Assignee: Don Bosco Durai >Priority: Critical > > We need to remove MPL license text from license file. > Refer to JIRA https://issues.apache.org/jira/browse/RANGER-316 and release > feedback http://s.apache.org/NBH -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2605) Update maven version to 3.6.2
[ https://issues.apache.org/jira/browse/RANGER-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-2605: Assignee: Selvamohan Neethiraj (was: Velmurugan Periasamy) > Update maven version to 3.6.2 > - > > Key: RANGER-2605 > URL: https://issues.apache.org/jira/browse/RANGER-2605 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > > Maven version needs to be updated to 3.3.9. See > https://issues.apache.org/jira/browse/INFRA-19222 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[ https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-2606: Assignee: Selvamohan Neethiraj > Maven central deployment publishing only the top level ranger artifact > -- > > Key: RANGER-2606 > URL: https://issues.apache.org/jira/browse/RANGER-2606 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > > Following these instructions to publish Apache Ranger artifacts to maven > central. > https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central > This used to work before, but now it is deploying only the top level > artifact. Most likely was caused by > https://issues.apache.org/jira/browse/RANGER-2243 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2605) Update maven version to 3.6.2
[ https://issues.apache.org/jira/browse/RANGER-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-2605: Assignee: Velmurugan Periasamy (was: Selvamohan Neethiraj) > Update maven version to 3.6.2 > - > > Key: RANGER-2605 > URL: https://issues.apache.org/jira/browse/RANGER-2605 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy >Assignee: Velmurugan Periasamy >Priority: Major > Fix For: 2.1.0 > > > Maven version needs to be updated to 3.3.9. See > https://issues.apache.org/jira/browse/INFRA-19222 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[ https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2606: - Attachment: 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch > Maven central deployment publishing only the top level ranger artifact > -- > > Key: RANGER-2606 > URL: https://issues.apache.org/jira/browse/RANGER-2606 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch > > > Following these instructions to publish Apache Ranger artifacts to maven > central. > https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central > This used to work before, but now it is deploying only the top level > artifact. Most likely was caused by > https://issues.apache.org/jira/browse/RANGER-2243 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[
https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946249#comment-16946249
]
Selvamohan Neethiraj commented on RANGER-2606:
--
Attached patch for fixing the deployment of {jar|war|...} files from the
modules ...
> Maven central deployment publishing only the top level ranger artifact
> --
>
> Key: RANGER-2606
> URL: https://issues.apache.org/jira/browse/RANGER-2606
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Velmurugan Periasamy
>Assignee: Selvamohan Neethiraj
>Priority: Major
> Fix For: 2.1.0
>
> Attachments:
> 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch
>
>
> Following these instructions to publish Apache Ranger artifacts to maven
> central.
> https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central
> This used to work before, but now it is deploying only the top level
> artifact. Most likely was caused by
> https://issues.apache.org/jira/browse/RANGER-2243
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[ https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946257#comment-16946257 ] Selvamohan Neethiraj commented on RANGER-2606: -- Review Request (https://reviews.apache.org/r/71587/) has been added. > Maven central deployment publishing only the top level ranger artifact > -- > > Key: RANGER-2606 > URL: https://issues.apache.org/jira/browse/RANGER-2606 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch > > > Following these instructions to publish Apache Ranger artifacts to maven > central. > https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central > This used to work before, but now it is deploying only the top level > artifact. Most likely was caused by > https://issues.apache.org/jira/browse/RANGER-2243 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[ https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2606: - Affects Version/s: 2.0.0 2.1 > Maven central deployment publishing only the top level ranger artifact > -- > > Key: RANGER-2606 > URL: https://issues.apache.org/jira/browse/RANGER-2606 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1 >Reporter: Velmurugan Periasamy > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch > > > Following these instructions to publish Apache Ranger artifacts to maven > central. > https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central > This used to work before, but now it is deploying only the top level > artifact. Most likely was caused by > https://issues.apache.org/jira/browse/RANGER-2243 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2532) unable to connect to hiverepo
[ https://issues.apache.org/jira/browse/RANGER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2532: - Attachment: 0001-RANGER-2606-Added-all-modules-to-the-sign-artifacts-master-branch.patch > unable to connect to hiverepo > -- > > Key: RANGER-2532 > URL: https://issues.apache.org/jira/browse/RANGER-2532 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: rohit >Priority: Blocker > > Unable to connect to hiveserver2 using http transport mode with AD LDAP > authentication > Error: > ERROR org.apache.ranger.plugin.util.PasswordUtils (PasswordUtils.java:147) - > Unable to decrypt password due to error > javax.crypto.IllegalBlockSizeException: Input length (with padding) not > multiple of 8 bytes > > h1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2532) unable to connect to hiverepo
[ https://issues.apache.org/jira/browse/RANGER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2532: - Attachment: (was: 0001-RANGER-2606-Added-all-modules-to-the-sign-artifacts-master-branch.patch) > unable to connect to hiverepo > -- > > Key: RANGER-2532 > URL: https://issues.apache.org/jira/browse/RANGER-2532 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: rohit >Priority: Blocker > > Unable to connect to hiveserver2 using http transport mode with AD LDAP > authentication > Error: > ERROR org.apache.ranger.plugin.util.PasswordUtils (PasswordUtils.java:147) - > Unable to decrypt password due to error > javax.crypto.IllegalBlockSizeException: Input length (with padding) not > multiple of 8 bytes > > h1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[ https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2606: - Attachment: 0001-RANGER-2606-Added-all-modules-to-the-sign-artifacts-master-branch.patch > Maven central deployment publishing only the top level ranger artifact > -- > > Key: RANGER-2606 > URL: https://issues.apache.org/jira/browse/RANGER-2606 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0 >Reporter: Velmurugan Periasamy > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2606-Added-all-modules-to-the-sign-artifacts-master-branch.patch, > 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch > > > Following these instructions to publish Apache Ranger artifacts to maven > central. > https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central > This used to work before, but now it is deploying only the top level > artifact. Most likely was caused by > https://issues.apache.org/jira/browse/RANGER-2243 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2606) Maven central deployment publishing only the top level ranger artifact
[ https://issues.apache.org/jira/browse/RANGER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946396#comment-16946396 ] Selvamohan Neethiraj commented on RANGER-2606: -- [~vel] - Please use 0001-RANGER-2606-Added-all-modules-to-the-sign-artifacts-master-branch.patch for applying to master branch ... > Maven central deployment publishing only the top level ranger artifact > -- > > Key: RANGER-2606 > URL: https://issues.apache.org/jira/browse/RANGER-2606 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0 >Reporter: Velmurugan Periasamy > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2606-Added-all-modules-to-the-sign-artifacts-master-branch.patch, > 0001-RANGER-2606-added-module-to-sign-artifacts-profile-t.patch > > > Following these instructions to publish Apache Ranger artifacts to maven > central. > https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central > This used to work before, but now it is deploying only the top level > artifact. Most likely was caused by > https://issues.apache.org/jira/browse/RANGER-2243 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
Selvamohan Neethiraj created RANGER-2907: Summary: Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml Key: RANGER-2907 URL: https://issues.apache.org/jira/browse/RANGER-2907 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 2.0.0 Reporter: Selvamohan Neethiraj When a CA certified certificate is used by Ranger Admin, the RangerPlugin should be able to use the default cacerts (from JVM) without having to configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-2907: Assignee: Selvamohan Neethiraj > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2907: - Attachment: 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust-v1.patch > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust-v1.patch, > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164008#comment-17164008 ] Selvamohan Neethiraj commented on RANGER-2907: -- Thanks [~pradeep]. I reviewed your patch; I see that we can achieve the same thing by getting the default TrustManagerFactory (see the modified v1 patch). Please review and provide your feedback. cc: [~vel] [~mad...@apache.org] > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust-v1.patch, > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2907: - Attachment: 0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust-v1.patch, > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch, > 0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2907: - Attachment: (was: 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust-v1.patch) > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch, > 0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164008#comment-17164008 ] Selvamohan Neethiraj edited comment on RANGER-2907 at 7/23/20, 11:11 PM: - Thanks [~pradeep]. I reviewed your patch; I see that we can achieve the same thing by getting the default TrustManagerFactory (see the modified v1 patch) - [^0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch] . Please review and provide your feedback. cc: [~vel] [~mad...@apache.org] was (Author: sneethiraj): Thanks [~pradeep]. I reviewed your patch; I see that we can achieve the same thing by getting the default TrustManagerFactory (see the modified v1 patch). Please review and provide your feedback. cc: [~vel] [~mad...@apache.org] > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch, > 0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164008#comment-17164008 ] Selvamohan Neethiraj edited comment on RANGER-2907 at 7/23/20, 11:18 PM: - Thanks [~pradeep]. I reviewed your patch; I see that we can achieve the same thing by getting the default TrustManagerFactory (see the modified v1 patch) - [^0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch] . Please review and provide your feedback on https://reviews.apache.org/r/72705/ cc: [~vel] [~mad...@apache.org] was (Author: sneethiraj): Thanks [~pradeep]. I reviewed your patch; I see that we can achieve the same thing by getting the default TrustManagerFactory (see the modified v1 patch) - [^0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch] . Please review and provide your feedback. cc: [~vel] [~mad...@apache.org] > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 2.0.1 > > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch, > 0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2907) Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
[ https://issues.apache.org/jira/browse/RANGER-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-2907. -- Resolution: Fixed commit # 694967aff3d09fcb8c27d1733322e92d44209c99 > Ranger Plugin is not using default TrustManager if a trustmanager is not > specified in ranger-policymgr-ssl.xml > -- > > Key: RANGER-2907 > URL: https://issues.apache.org/jira/browse/RANGER-2907 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 2.0.1 > > Attachments: > 0001-RANGER-2907-Ranger-Plugin-is-not-using-default-Trust.patch, > 0001-RANGER-2907-adding-default-trust-manager-from-JVM-if.patch > > > When a CA certified certificate is used by Ranger Admin, the RangerPlugin > should be able to use the default cacerts (from JVM) without having to > configure it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2611) Ranger should fall back to default TrustManagers if no trust store is specified
[ https://issues.apache.org/jira/browse/RANGER-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2611: - Fix Version/s: 2.0.1 > Ranger should fall back to default TrustManagers if no trust store is > specified > --- > > Key: RANGER-2611 > URL: https://issues.apache.org/jira/browse/RANGER-2611 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Todd Lipcon > Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 2.0.1 > > > Currently if no truststore is specified, the Ranger SSL code path will refuse > to connect, giving an error message "TrustManager is not specified". > Specifying a trust store should not be necessary if the ranger server has its > cert signed by a CA that is already trusted by the JVM, for example because > the cert is signed by a public CA, or a private CA cert has been put into the > default JVM trust store, or because it has been configured via Java system > properties on the command line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2611) Ranger should fall back to default TrustManagers if no trust store is specified
[ https://issues.apache.org/jira/browse/RANGER-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-2611: Assignee: Selvamohan Neethiraj > Ranger should fall back to default TrustManagers if no trust store is > specified > --- > > Key: RANGER-2611 > URL: https://issues.apache.org/jira/browse/RANGER-2611 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Todd Lipcon > Assignee: Selvamohan Neethiraj >Priority: Critical > > Currently if no truststore is specified, the Ranger SSL code path will refuse > to connect, giving an error message "TrustManager is not specified". > Specifying a trust store should not be necessary if the ranger server has its > cert signed by a CA that is already trusted by the JVM, for example because > the cert is signed by a public CA, or a private CA cert has been put into the > default JVM trust store, or because it has been configured via Java system > properties on the command line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2611) Ranger should fall back to default TrustManagers if no trust store is specified
[ https://issues.apache.org/jira/browse/RANGER-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-2611. -- Resolution: Fixed Please refer to RANGER-2907 > Ranger should fall back to default TrustManagers if no trust store is > specified > --- > > Key: RANGER-2611 > URL: https://issues.apache.org/jira/browse/RANGER-2611 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Todd Lipcon >Priority: Critical > > Currently if no truststore is specified, the Ranger SSL code path will refuse > to connect, giving an error message "TrustManager is not specified". > Specifying a trust store should not be necessary if the ranger server has its > cert signed by a CA that is already trusted by the JVM, for example because > the cert is signed by a public CA, or a private CA cert has been put into the > default JVM trust store, or because it has been configured via Java system > properties on the command line. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2958) Unable to run build using docker script - build_ranger_using_docker.sh
Selvamohan Neethiraj created RANGER-2958: Summary: Unable to run build using docker script - build_ranger_using_docker.sh Key: RANGER-2958 URL: https://issues.apache.org/jira/browse/RANGER-2958 Project: Ranger Issue Type: Bug Components: build-infra Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj build_ranger_using_docker.sh is failing due to (a) centos needs diff command to be installed via "yum install" (b) comparision of the SH1 checksum string needs to compare only first column - was doing file compare and failing! (b) installed maven 3.5.4 is not meeting minimum requirement 3.6.2 for ranger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2960) Ranger build using Docker - ubuntu
[ https://issues.apache.org/jira/browse/RANGER-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182175#comment-17182175 ] Selvamohan Neethiraj commented on RANGER-2960: -- tested it on Mac and it worked. > Ranger build using Docker - ubuntu > -- > > Key: RANGER-2960 > URL: https://issues.apache.org/jira/browse/RANGER-2960 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: RANGER-2960.patch > > > Enable building Ranger via Docker, with option to specify branch, profile and > run/skip tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2958) Unable to run build using docker script - build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2958: - Attachment: 0001-RANGER-2958-modified-docker-build-to-fix-ranger-buil.patch > Unable to run build using docker script - build_ranger_using_docker.sh > --- > > Key: RANGER-2958 > URL: https://issues.apache.org/jira/browse/RANGER-2958 > Project: Ranger > Issue Type: Bug > Components: build-infra > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-RANGER-2958-modified-docker-build-to-fix-ranger-buil.patch > > > build_ranger_using_docker.sh is failing due to > (a) centos needs diff command to be installed via "yum install" > (b) comparision of the SH1 checksum string needs to compare only first column > - was doing file compare and failing! > (b) installed maven 3.5.4 is not meeting minimum requirement 3.6.2 for ranger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2958) Unable to run build using docker script - build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2958: - Fix Version/s: 2.1.0 > Unable to run build using docker script - build_ranger_using_docker.sh > --- > > Key: RANGER-2958 > URL: https://issues.apache.org/jira/browse/RANGER-2958 > Project: Ranger > Issue Type: Bug > Components: build-infra > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2958-modified-docker-build-to-fix-ranger-buil.patch > > > build_ranger_using_docker.sh is failing due to > (a) centos needs diff command to be installed via "yum install" > (b) comparision of the SH1 checksum string needs to compare only first column > - was doing file compare and failing! > (b) installed maven 3.5.4 is not meeting minimum requirement 3.6.2 for ranger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2958) Unable to run build using docker script - build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2958: - Fix Version/s: 3.0.0 > Unable to run build using docker script - build_ranger_using_docker.sh > --- > > Key: RANGER-2958 > URL: https://issues.apache.org/jira/browse/RANGER-2958 > Project: Ranger > Issue Type: Bug > Components: build-infra > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: > 0001-RANGER-2958-modified-docker-build-to-fix-ranger-buil.patch > > > build_ranger_using_docker.sh is failing due to > (a) centos needs diff command to be installed via "yum install" > (b) comparision of the SH1 checksum string needs to compare only first column > - was doing file compare and failing! > (b) installed maven 3.5.4 is not meeting minimum requirement 3.6.2 for ranger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2961) Docker setup to run Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182926#comment-17182926 ] Selvamohan Neethiraj commented on RANGER-2961: -- committed the patch - d65628827bbaeb6b32c1bb52e93532ead56b7878 > Docker setup to run Ranger Admin > > > Key: RANGER-2961 > URL: https://issues.apache.org/jira/browse/RANGER-2961 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: RANGER-2961.patch > > > Enable running Ranger Admin via Docker, to build on to the work done in > RANGER-2960 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2958) Unable to run build using docker script - build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186746#comment-17186746 ] Selvamohan Neethiraj commented on RANGER-2958: -- committed the patch - 21485cb4369de07a18eae411f342d38bb709899d after approval in Review Request ... > Unable to run build using docker script - build_ranger_using_docker.sh > --- > > Key: RANGER-2958 > URL: https://issues.apache.org/jira/browse/RANGER-2958 > Project: Ranger > Issue Type: Bug > Components: build-infra > Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: > 0001-RANGER-2958-modified-docker-build-to-fix-ranger-buil.patch > > > build_ranger_using_docker.sh is failing due to > (a) centos needs diff command to be installed via "yum install" > (b) comparision of the SH1 checksum string needs to compare only first column > - was doing file compare and failing! > (b) installed maven 3.5.4 is not meeting minimum requirement 3.6.2 for ranger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2999) Ranger build is failing if you do not have already downloads ~/.m2 lib for calcite-linq4j-1.16.0-kylin-r2
Selvamohan Neethiraj created RANGER-2999: Summary: Ranger build is failing if you do not have already downloads ~/.m2 lib for calcite-linq4j-1.16.0-kylin-r2 Key: RANGER-2999 URL: https://issues.apache.org/jira/browse/RANGER-2999 Project: Ranger Issue Type: Bug Components: build-infra Reporter: Selvamohan Neethiraj 21:07:17 [ERROR] Failed to execute goal on project ranger-kylin-plugin: Could not resolve dependencies for project org.apache.ranger:ranger-kylin-plugin:jar:3.0.0-SNAPSHOT: Failed to collect dependencies at org.apache.kylin:kylin-server-base:jar:2.6.6 -> org.apache.kylin:kylin-query:jar:2.6.6 -> org.apache.kylin:kylin-datasource-sdk:jar:2.6.6 -> org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2: Failed to read artifact descriptor for org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2: Could not transfer artifact org.apache.calcite:calcite-linq4j:pom:1.16.0-kylin-r2 from/to spring-snapshots (http://repo.spring.io/libs-snapshot): Authorization failed for http://repo.spring.io/libs-snapshot/org/apache/calcite/calcite-linq4j/1.16.0-kylin-r2/calcite-linq4j-1.16.0-kylin-r2.pom 403 Forbidden -> [Help 1] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2999) Ranger build is failing if you do not have already downloaded jar under ~/.m2 for calcite-linq4j-1.16.0-kylin-r2
[ https://issues.apache.org/jira/browse/RANGER-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-2999: - Summary: Ranger build is failing if you do not have already downloaded jar under ~/.m2 for calcite-linq4j-1.16.0-kylin-r2 (was: Ranger build is failing if you do not have already downloads ~/.m2 lib for calcite-linq4j-1.16.0-kylin-r2) > Ranger build is failing if you do not have already downloaded jar under ~/.m2 > for calcite-linq4j-1.16.0-kylin-r2 > > > Key: RANGER-2999 > URL: https://issues.apache.org/jira/browse/RANGER-2999 > Project: Ranger > Issue Type: Bug > Components: build-infra > Reporter: Selvamohan Neethiraj >Priority: Critical > > 21:07:17 [ERROR] Failed to execute goal on project ranger-kylin-plugin: Could > not resolve dependencies for project > org.apache.ranger:ranger-kylin-plugin:jar:3.0.0-SNAPSHOT: Failed to collect > dependencies at org.apache.kylin:kylin-server-base:jar:2.6.6 -> > org.apache.kylin:kylin-query:jar:2.6.6 -> > org.apache.kylin:kylin-datasource-sdk:jar:2.6.6 -> > org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2: Failed to read > artifact descriptor for > org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2: Could not transfer > artifact org.apache.calcite:calcite-linq4j:pom:1.16.0-kylin-r2 from/to > spring-snapshots (http://repo.spring.io/libs-snapshot): Authorization failed > for > http://repo.spring.io/libs-snapshot/org/apache/calcite/calcite-linq4j/1.16.0-kylin-r2/calcite-linq4j-1.16.0-kylin-r2.pom > 403 Forbidden -> [Help 1] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-1117) usersync pid location not configurable
[ https://issues.apache.org/jira/browse/RANGER-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838259#comment-15838259 ] Selvamohan Neethiraj commented on RANGER-1117: -- [~yzhou2001] I am not sure if anyone has done a review of this patch. Looks like, the patch is outdated (due to changes on top of the file) and also, this specific bug has been addressed in the code (RANGER-1241 and RANGER-1192). Can you please review the changed code and see if this patch is still needed. cc: [~amadhavi] > usersync pid location not configurable > -- > > Key: RANGER-1117 > URL: https://issues.apache.org/jira/browse/RANGER-1117 > Project: Ranger > Issue Type: Bug > Components: usersync >Affects Versions: 0.5.2, 0.6.0 >Reporter: Yujie Li > Attachments: > 0001-RANGER-1117-usersync-pid-location-not-configurable.patch > > > I am using Ambari UI to install Ranger. During the installation, we should be > able to change the directories for ranger-usersync log and pid locations. But > changing the location for pid doesn't work since the location for pid is > hard-coded in the ranger-usersync-services.sh file. Can we make the location > for pid file configurable just like usersync_log_dir? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RANGER-1332) Ranger TLP : Source Code / Script changes
Selvamohan Neethiraj created RANGER-1332: Summary: Ranger TLP : Source Code / Script changes Key: RANGER-1332 URL: https://issues.apache.org/jira/browse/RANGER-1332 Project: Ranger Issue Type: Task Components: documentation Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj As part of the Ranger TLP, bunch of source/script needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (RANGER-1332) Ranger TLP : Source Code / Script changes
[ https://issues.apache.org/jira/browse/RANGER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1332: - Attachment: 0001-RANGER-1332-updated-docs-and-scripts-for-removal-of-.patch > Ranger TLP : Source Code / Script changes > - > > Key: RANGER-1332 > URL: https://issues.apache.org/jira/browse/RANGER-1332 > Project: Ranger > Issue Type: Task > Components: documentation > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj > Attachments: > 0001-RANGER-1332-updated-docs-and-scripts-for-removal-of-.patch > > > As part of the Ranger TLP, bunch of source/script needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (RANGER-1332) Ranger TLP : Source Code / Script changes
[ https://issues.apache.org/jira/browse/RANGER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-1332. -- Resolution: Fixed Changes are committed - 28d2ed14d71185103168d407c5c2efb944fb44f0 docs are published to - http://ranger.apache.org/ > Ranger TLP : Source Code / Script changes > - > > Key: RANGER-1332 > URL: https://issues.apache.org/jira/browse/RANGER-1332 > Project: Ranger > Issue Type: Task > Components: documentation > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj > Attachments: > 0001-RANGER-1332-updated-docs-and-scripts-for-removal-of-.patch > > > As part of the Ranger TLP, bunch of source/script needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (RANGER-1346) Policies are matched against wildcard path for location
[ https://issues.apache.org/jira/browse/RANGER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj deleted RANGER-1346: - > Policies are matched against wildcard path for location > --- > > Key: RANGER-1346 > URL: https://issues.apache.org/jira/browse/RANGER-1346 > Project: Ranger > Issue Type: Bug >Reporter: Krzysztof Adamski > Labels: security > > A policy in Ranger is being picked up based on the destination path. All the > destination paths that match the substring are being picked up. This is > undesired and it breaks the security concept. > e.g. for the path > /test1234 > a policy for path > /test > will be used. > See details in attachments. > No additional permission on hdfs to exclude fallback. > Tested on Ranger 0.6.0.2.5 HDP 2.5. > hdfs dfs –ls / | grep test > d- - hdfs hdfs0 2017-02-02 14:17 /test > d- - hdfs hdfs0 2017-02-02 14:18 /test1234 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1148) Ranger needs to map Storm ACL- debug, setLogConfig , getLogConfig to getTopologyInfo
[ https://issues.apache.org/jira/browse/RANGER-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1148: - Affects Version/s: (was: 1.0.0) 0.7.0 > Ranger needs to map Storm ACL- debug, setLogConfig , getLogConfig to > getTopologyInfo > - > > Key: RANGER-1148 > URL: https://issues.apache.org/jira/browse/RANGER-1148 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani > Fix For: 0.7.0 > > Attachments: RANGER-1148.patch > > > Ranger needs to map Storm ACL- "debug" "setLogConfig" , "getLogConfig" to > getTopologyInfo to handle authorization of these operation correctly -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1262) Setting up database on MacOS is not working
[ https://issues.apache.org/jira/browse/RANGER-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1262: - Affects Version/s: (was: 1.0.0) 0.7.0 > Setting up database on MacOS is not working > --- > > Key: RANGER-1262 > URL: https://issues.apache.org/jira/browse/RANGER-1262 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 0.7.0 >Reporter: Zsombor Gegesy >Priority: Minor > Labels: patch > Fix For: 0.7.0 > > Attachments: > 0001-Make-the-db-setup-scripts-compatible-with-MacOS.patch > > > Currently it's pretty hard to setup the dev environment, for example the > scripts which are creating and updating the db schema have a lot's of linux > and windows specific steps, which is not executed on MacOS (or any other OS), > as MacOS is very similar to Linux, most of the Linux steps could work well on > Mac. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1139) Ranger Kafka Plugin should include commons-codec jar as a dependency
[ https://issues.apache.org/jira/browse/RANGER-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1139: - Affects Version/s: (was: 1.0.0) 0.7.0 > Ranger Kafka Plugin should include commons-codec jar as a dependency > > > Key: RANGER-1139 > URL: https://issues.apache.org/jira/browse/RANGER-1139 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani > Fix For: 0.7.0 > > Attachments: RANGER-1139.patch > > > Ranger Kafka Plugin should include commons-codec jar as a dependency -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1364) MySQLPLRunner take wrong start index when traverse the resultSet metadata
[ https://issues.apache.org/jira/browse/RANGER-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1364: - Affects Version/s: (was: 1.0.0) 0.7.0 > MySQLPLRunner take wrong start index when traverse the resultSet metadata > - > > Key: RANGER-1364 > URL: https://issues.apache.org/jira/browse/RANGER-1364 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: zhangxiong > Fix For: 0.7.0 > > Attachments: > 0001-change-mysql-ResultSetMetaData-traverse-index-from-0.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > when we install the admin,the dba_script.py would call MySQLRunner to run > some sqls from file or input string.But MySQLRunner take wrong start index > when traverse then resultSet colname.According to jdbc specification,we > should get the rs first column name with index 1 NOT 0. But take 0 as start > index is what ranger does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1186) Ranger Source: eclipse
[ https://issues.apache.org/jira/browse/RANGER-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1186: - Affects Version/s: (was: 1.0.0) 0.7.0 > Ranger Source: eclipse > -- > > Key: RANGER-1186 > URL: https://issues.apache.org/jira/browse/RANGER-1186 > Project: Ranger > Issue Type: Bug > Components: documentation >Affects Versions: 0.7.0 > Environment: eclipse neon, ubuntu 16.10 >Reporter: Nigel Jones >Assignee: Pradeep Agrawal > Attachments: RANGER-1186_Ranger_Source_Eclipse.pdf, ranger_me0.PNG, > ranger_me1.PNG > > > I can happily build ranger in my Ubuntu 16.10 environment with > - open jdk 1.8.0_102 > - maven 3.3.9 > I also have eclipse neon installed in this environment > The build/setup instructions at > http://ranger.apache.org/quick_start_guide.html have minimal instructions for > eclipse. > I imported the top level ranger directory using the m2e plugin as provided in > neon. > This failed with numerous errors > Is anyone actively building with eclipse? If so can we update the website > with current setup information? > If not I'll use this JIRA to record the issues & hope to address them & > update the docs ;-) > Screenshots to follow -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1381) Add hadoop-common.jar as dependency to ranger-hive-utils package to avoid build failure
[ https://issues.apache.org/jira/browse/RANGER-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864431#comment-15864431 ] Selvamohan Neethiraj commented on RANGER-1381: -- +1 on the patch ... commited to master branch : 24b411016e879349d557be999cec703c92b601bc commited to ranger-0.7 branch : 59c5c9e856ddaf59dee9a2227b438375359ea650 > Add hadoop-common.jar as dependency to ranger-hive-utils package to avoid > build failure > > > Key: RANGER-1381 > URL: https://issues.apache.org/jira/browse/RANGER-1381 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 0.7.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani > Fix For: 0.7.0 > > > Add hadoop-common.jar as dependency to ranger-hive-utils package to avoid > build failure -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1381) Add hadoop-common.jar as dependency to ranger-hive-utils package to avoid build failure
[ https://issues.apache.org/jira/browse/RANGER-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1381: - Fix Version/s: 1.0.0 > Add hadoop-common.jar as dependency to ranger-hive-utils package to avoid > build failure > > > Key: RANGER-1381 > URL: https://issues.apache.org/jira/browse/RANGER-1381 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 0.7.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani > Fix For: 0.7.0, 1.0.0 > > > Add hadoop-common.jar as dependency to ranger-hive-utils package to avoid > build failure -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1394) Ranger Release of 0.7.0
Selvamohan Neethiraj created RANGER-1394: Summary: Ranger Release of 0.7.0 Key: RANGER-1394 URL: https://issues.apache.org/jira/browse/RANGER-1394 Project: Ranger Issue Type: Task Components: Ranger Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix For: 0.7.0 Track all Release related activities -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1394) Ranger Release of 0.7.0
[ https://issues.apache.org/jira/browse/RANGER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1394: - Priority: Blocker (was: Major) > Ranger Release of 0.7.0 > --- > > Key: RANGER-1394 > URL: https://issues.apache.org/jira/browse/RANGER-1394 > Project: Ranger > Issue Type: Task > Components: Ranger > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Blocker > Fix For: 0.7.0 > > > Track all Release related activities -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1347) The AtlasClient should fall back to the plain password if the password decryption fails
[ https://issues.apache.org/jira/browse/RANGER-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874080#comment-15874080 ] Selvamohan Neethiraj commented on RANGER-1347: -- +1 for the patch committed to ranger-0.7 branch 5eb030ada419c4b1aaff4474ac98b6680667efb0 > The AtlasClient should fall back to the plain password if the password > decryption fails > --- > > Key: RANGER-1347 > URL: https://issues.apache.org/jira/browse/RANGER-1347 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 0.7.0 > > Attachments: > 0001-RANGER-1347-The-AtlasClient-should-fall-back-to-the-.patch > > > The AtlasClient should fall back to the plain password if the password > decryption fails. Otherwise trying to Test the Connection when creating a new > service fails for me. The KnoxClient also follows this approach. > Review request: https://reviews.apache.org/r/56280/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1391) Error occurred when use EndDate as Search Filter in Audit Access WebPage
[
https://issues.apache.org/jira/browse/RANGER-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-1391:
-
Fix Version/s: 0.7.0
> Error occurred when use EndDate as Search Filter in Audit Access WebPage
>
>
> Key: RANGER-1391
> URL: https://issues.apache.org/jira/browse/RANGER-1391
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Labels: patch
> Fix For: 0.7.0
>
> Attachments:
> 0001-RANGER-1391-Error-occurred-when-use-EndDate-as-Searc.patch,
> solrEndDateError.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> RangerAdmin use solr to store audit data,
> then open the WebPage Audit Access of RangerAdmin,
> and use only EndDate as Search Filter without StartDate,
> there is error occurred with message "Unable to connect to Audit store!!",
> please refer screenshot
> [solrEndDateError.png|https://issues.apache.org/jira/secure/attachment/12853228/solrEndDateError.png]
> for more detail,
> check ranger_admin.log to find error log:
> {noformat}
> 2017-02-17 06:28:36,113 [http-bio-6080-exec-5] ERROR
> org.apache.ranger.solr.SolrUtil (SolrUtil.java:159) - Error running query.
> query=q=*:*&fq=null:[*+TO+2017-02-17T15:59:59Z]&sort=evtTime+desc&start=0&rows=25,
> response=null
> 2017-02-17 06:28:36,113 [http-bio-6080-exec-5] INFO
> org.apache.ranger.common.RESTErrorUtil (RESTErrorUtil.java:63) - Request
> failed. loginId=admin, logMessage=Error running query
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1391) Error occurred when use EndDate as Search Filter in Audit Access WebPage
[
https://issues.apache.org/jira/browse/RANGER-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874083#comment-15874083
]
Selvamohan Neethiraj commented on RANGER-1391:
--
+1 for the patch
Patch committed - 06005ca39b12bde4042804bf538ab855507c983f
> Error occurred when use EndDate as Search Filter in Audit Access WebPage
>
>
> Key: RANGER-1391
> URL: https://issues.apache.org/jira/browse/RANGER-1391
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Labels: patch
> Fix For: 0.7.0
>
> Attachments:
> 0001-RANGER-1391-Error-occurred-when-use-EndDate-as-Searc.patch,
> solrEndDateError.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> RangerAdmin use solr to store audit data,
> then open the WebPage Audit Access of RangerAdmin,
> and use only EndDate as Search Filter without StartDate,
> there is error occurred with message "Unable to connect to Audit store!!",
> please refer screenshot
> [solrEndDateError.png|https://issues.apache.org/jira/secure/attachment/12853228/solrEndDateError.png]
> for more detail,
> check ranger_admin.log to find error log:
> {noformat}
> 2017-02-17 06:28:36,113 [http-bio-6080-exec-5] ERROR
> org.apache.ranger.solr.SolrUtil (SolrUtil.java:159) - Error running query.
> query=q=*:*&fq=null:[*+TO+2017-02-17T15:59:59Z]&sort=evtTime+desc&start=0&rows=25,
> response=null
> 2017-02-17 06:28:36,113 [http-bio-6080-exec-5] INFO
> org.apache.ranger.common.RESTErrorUtil (RESTErrorUtil.java:63) - Request
> failed. loginId=admin, logMessage=Error running query
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1392) Hive test connection is failing even if jdbc.url configured is correct in Ranger 0.7.0
[ https://issues.apache.org/jira/browse/RANGER-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1392: - Fix Version/s: (was: 0.7.0) 1.0.0 > Hive test connection is failing even if jdbc.url configured is correct in > Ranger 0.7.0 > -- > > Key: RANGER-1392 > URL: https://issues.apache.org/jira/browse/RANGER-1392 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Deepak Sharma >Assignee: Sailaja Polavarapu > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1392-Hive-test-connection-is-failing-even-if-.patch > > > even if jdbc.url is correct then also ranger hive test connection is failing. > jdbc.url is configured to > jdbc:hive2://ctr-e127-1486658464320-1453-01-04.hwx.site:2181,ctr-e127-1486658464320-1453-01-03.hwx.site:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2;principal=hive/_h...@example.com;transportMode=http;httpPath=cliservice;ssl=true;sslTrustStore=/etc/security/serverKeys/hivetruststore.jks;trustStorePassword=changeit > but during test connection it gives error: > org.apache.ranger.plugin.client.HadoopException: Unable to connect to Hive > Thrift Server instance.. > Unable to connect to Hive Thrift Server instance.. > Could not establish connection to > jdbc:hive2://ctr-e127-1486658464320-1453-01-04.hwx.site:10001/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2;principal=hive/_h...@example.com;transportMode=http;httpPath=cliservice;ssl=true;sslTrustStore=/etc/security/serverKeys/hivetruststore.jks;trustStorePassword=changeit: > org.apache.hive.org.apache.http.client.ClientProtocolException. > org.apache.hive.org.apache.http.client.ClientProtocolException. > java.lang.RuntimeException: class > org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not > org.apache.hive.org.apache.hadoop.security.GroupMappingServiceProvider. > class org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not > org.apache.hive.org.apache.hadoop.security.GroupMappingServiceProvider. > problem is during test connection hiveserver2 url is used > dbc:hive2://ctr-e127-1486658464320-1453-01-04.hwx.site:10001/; and > servicediscovery mode is zookeeper, > tried to connect manually to this url , it failed due to same error, but when > remove zookeeper service discovery parameter then i was able to connect using > beeline. > so it seems somewhere this url is being modified. > This happens in non WE clusters as well. Though the error is somewhat > different: > 2017-02-16 00:24:23,432 [timed-executor-pool-0] INFO > org.apache.ranger.plugin.client.BaseClient (BaseClient.java:125) - Init > Lookup Login: security enabled, using lookupPrincipal/lookupKeytab > 2017-02-16 00:24:23,436 [timed-executor-pool-0] INFO > apache.ranger.services.hive.client.HiveClient (HiveClient.java:67) - Secured > Mode: JDBC Connection done with preAuthenticated Subject > 2017-02-16 00:24:23,481 [timed-executor-pool-0] ERROR > apache.ranger.services.hive.client.HiveClient (HiveClient.java:433) - Unable > to Connect to Hive > org.apache.ranger.plugin.client.HadoopException: Unable to connect to Hive > Thrift Server instance > at > org.apache.ranger.services.hive.client.HiveClient.initConnection(HiveClient.java:549) > As per [~rmani]: > Issue being this class > org.apache.hive.org.apache.hadoop.security.GroupMappingServiceProvider from > hive-jdbc-1.2.1000.2.6.0.0-*-standalone.jar is getting loaded by ranger > class-loader where as > org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback is loaded by > Tomcat class-loader. > One way to fix is to pack hive-jdbc-1.2.1000.2.6.0.0-*-standalone.jar in > /usr/hdp/2.6.0.0-*/ranger-admin/ews/webapp/WEB-INF/lib so the type issue will > be resolved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1326) Fix remaining licensing issues
[ https://issues.apache.org/jira/browse/RANGER-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1326: - Fix Version/s: (was: 0.7.0) 1.0.0 > Fix remaining licensing issues > -- > > Key: RANGER-1326 > URL: https://issues.apache.org/jira/browse/RANGER-1326 > Project: Ranger > Issue Type: Bug >Affects Versions: 0.6.2 >Reporter: Colm O hEigeartaigh > Fix For: 1.0.0 > > > We need to fix the remaining licensing issues as raised by Jusin: > For items not fixed please see [1][2][3]. > Also note that with json2.js license it seems a little unclear to me and may > be under the JSON license. It does have “public domain” in the code so it may > be OK, it still however needs to be added to LICENSE. Just be careful as the > JSON license no longer allowed in Apache software and it is considered > category X. [4] In this case you do have a few months grace to remove this > [5] but you need to call it out in NOTICE and it still needs to be removed by > end of April. [5] > 1. > https://lists.apache.org/thread.html/6949e2f048b07478c861a675ad8e98d750e0f786b272a6afc69df78e@%3Cgeneral.incubator.apache.org%3E > 2. > https://lists.apache.org/thread.html/9552c63b71a38ed75cd252463e788408aa4a9a05abeba36168df5a12@%3Cgeneral.incubator.apache.org%3E > 3. > https://lists.apache.org/thread.html/de169a09f7527fbc3549518f0227ba40ee8524c6e60ba8105d82479b@%3Cgeneral.incubator.apache.org%3E > 4. https://www.apache.org/legal/resolved#category-x > 5. > https://lists.apache.org/thread.html/bb18f942ce7eb83c11438303c818b885810fb76385979490366720d5@%3Clegal-discuss.apache.org%3E -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1252) Policy lookup does not honor the case sensitivity flag of resources
[ https://issues.apache.org/jira/browse/RANGER-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1252: - Fix Version/s: (was: 0.7.0) 1.0.0 > Policy lookup does not honor the case sensitivity flag of resources > --- > > Key: RANGER-1252 > URL: https://issues.apache.org/jira/browse/RANGER-1252 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.6.2 >Reporter: Yan > Fix For: 1.0.0 > > Attachments: Ranger-1252.patch > > > For case insensitive Hive db/table names, the public API's policy lookup does > not hit the case insensitive names. For instance, the following curl command: > curl -iv -u admin:admin -H "Content-type:application/json" -X GET > http://11.22.33.444:6080/service/public/api/policy?databases=db1&tables=table1 > returns different results from running the following command using different > cases in names: > curl -iv -u admin:admin -H "Content-type:application/json" -X GET > http://11.22.33.444:6080/service/public/api/policy?databases=DB1&tables=TABLE1 > if there exists such a Hive table db1/table1 in the metastore. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1348) Atlas Autocompletion not working properly
[ https://issues.apache.org/jira/browse/RANGER-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1348: - Fix Version/s: (was: 0.7.0) 1.0.0 > Atlas Autocompletion not working properly > - > > Key: RANGER-1348 > URL: https://issues.apache.org/jira/browse/RANGER-1348 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Colm O hEigeartaigh >Assignee: Qiang Zhang > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1348-Atlas-Autocompletion-not-working-properl-2.patch, > 0001-RANGER-1348-Atlas-Autocompletion-not-working-properl.patch, > ranger-atlas.png, test1.png > > > The autocompletion feature available in the Admin Service when selecting an > Atlas type (for example) does not work properly. If you start typing you can > see that all of the results retrieved from Atlas are available to be selected > (see the screenshot below). It looks like the results from Atlas are not > parsed properly (tested with 0.8.0 SNAPSHOT version of Atlas for the record) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1364) MySQLPLRunner take wrong start index when traverse the resultSet metadata
[ https://issues.apache.org/jira/browse/RANGER-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1364: - Fix Version/s: (was: 0.7.0) 1.0.0 > MySQLPLRunner take wrong start index when traverse the resultSet metadata > - > > Key: RANGER-1364 > URL: https://issues.apache.org/jira/browse/RANGER-1364 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: zhangxiong > Fix For: 1.0.0 > > Attachments: > 0001-change-mysql-ResultSetMetaData-traverse-index-from-0.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > when we install the admin,the dba_script.py would call MySQLRunner to run > some sqls from file or input string.But MySQLRunner take wrong start index > when traverse then resultSet colname.According to jdbc specification,we > should get the rs first column name with index 1 NOT 0. But take 0 as start > index is what ranger does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1354) Error on Atlas plugin install
[ https://issues.apache.org/jira/browse/RANGER-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1354: - Fix Version/s: (was: 0.7.0) 1.0.0 > Error on Atlas plugin install > - > > Key: RANGER-1354 > URL: https://issues.apache.org/jira/browse/RANGER-1354 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1354-Error-on-Atlas-plugin-install.patch > > > When installing the Atlas plugin, it throws an error if the Apache Atlas > distribution does not have a "libext" directory. As it doesn't by default, > this can be a bit confusing to the user. The script should be updated to > create the "libext" directory in the Atlas distribution if it doesn't already > exist. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1383) Support for using resource-matcher for filtering policies within a service if service-resource is provided in the filter
[ https://issues.apache.org/jira/browse/RANGER-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1383: - Fix Version/s: (was: 0.7.0) 1.0.0 > Support for using resource-matcher for filtering policies within a service if > service-resource is provided in the filter > > > Key: RANGER-1383 > URL: https://issues.apache.org/jira/browse/RANGER-1383 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Deepak Sharma >Assignee: Abhay Kulkarni > Fix For: 1.0.0 > > > Ranger admin's REST API support retrieving and filtering policies for > resource specified in the provided filter. Currently, a simple string-match > and wildcard-match is used to filter policies. It is desirable to provide an > option to use, for filtering purpose, the same resource-matching algorithm > that is used by the policy engine to search policies that need to be > evaluated for access determination in the component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1394) Ranger Release of 0.7.0
[ https://issues.apache.org/jira/browse/RANGER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-1394. -- Resolution: Fixed Completed Release 0.7.0 > Ranger Release of 0.7.0 > --- > > Key: RANGER-1394 > URL: https://issues.apache.org/jira/browse/RANGER-1394 > Project: Ranger > Issue Type: Task > Components: Ranger > Reporter: Selvamohan Neethiraj > Assignee: Selvamohan Neethiraj >Priority: Blocker > Fix For: 0.7.0 > > > Track all Release related activities -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1401) Add consolidated db schema script for SQLServer DB flavor
[ https://issues.apache.org/jira/browse/RANGER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1401: - Fix Version/s: (was: 0.7.0) 0.7.1 > Add consolidated db schema script for SQLServer DB flavor > - > > Key: RANGER-1401 > URL: https://issues.apache.org/jira/browse/RANGER-1401 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1401-2.patch > > > A consolidated db schema script for SQLServer DB flavor would be required as > execution of db patches and java patches takes lot of time. Before > installing Ranger User can separately run this script to reduce db setup and > installation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1409) User role get deleted from table when he tries to update his role to a restricted role
[ https://issues.apache.org/jira/browse/RANGER-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1409: - Fix Version/s: (was: 0.7.0) 0.7.1 > User role get deleted from table when he tries to update his role to a > restricted role > -- > > Key: RANGER-1409 > URL: https://issues.apache.org/jira/browse/RANGER-1409 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.5.0, 0.6.0, 0.7.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1409-1.patch > > > *Problem Statement :* User role get deleted from x_portal_user_role table and > login does not work when he tries to update his role to a restricted role for > his profile by using Post method of API /service/users/ . > User having role 'ROLE_SYS_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_KEY_ADMIN' can change his role to 'ROLE_USER' > User having role 'ROLE_USER' should not able to change his role to any other > role. > *Proposed solution :* User's new requested role should be validated and if > requested role is invalid then server should return error message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1407) Service update transaction log is not generated in some cases
[ https://issues.apache.org/jira/browse/RANGER-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1407: - Fix Version/s: (was: 0.7.0) 0.7.1 > Service update transaction log is not generated in some cases > - > > Key: RANGER-1407 > URL: https://issues.apache.org/jira/browse/RANGER-1407 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Pradeep Agrawal > Fix For: 0.7.1 > > Attachments: RANGER-1407-1.patch > > > If a Ranger service is updated to change its associated tag service name, > then the service-update transaction log is not generated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1398) Missing the settings for 'ranger.usersync.unix.minGroupId' in ranger usersync module
[ https://issues.apache.org/jira/browse/RANGER-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1398: - Fix Version/s: (was: 0.7.0) 0.7.1 > Missing the settings for 'ranger.usersync.unix.minGroupId' in ranger usersync > module > > > Key: RANGER-1398 > URL: https://issues.apache.org/jira/browse/RANGER-1398 > Project: Ranger > Issue Type: Bug > Components: usersync >Affects Versions: 0.7.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang > Fix For: 0.7.1 > > Attachments: > 0001-RANGER-1398-Missing-the-settings-for-ranger.usersync.patch > > > I checked the codes and found we will get 'minimumGroupId' from > ranger-ugsync-site.xml, but I can't find this parameter in this file after > execute the shell script. > The reason why I set the value for 'ranger.usersync.unix.minGroupId' as 500: > The value must be non-negative. The default is to use the smallest ID value > greater than 500 and greater than every other group. Values between 0 and 499 > are typically reserved for system accounts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1413) Good coding practice in Ranger recommended by static code analysis
[ https://issues.apache.org/jira/browse/RANGER-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-1413: - Fix Version/s: (was: 0.7.0) 0.7.1 > Good coding practice in Ranger recommended by static code analysis > -- > > Key: RANGER-1413 > URL: https://issues.apache.org/jira/browse/RANGER-1413 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Minor > Fix For: 0.7.1 > > > Fix potential run-time issues identified by static code analysis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
