[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] [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=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] [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] [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] [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=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] [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-4214) Build broken on JDK11 -
[
https://issues.apache.org/jira/browse/RANGER-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Commented] (RANGER-4214) Build broken on JDK11 -
[
https://issues.apache.org/jira/browse/RANGER-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [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] [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] [Updated] (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 updated RANGER-4142: - Attachment: 0001-RANGER-4142-added-docs-update-for-2.4.0-release-in-r.patch > 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] [Updated] (RANGER-4198) [BUILD] [JDK11] - failed - ranger-master-snapshot-publish : Unix Native Authenticator #773' does not have a result yet.
[ https://issues.apache.org/jira/browse/RANGER-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4198: - Attachment: 0001-RANGER-4198-fixed-build-issue.patch > [BUILD] [JDK11] - failed - ranger-master-snapshot-publish : Unix Native > Authenticator #773' does not have a result yet. > --- > > Key: RANGER-4198 > URL: https://issues.apache.org/jira/browse/RANGER-4198 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Affects Versions: 3.0.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: 0001-RANGER-4198-fixed-build-issue.patch > > > See error at > https://ci-builds.apache.org/user/sneethir/my-views/view/RangerView/job/Ranger/job/ranger-master-snapshot-publish/773/console -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4198) [BUILD] [JDK11] - failed - ranger-master-snapshot-publish : Unix Native Authenticator #773' does not have a result yet.
[ https://issues.apache.org/jira/browse/RANGER-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-4198: Assignee: Selvamohan Neethiraj > [BUILD] [JDK11] - failed - ranger-master-snapshot-publish : Unix Native > Authenticator #773' does not have a result yet. > --- > > Key: RANGER-4198 > URL: https://issues.apache.org/jira/browse/RANGER-4198 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Affects Versions: 3.0.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > > See error at > https://ci-builds.apache.org/user/sneethir/my-views/view/RangerView/job/Ranger/job/ranger-master-snapshot-publish/773/console -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4198) [BUILD] [JDK11] - failed - ranger-master-snapshot-publish : Unix Native Authenticator #773' does not have a result yet.
Selvamohan Neethiraj created RANGER-4198: Summary: [BUILD] [JDK11] - failed - ranger-master-snapshot-publish : Unix Native Authenticator #773' does not have a result yet. Key: RANGER-4198 URL: https://issues.apache.org/jira/browse/RANGER-4198 Project: Ranger Issue Type: Improvement Components: build-infra Affects Versions: 3.0.0 Reporter: Selvamohan Neethiraj See error at https://ci-builds.apache.org/user/sneethir/my-views/view/RangerView/job/Ranger/job/ranger-master-snapshot-publish/773/console -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4139) DOC SITE: ranger.apache.org - revamp site's look and feel
[ https://issues.apache.org/jira/browse/RANGER-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4139: - Attachment: 0001-RANGER-4139-Updated-changes-with-both-patches.patch > DOC SITE: ranger.apache.org - revamp site's look and feel > -- > > Key: RANGER-4139 > URL: https://issues.apache.org/jira/browse/RANGER-4139 > Project: Ranger > Issue Type: Improvement > Components: documentation >Affects Versions: 3.0.0, 2.4.0 >Reporter: Selvamohan Neethiraj >Assignee: Stalin Nadar >Priority: Major > Attachments: 0001-RANGER-4139-Updated-changes-with-both-patches.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4167) Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch)
[ https://issues.apache.org/jira/browse/RANGER-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707741#comment-17707741 ] Selvamohan Neethiraj commented on RANGER-4167: -- Commit : 06fc1ef09220cf82096a990a072ff18dbb148151 - Done after review approved. > Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch) > - > > Key: RANGER-4167 > URL: https://issues.apache.org/jira/browse/RANGER-4167 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 3.0.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4167-fixes-to-kafka-test-suite-issues.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4159) Ranger audit metrics deletion is failing
[ https://issues.apache.org/jira/browse/RANGER-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707594#comment-17707594 ] Selvamohan Neethiraj commented on RANGER-4159: -- [~dineshkumar-yadav] - Can you please add little more context and screenshot of errors for us to better understand and work on the fix? > Ranger audit metrics deletion is failing > > > Key: RANGER-4159 > URL: https://issues.apache.org/jira/browse/RANGER-4159 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dineshkumar Yadav >Priority: Major > > Ranger audit metrics deletion is failing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4167) Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch)
[ https://issues.apache.org/jira/browse/RANGER-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4167: - Attachment: 0001-RANGER-4167-fixes-to-kafka-test-suite-issues.patch > Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch) > - > > Key: RANGER-4167 > URL: https://issues.apache.org/jira/browse/RANGER-4167 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.4.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4167-fixes-to-kafka-test-suite-issues.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4167) Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch)
[ https://issues.apache.org/jira/browse/RANGER-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4167: - Attachment: (was: 0001-RANGER-4144-fixed-kafka-plugin-test-suite-issues.patch) > Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch) > - > > Key: RANGER-4167 > URL: https://issues.apache.org/jira/browse/RANGER-4167 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.4.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4167) Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch)
[ https://issues.apache.org/jira/browse/RANGER-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4167: - Fix Version/s: 3.0.0 (was: 2.4.0) > Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch) > - > > Key: RANGER-4167 > URL: https://issues.apache.org/jira/browse/RANGER-4167 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.4.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4144-fixed-kafka-plugin-test-suite-issues.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4167) Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch)
Selvamohan Neethiraj created RANGER-4167: Summary: Kafka Test Suite Issues (RANGER-4144 on 3.0.0 branch) Key: RANGER-4167 URL: https://issues.apache.org/jira/browse/RANGER-4167 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 2.4.0 Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix For: 2.4.0 Attachments: 0001-RANGER-4144-fixed-kafka-plugin-test-suite-issues.patch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (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 resolved RANGER-707. - Resolution: Done > 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 (v8.20.10#820010)
[jira] [Resolved] (RANGER-4162) Create a separate GIT REPO (ranger-site.git) for Ranger Website Content
[ https://issues.apache.org/jira/browse/RANGER-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-4162. -- Resolution: Fixed > Create a separate GIT REPO (ranger-site.git) for Ranger Website Content > --- > > Key: RANGER-4162 > URL: https://issues.apache.org/jira/browse/RANGER-4162 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4162) Create a separate GIT REPO (ranger-site.git) for Ranger Website Content
[ https://issues.apache.org/jira/browse/RANGER-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707242#comment-17707242 ] Selvamohan Neethiraj commented on RANGER-4162: -- created the site - [https://github.com/apache/ranger-site]. using [https://selfserve.apache.org/] > Create a separate GIT REPO (ranger-site.git) for Ranger Website Content > --- > > Key: RANGER-4162 > URL: https://issues.apache.org/jira/browse/RANGER-4162 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4162) Create a separate GIT REPO (ranger-site.git) for Ranger Website Content
[ https://issues.apache.org/jira/browse/RANGER-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-4162: Assignee: Selvamohan Neethiraj > Create a separate GIT REPO (ranger-site.git) for Ranger Website Content > --- > > Key: RANGER-4162 > URL: https://issues.apache.org/jira/browse/RANGER-4162 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4162) Create a separate GIT REPO (ranger-site.git) for Ranger Website Content
Selvamohan Neethiraj created RANGER-4162: Summary: Create a separate GIT REPO (ranger-site.git) for Ranger Website Content Key: RANGER-4162 URL: https://issues.apache.org/jira/browse/RANGER-4162 Project: Ranger Issue Type: Improvement Components: documentation Reporter: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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=17707160#comment-17707160 ] Selvamohan Neethiraj commented on RANGER-4142: -- 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 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3894) Application is 'unknown' for metastore in plugin status page
[ https://issues.apache.org/jira/browse/RANGER-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3894: - Fix Version/s: (was: 2.4.0) > Application is 'unknown' for metastore in plugin status page > > > Key: RANGER-3894 > URL: https://issues.apache.org/jira/browse/RANGER-3894 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Sercan Tekin >Priority: Minor > Fix For: 3.0.0 > > Attachments: metastore.png, unknown.png > > > After https://issues.apache.org/jira/browse/RANGER-768 I have configured hive > plugin for metastore. In plugin status page, application column shows > 'unknown' for metastore as in screen shot; > !unknown.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3996) Upgrade commons-configuration2 to version 2.8.0
[ https://issues.apache.org/jira/browse/RANGER-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3996: - Fix Version/s: (was: 2.4.0) > Upgrade commons-configuration2 to version 2.8.0 > --- > > Key: RANGER-3996 > URL: https://issues.apache.org/jira/browse/RANGER-3996 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-3996.patch > > > Update commons-configurations2 version used in Ranger from 2.1.1 to 2.8.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4029) Ranger cannot build with HBase 2.5.x versions because preBalance coprocessor hook syntax changed in HBASE-26147
[
https://issues.apache.org/jira/browse/RANGER-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-4029:
-
Fix Version/s: (was: 2.4.0)
> Ranger cannot build with HBase 2.5.x versions because preBalance coprocessor
> hook syntax changed in HBASE-26147
> ---
>
> Key: RANGER-4029
> URL: https://issues.apache.org/jira/browse/RANGER-4029
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> [INFO] Compiling 3 source files to
> /workspace/bigtop/build/ranger/rpm/BUILD/ranger-2.1.0.3.2.2.3-1/ranger-hbase-plugin-shim/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /workspace/bigtop/build/ranger/rpm/BUILD/ranger-2.1.0.3.2.2.3-1/ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java:[281,1]
> error: method does not override or implement a method from a supertype
> [ERROR]
> /workspace/bigtop/build/ranger/rpm/BUILD/ranger-2.1.0.3.2.2.3-1/ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java:[289,21]
> error: method preBalance in interface MasterObserver cannot be applied to
> given types;
> [ERROR] required: ObserverContext,BalanceRequest
> found: ObserverContext
> reason: actual and formal argument lists differ in length
> /workspace/bigtop/build/ranger/rpm/BUILD/ranger-2.1.0.3.2.2.3-1/ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java:[2389,1]
> error: method does not override or implement a method from a supertype
> [ERROR]
> /workspace/bigtop/build/ranger/rpm/BUILD/ranger-2.1.0.3.2.2.3-1/ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java:[2397,21]
> error: method postBalance in interface MasterObserver cannot be applied to
> given types;
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4035) support for policies to refer access-types using category, like Create/Read/Update/Delete/Manage
[ https://issues.apache.org/jira/browse/RANGER-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4035: - Fix Version/s: (was: 2.4.0) > support for policies to refer access-types using category, like > Create/Read/Update/Delete/Manage > > > Key: RANGER-4035 > URL: https://issues.apache.org/jira/browse/RANGER-4035 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4035.patch > > > Ranger policy model supports setting up policies with fine-grained > permissions - like create/alter/drop/select/insert/update/truncate, > read/write/list/create/delete/mkdir. Supporting policies to specify > permissions as broad categories like CRUD, will make it easier for policy > authors - especially for tag-based policies. > In addition, it will also help to have a built-in access-type that captures > all other access-types - like ALL. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3664) Ranger KMS : Add refresh functionality on kms key listing page.
[ https://issues.apache.org/jira/browse/RANGER-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3664: - Fix Version/s: (was: 2.4.0) > Ranger KMS : Add refresh functionality on kms key listing page. > --- > > Key: RANGER-3664 > URL: https://issues.apache.org/jira/browse/RANGER-3664 > Project: Ranger > Issue Type: Improvement > Components: kms, Ranger >Reporter: Mateen N Mansoori >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0 > > > Add refresh functionality on kms key listing page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4044) Publish official docker images for ranger to dockerhub
[ https://issues.apache.org/jira/browse/RANGER-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4044: - Fix Version/s: (was: 2.4.0) > Publish official docker images for ranger to dockerhub > -- > > Key: RANGER-4044 > URL: https://issues.apache.org/jira/browse/RANGER-4044 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Priority: Major > Labels: Docker > Fix For: 3.0.0 > > > Similar to other apache products having official docker images on dockerhub > ([https://hub.docker.com/u/apache]), ranger can have its own image published > to the repository as well. > To begin with this can be just ranger-admin and its dependencies. > It'll be good to have one ranger image published to dockerhub with every > apache release. > CC: [~madhan] , [~vel], [~abhay] , [~rmani] , [~mehul] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4065) Fix README and PyPI Doc for Ranger Python Client
[ https://issues.apache.org/jira/browse/RANGER-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4065: - Fix Version/s: 3.0.0 (was: 2.4.0) > Fix README and PyPI Doc for Ranger Python Client > - > > Key: RANGER-4065 > URL: https://issues.apache.org/jira/browse/RANGER-4065 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.2.0, 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Minor > Fix For: 3.0.0 > > > Readme and PyPI doc for the ranger python client is out of sync. > The below lines need update in the README. > > to disable SSL certificate validation (not recommended for production use!) # > # ranger.session.verify = False > Affects PyPI version 0.0.6 and above: > [https://pypi.org/project/apache-ranger/0.0.6/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4122) [RangerAdmin] Reorganize authorization/access check logic
[
https://issues.apache.org/jira/browse/RANGER-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-4122:
-
Fix Version/s: 3.0.0
(was: 2.4.0)
> [RangerAdmin] Reorganize authorization/access check logic
> -
>
> Key: RANGER-4122
> URL: https://issues.apache.org/jira/browse/RANGER-4122
> Project: Ranger
> Issue Type: Improvement
> Components: admin
>Affects Versions: 2.3.0
>Reporter: KyrieG
>Assignee: KyrieG
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Pasted image 20230305134707 1.png,
> image-2023-03-05-22-16-17-927.png, image-2023-03-05-22-17-00-698.png,
> image-2023-03-05-22-17-35-210.png
>
>
> # Reorganize authorization logic
> Recently when I was sorting out the authorization logic of ranger admin, I
> saw confusion.
> For example: At ServiceREST I saw the following, similar logic been
> implemented in a distributed fasion.
> !image-2023-03-05-22-16-17-927.png!
> !image-2023-03-05-22-17-00-698.png!!image-2023-03-05-22-17-35-210.png!
> # I think these method should be in the same class for easy maintainance. A
> Better way is to create a new class for authorization logic instead of
> putting everythiong into bizUtil because it's responsible for many thing.
> # To sum up, I want to put these method into A new class named
> "RangerAuthorizationHelper".
> {quote}RangerBizUtil.isUserAllowed
> RangerBizUtil.checkAdminAccess
> RangerBizUtil.isUserRangerAdmin
> RangerBizUtil.isUserServiceAdmin
> RoleREST.userIsSrvAdmOrSrvUser
> svcStore.isServiceAdminUser
> XUserMgr.hasAccessToModule
> RangerBizUtil.hasModuleAccess
> RoleDBStore.ensureRoleAccess
> RangerBizUtil.blockAuditorRoleUser
> ... and many.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4064) RANGER-3348 introduces bug in python client for SSL enabled clusters
[
https://issues.apache.org/jira/browse/RANGER-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-4064:
-
Fix Version/s: 3.0.0
(was: 2.4.0)
> RANGER-3348 introduces bug in python client for SSL enabled clusters
>
>
> Key: RANGER-4064
> URL: https://issues.apache.org/jira/browse/RANGER-4064
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 3.0.0
>
>
> Bug was introduced in RANGER-3348 wherein using the python client on an SSL
> enabled cluster w/o host verification is no longer possible.
> ranger.session.verify = False # this was used to skip host verification
> earlier whereas in current code it is not possible to do so.
> >>> from apache_ranger.model.ranger_service import *
> >>> from apache_ranger.client.ranger_client import *
> >>> from apache_ranger.model.ranger_policy import *
> >>> ranger_url = 'someurl'
> >>> ranger_auth = ('admin', 'X')
> >>> from requests_kerberos import HTTPKerberosAuth
> >>> ranger_auth = HTTPKerberosAuth()
> >>> ranger = RangerClient(ranger_url, ranger_auth)
> >>> ranger.
> Display all 123 possibilities? (y or n)
> >>> ranger.session.verify = True
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'RangerClient' object has no attribute 'session'
> CC: [~kishor.gollapalliwar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3988) Trino plugin should differntiate between views and tables
[ https://issues.apache.org/jira/browse/RANGER-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3988: - Fix Version/s: 3.0.0 (was: 2.4.0) > Trino plugin should differntiate between views and tables > - > > Key: RANGER-3988 > URL: https://issues.apache.org/jira/browse/RANGER-3988 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger >Affects Versions: 2.3.0 >Reporter: Jonas Hartwig >Priority: Major > Fix For: 3.0.0 > > > The Trino plugin only "knows" tables. Views are validated against the same > rules "as" tables. Views and tables should be treated separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3973) LDAP incremental search not always available
[ https://issues.apache.org/jira/browse/RANGER-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3973: - Fix Version/s: 3.0.0 (was: 2.4.0) > LDAP incremental search not always available > > > Key: RANGER-3973 > URL: https://issues.apache.org/jira/browse/RANGER-3973 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.3.0 >Reporter: Jonas Hartwig >Priority: Blocker > Fix For: 3.0.0 > > > In certain situations the LDAP incremental user/groups search is not > available. There is a feature already to disable incremental loads. This is a > request to add a feature to disable using the delta fields for lookup. Our > LDAP does not have modifyTimestamp field. > When the flag ranger.usersync.ldap.deltasync is set ldap search should not > use properties > uSNChanged and modifyTimestamp (they are not needed). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3985) Trino plugin: Check table name when creating tables
[ https://issues.apache.org/jira/browse/RANGER-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-3985: - Fix Version/s: 3.0.0 (was: 2.4.0) > Trino plugin: Check table name when creating tables > --- > > Key: RANGER-3985 > URL: https://issues.apache.org/jira/browse/RANGER-3985 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.3.0 >Reporter: Jonas Hartwig >Priority: Major > Fix For: 3.0.0 > > > The ranger rules to create tables in Trino currently check schema level to > create. > If this is set, anyone can create any table/view. There is no way to limit > the naming of tables. > However e.g. drop, alter rights are granted on table level. So user might > create any table, but not remove them. > To allow a more strict implementation view/table creation should verify table > name as well. > In that case the previous behaviour can be created by adding a rule to allow > create on catalog/schema/*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4140) Release Apache Ranger 2.4.0
[ https://issues.apache.org/jira/browse/RANGER-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-4140. -- Resolution: Done > Release Apache Ranger 2.4.0 > --- > > Key: RANGER-4140 > URL: https://issues.apache.org/jira/browse/RANGER-4140 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.3.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 2.4.0 > > > Tracking 2.4.0 release tasks. -- 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: Done > 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 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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=17707122#comment-17707122 ] Selvamohan Neethiraj commented on RANGER-4142: -- Added new pages in Wikis: * [https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.4.0+-+Release+Notes] * [https://cwiki.apache.org/confluence/display/RANGER/2.4.0+release+-+Apache+Ranger] * Created a Git Tag 'release-ranger-*2.4*.0' on the source location where tag 'release-*2.4*.0-rc2' was. > 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 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (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 reassigned RANGER-4142: Assignee: Selvamohan Neethiraj > 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 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4161) Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/RANGER-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-4161. -- Resolution: Done > Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT > -- > > Key: RANGER-4161 > URL: https://issues.apache.org/jira/browse/RANGER-4161 > Project: Ranger > Issue Type: Sub-task > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4161) Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/RANGER-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707115#comment-17707115 ] Selvamohan Neethiraj commented on RANGER-4161: -- Changed via commit - 83d720a9c254b96aa9ba6219830449d8674c34b4 > Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT > -- > > Key: RANGER-4161 > URL: https://issues.apache.org/jira/browse/RANGER-4161 > Project: Ranger > Issue Type: Sub-task > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4161) Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT
Selvamohan Neethiraj created RANGER-4161: Summary: Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT Key: RANGER-4161 URL: https://issues.apache.org/jira/browse/RANGER-4161 Project: Ranger Issue Type: Sub-task Components: build-infra Reporter: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4161) Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/RANGER-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-4161: Assignee: Selvamohan Neethiraj > Update branch ranger-2.4 to produce 2.4.1-SNAPSHOT > -- > > Key: RANGER-4161 > URL: https://issues.apache.org/jira/browse/RANGER-4161 > Project: Ranger > Issue Type: Sub-task > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4143) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-4143. -- Resolution: Done Release artifacts published. > Publish release artifacts > - > > Key: RANGER-4143 > URL: https://issues.apache.org/jira/browse/RANGER-4143 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4143) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707109#comment-17707109 ] Selvamohan Neethiraj edited comment on RANGER-4143 at 3/31/23 4:41 AM: --- Published Apache 2.4.0 binaries based on the -[https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central] was (Author: sneethiraj): Working on publishing the binaries based on the -[https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central] > Publish release artifacts > - > > Key: RANGER-4143 > URL: https://issues.apache.org/jira/browse/RANGER-4143 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4143) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707109#comment-17707109 ] Selvamohan Neethiraj commented on RANGER-4143: -- Working on publishing the binaries based on the -[https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central] > Publish release artifacts > - > > Key: RANGER-4143 > URL: https://issues.apache.org/jira/browse/RANGER-4143 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4143) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707107#comment-17707107 ] Selvamohan Neethiraj commented on RANGER-4143: -- Committed the source artifacts & checksum artifacts from svn : [https://dist.apache.org/repos/dist/dev/range]r/2.4.0-rc2 to svn : [https://dist.apache.org/repos/dist/release/ranger]/2.4.0 > Publish release artifacts > - > > Key: RANGER-4143 > URL: https://issues.apache.org/jira/browse/RANGER-4143 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4143) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-4143: Assignee: Selvamohan Neethiraj > Publish release artifacts > - > > Key: RANGER-4143 > URL: https://issues.apache.org/jira/browse/RANGER-4143 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4139) DOC SITE: ranger.apache.org - revamp site's look and feel
[ https://issues.apache.org/jira/browse/RANGER-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-4139: Assignee: Stalin Nadar > DOC SITE: ranger.apache.org - revamp site's look and feel > -- > > Key: RANGER-4139 > URL: https://issues.apache.org/jira/browse/RANGER-4139 > Project: Ranger > Issue Type: Improvement > Components: documentation >Affects Versions: 3.0.0, 2.4.0 >Reporter: Selvamohan Neethiraj >Assignee: Stalin Nadar >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4141) Change pom version from 2.4.0-SNAPSHOT to 2.4.0
[ https://issues.apache.org/jira/browse/RANGER-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703479#comment-17703479 ] Selvamohan Neethiraj commented on RANGER-4141: -- Done - commit id - 9b25bc9f342e259cca2aa645324a2d4a1c6c9a71 > Change pom version from 2.4.0-SNAPSHOT to 2.4.0 > --- > > Key: RANGER-4141 > URL: https://issues.apache.org/jira/browse/RANGER-4141 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4141) Change pom version from 2.4.0-SNAPSHOT to 2.4.0
[ https://issues.apache.org/jira/browse/RANGER-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-4141. -- Assignee: Selvamohan Neethiraj Resolution: Done > Change pom version from 2.4.0-SNAPSHOT to 2.4.0 > --- > > Key: RANGER-4141 > URL: https://issues.apache.org/jira/browse/RANGER-4141 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4144) Fixed Kafka Test Suite Issues
[ https://issues.apache.org/jira/browse/RANGER-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4144: - Attachment: 0001-RANGER-4144-fixed-kafka-plugin-test-suite-issues.patch > Fixed Kafka Test Suite Issues > - > > Key: RANGER-4144 > URL: https://issues.apache.org/jira/browse/RANGER-4144 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.4.0 >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Critical > Fix For: 2.4.0 > > Attachments: > 0001-RANGER-4144-fixed-kafka-plugin-test-suite-issues.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4144) Fixed Kafka Test Suite Issues
Selvamohan Neethiraj created RANGER-4144: Summary: Fixed Kafka Test Suite Issues Key: RANGER-4144 URL: https://issues.apache.org/jira/browse/RANGER-4144 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 2.4.0 Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix For: 2.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4143) Publish release artifacts
Selvamohan Neethiraj created RANGER-4143: Summary: Publish release artifacts Key: RANGER-4143 URL: https://issues.apache.org/jira/browse/RANGER-4143 Project: Ranger Issue Type: Sub-task Components: Ranger Reporter: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4142) Update Apache Ranger website with 2.4.0
Selvamohan Neethiraj created RANGER-4142: Summary: 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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4141) Change pom version from 2.4.0-SNAPSHOT to 2.4.0
Selvamohan Neethiraj created RANGER-4141: Summary: Change pom version from 2.4.0-SNAPSHOT to 2.4.0 Key: RANGER-4141 URL: https://issues.apache.org/jira/browse/RANGER-4141 Project: Ranger Issue Type: Sub-task Components: Ranger Reporter: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4140) Release Apache Ranger 2.4.0
Selvamohan Neethiraj created RANGER-4140: Summary: Release Apache Ranger 2.4.0 Key: RANGER-4140 URL: https://issues.apache.org/jira/browse/RANGER-4140 Project: Ranger Issue Type: Task Components: Ranger Affects Versions: 2.3.0 Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix For: 2.4.0 Tracking 2.4.0 release tasks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4139) DOC SITE: ranger.apache.org - revamp site's look and feel
Selvamohan Neethiraj created RANGER-4139: Summary: DOC SITE: ranger.apache.org - revamp site's look and feel Key: RANGER-4139 URL: https://issues.apache.org/jira/browse/RANGER-4139 Project: Ranger Issue Type: Improvement Components: documentation Affects Versions: 3.0.0, 2.4.0 Reporter: Selvamohan Neethiraj -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-3896) Update Ozone dependency version to latest 1.3.0
[ https://issues.apache.org/jira/browse/RANGER-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj reassigned RANGER-3896: Assignee: Neil Joshi > Update Ozone dependency version to latest 1.3.0 > --- > > Key: RANGER-3896 > URL: https://issues.apache.org/jira/browse/RANGER-3896 > Project: Ranger > Issue Type: Bug > Components: plugins, Ranger >Reporter: Neil Joshi >Assignee: Neil Joshi >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > update Ozone dependency in pom build file from 1.0.0 to latest Ozone version > 1.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-3922) Ranger build has missing dependencies when calling credentialapi.buildks create
[
https://issues.apache.org/jira/browse/RANGER-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj reassigned RANGER-3922:
Assignee: Neil Joshi
> Ranger build has missing dependencies when calling credentialapi.buildks
> create
>
>
> Key: RANGER-3922
> URL: https://issues.apache.org/jira/browse/RANGER-3922
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Neil Joshi
>Assignee: Neil Joshi
>Priority: Major
>
> Ranger 2.3.0 has build issues with missing dependencies when calling:
> {code:java}
> org.apache.ranger.credentalapi.buildks create{code}
> missing -
> # org/apache/commons/lang3/StringUtils
> # org/apache/commons/compress/archivers/tar/TarArchiver
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17650089#comment-17650089 ] Selvamohan Neethiraj commented on RANGER-4017: -- Just FYI: had some trouble with Docker Volume Mapping (for .m2 folder) when tested with a older version of docker-compose (docker-compose version 1.29.2); Updated to version 2.14.2 of docker-compose and it seems to work fine. > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: patch-v4.diff > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17650074#comment-17650074 ] Selvamohan Neethiraj commented on RANGER-4017: -- Added the patch after approval from Apache Review Board Here are the commits : dbca7795c13290027b00c5d410fa6843ddbec172 855801506820d491b1fe33ecfb8b38f599579fc1 e8dd5f11a9527c9ab2b942a556e5eb6a68ed3069 aca732469afa1ef42338ff7fd3c83dcaacee3a3d > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: patch-v4.diff > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: patch-v4.diff > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: patch-v4.diff > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: (was: 0001-RANGER-4017-running-ranger-in-few-mins-using-docker.patch) > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: patch-v4.diff > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: (was: 0002-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch) > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: patch-v4.diff > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: 0002-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4017-running-ranger-in-few-mins-using-docker.patch, > 0002-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: (was: 0001-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch) > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4017-running-ranger-in-few-mins-using-docker.patch > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: 0001-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4017-added-to-run-ranger-kms-as-part-of-the-p.patch, > 0001-RANGER-4017-running-ranger-in-few-mins-using-docker.patch > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-1643) Handle multiple comma in credentials ...
[ https://issues.apache.org/jira/browse/RANGER-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647854#comment-17647854 ] Selvamohan Neethiraj commented on RANGER-1643: -- [~andrewsmith87] - What is pending on this fix? > Handle multiple comma in credentials ... > > > Key: RANGER-1643 > URL: https://issues.apache.org/jira/browse/RANGER-1643 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.3, 0.7.1 >Reporter: Selvamohan Neethiraj >Assignee: Endre Kovacs >Priority: Minor > Attachments: > 0001-RANGER-1644-RANGER-1643-using-stronger-crypto-algo-s.patch > > > Currently, PasswordUtils parses the encryption configuration based on the > presence of a comma character. The actual password itself may have comma > characters. We should fix this to allow the user with the password or we > should remove the code that handles the password without having encryption > configuration as part of the input string. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-254) Add support for UserSync and Authentication of Windows Platform
[ https://issues.apache.org/jira/browse/RANGER-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-254. - Resolution: Won't Do > Add support for UserSync and Authentication of Windows Platform > --- > > Key: RANGER-254 > URL: https://issues.apache.org/jira/browse/RANGER-254 > Project: Ranger > Issue Type: New Feature >Reporter: Selvamohan Neethiraj >Priority: Major > > When Hadoop is hosted on windows platform, the usersync lacks ability to pull > in the users from Windows Platform (unless it is setup as Active Directory > users). Also, if the RangerAdmin can use windows authentication to login, it > would provide easier access for Windows User into RangerAdmin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-254) Add support for UserSync and Authentication of Windows Platform
[ https://issues.apache.org/jira/browse/RANGER-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647851#comment-17647851 ] Selvamohan Neethiraj commented on RANGER-254: - As there are no further need for this feature (on windows platform), I am closing this JIRA. If needed, we can re-open it later. > Add support for UserSync and Authentication of Windows Platform > --- > > Key: RANGER-254 > URL: https://issues.apache.org/jira/browse/RANGER-254 > Project: Ranger > Issue Type: New Feature >Reporter: Selvamohan Neethiraj >Priority: Major > > When Hadoop is hosted on windows platform, the usersync lacks ability to pull > in the users from Windows Platform (unless it is setup as Active Directory > users). Also, if the RangerAdmin can use windows authentication to login, it > would provide easier access for Windows User into RangerAdmin UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-253) Add support for audit reporting for the data stored in HDFS
[ https://issues.apache.org/jira/browse/RANGER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj resolved RANGER-253. - Resolution: Not A Problem > Add support for audit reporting for the data stored in HDFS > --- > > Key: RANGER-253 > URL: https://issues.apache.org/jira/browse/RANGER-253 > Project: Ranger > Issue Type: New Feature >Reporter: Selvamohan Neethiraj >Priority: Major > > With the ability to store the audit log information in HDFS, Ranger needs to > provide tools to view (as report) the audit information. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-253) Add support for audit reporting for the data stored in HDFS
[ https://issues.apache.org/jira/browse/RANGER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647850#comment-17647850 ] Selvamohan Neethiraj commented on RANGER-253: - As HDFS is used for long term storage (which can be viewed by mapping it to Hive tables and querying it), we no longer need this functionality. Closing this JIRA. > Add support for audit reporting for the data stored in HDFS > --- > > Key: RANGER-253 > URL: https://issues.apache.org/jira/browse/RANGER-253 > Project: Ranger > Issue Type: New Feature >Reporter: Selvamohan Neethiraj >Priority: Major > > With the ability to store the audit log information in HDFS, Ranger needs to > provide tools to view (as report) the audit information. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17647847#comment-17647847
]
Selvamohan Neethiraj commented on RANGER-3866:
--
This is no longer needed. Closing this issue.
> 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-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
[ https://issues.apache.org/jira/browse/RANGER-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated RANGER-4017: - Attachment: 0001-RANGER-4017-running-ranger-in-few-mins-using-docker.patch > Complete Apache Ranger Stack on Docker - automation of existing README.md > -- > > Key: RANGER-4017 > URL: https://issues.apache.org/jira/browse/RANGER-4017 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4017-running-ranger-in-few-mins-using-docker.patch > > > Currently the docker based setup existing as Documentation in > ./dev-support/ranger-docker/README.md and we need a single script that can > do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4017) Complete Apache Ranger Stack on Docker - automation of existing README.md
Selvamohan Neethiraj created RANGER-4017: Summary: Complete Apache Ranger Stack on Docker - automation of existing README.md Key: RANGER-4017 URL: https://issues.apache.org/jira/browse/RANGER-4017 Project: Ranger Issue Type: Improvement Components: build-infra Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix For: 3.0.0 Currently the docker based setup existing as Documentation in ./dev-support/ranger-docker/README.md and we need a single script that can do all of the steps to automate the Apache Ranger runtime deployment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3863) Ranger Failed to run on Apple M1 macOS (Apple Silicon)
[
https://issues.apache.org/jira/browse/RANGER-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642106#comment-17642106
]
Selvamohan Neethiraj commented on RANGER-3863:
--
Thanks [~ttzztztz] . I have tested the above patch on Apple M2 and it needed
one more change as follows to complete the build successfully:
{code:java}
% git diff security-admin/pom.xml
diff --git a/security-admin/pom.xml b/security-admin/pom.xml
index 5e24dd846..54bd231d8 100644
--- a/security-admin/pom.xml
+++ b/security-admin/pom.xml
@@ -928,7 +928,7 @@
com.github.eirslett
frontend-maven-plugin
- 1.6
+ 1.12.1
${project.build.directory}
${project.build.directory} {code}
Since this change works on Apple M2, I do not know if this works fine on Apple
M1 and other Intel computers. Can you please include above change and see if
this works on Apple M1 ?
> Ranger Failed to run on Apple M1 macOS (Apple Silicon)
> --
>
> Key: RANGER-3863
> URL: https://issues.apache.org/jira/browse/RANGER-3863
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: ziyue
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to bump some dependencies to the latest version in order to support
> M1 aarm64 environment:
>
> # JNA to >= 5.7.0
> [https://github.com/java-native-access/jna/blob/master/CHANGES.md#release-570]
> # gethostname4j to >= 1.0.0
> [https://github.com/mattsheppard/gethostname4j/pull/8]
>
--
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-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: 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] [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] [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] [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=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-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-3730) log4j dependency is not completely removed
[
https://issues.apache.org/jira/browse/RANGER-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [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=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] [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-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=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] [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=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] [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] [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] [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: - 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] [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] [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=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)
