[GitHub] [ranger] mr1716 opened a new pull request, #172: Update Hadoop To 3.3.4
mr1716 opened a new pull request, #172: URL: https://github.com/apache/ranger/pull/172 Upgrading Hadoop to 3.3.4 will help reduce the number of open CVEs in the ranger product -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (RANGER-3865) support for using user attributes in masking expressions
Madhan Neethiraj created RANGER-3865:
Summary: support for using user attributes in masking expressions
Key: RANGER-3865
URL: https://issues.apache.org/jira/browse/RANGER-3865
Project: Ranger
Issue Type: Improvement
Components: plugins
Reporter: Madhan Neethiraj
RANGER-3550 introduced support for referencing user attributes in row-filter
expressions.
Extending use of user attributes in masking expressions can help address more
use cases, including the following:
Restrict users to see email address of customers in user's country only; email
address of other customers must be masked:
{code:java}
CASE WHEN country = '${{USER.country}}' THEN {col} ELSE mask({col}) END{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74096: RANGER-3865: support user attribute references in masking expressions
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74096/ --- Review request for ranger, Abhishek Kumar, Ankita Sinha, Kishor Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy. Bugs: RANGER-3865 https://issues.apache.org/jira/browse/RANGER-3865 Repository: ranger Description --- updated masking policy evaluation to handle expressions similar to in row-filters Diffs - agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultDataMaskPolicyItemEvaluator.java 8d9969a3f agents-common/src/test/java/org/apache/ranger/plugin/policyengine/TestPolicyEngine.java e6bd2f4f8 agents-common/src/test/resources/policyengine/test_policyengine_hive_mask_filter_with_req_expressions.json PRE-CREATION Diff: https://reviews.apache.org/r/74096/diff/1/ Testing --- - added unit tests to verify handling of user attributes in masking expressions - verified that existing tests pass successfully Thanks, Madhan Neethiraj
[jira] [Updated] (RANGER-3865) support for using user attributes in masking expressions
[
https://issues.apache.org/jira/browse/RANGER-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-3865:
-
Attachment: RANGER-3865.patch
> support for using user attributes in masking expressions
>
>
> Key: RANGER-3865
> URL: https://issues.apache.org/jira/browse/RANGER-3865
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: RANGER-3865.patch
>
>
> RANGER-3550 introduced support for referencing user attributes in row-filter
> expressions.
> Extending use of user attributes in masking expressions can help address more
> use cases, including the following:
> Restrict users to see email address of customers in user's country only;
> email address of other customers must be masked:
> {code:java}
> CASE WHEN country = '${{USER.country}}' THEN {col} ELSE mask({col}) END{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-3865) support for using user attributes in masking expressions
[
https://issues.apache.org/jira/browse/RANGER-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reassigned RANGER-3865:
Assignee: Madhan Neethiraj
> support for using user attributes in masking expressions
>
>
> Key: RANGER-3865
> URL: https://issues.apache.org/jira/browse/RANGER-3865
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: RANGER-3865.patch
>
>
> RANGER-3550 introduced support for referencing user attributes in row-filter
> expressions.
> Extending use of user attributes in masking expressions can help address more
> use cases, including the following:
> Restrict users to see email address of customers in user's country only;
> email address of other customers must be masked:
> {code:java}
> CASE WHEN country = '${{USER.country}}' THEN {col} ELSE mask({col}) END{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3865) support for using user attributes in masking expressions
[
https://issues.apache.org/jira/browse/RANGER-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584352#comment-17584352
]
Barbara Eckman commented on RANGER-3865:
Is this built to work with all plugins, or just hive?
> support for using user attributes in masking expressions
>
>
> Key: RANGER-3865
> URL: https://issues.apache.org/jira/browse/RANGER-3865
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-3865.patch
>
>
> RANGER-3550 introduced support for referencing user attributes in row-filter
> expressions.
> Extending use of user attributes in masking expressions can help address more
> use cases, including the following:
> Restrict users to see email address of customers in user's country only;
> email address of other customers must be masked:
> {code:java}
> CASE WHEN country = '${{USER.country}}' THEN {col} ELSE mask({col}) END{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74096: RANGER-3865: support user attribute references in masking expressions
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74096/#review224641 --- Ship it! Ship It! - Abhay Kulkarni On Aug. 24, 2022, 1:14 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74096/ > --- > > (Updated Aug. 24, 2022, 1:14 p.m.) > > > Review request for ranger, Abhishek Kumar, Ankita Sinha, Kishor > Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy. > > > Bugs: RANGER-3865 > https://issues.apache.org/jira/browse/RANGER-3865 > > > Repository: ranger > > > Description > --- > > updated masking policy evaluation to handle expressions similar to in > row-filters > > > Diffs > - > > > agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultDataMaskPolicyItemEvaluator.java > 8d9969a3f > > agents-common/src/test/java/org/apache/ranger/plugin/policyengine/TestPolicyEngine.java > e6bd2f4f8 > > agents-common/src/test/resources/policyengine/test_policyengine_hive_mask_filter_with_req_expressions.json > PRE-CREATION > > > Diff: https://reviews.apache.org/r/74096/diff/1/ > > > Testing > --- > > - added unit tests to verify handling of user attributes in masking > expressions > - verified that existing tests pass successfully > > > Thanks, > > Madhan Neethiraj > >
[jira] [Commented] (RANGER-3865) support for using user attributes in masking expressions
[
https://issues.apache.org/jira/browse/RANGER-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584383#comment-17584383
]
Madhan Neethiraj commented on RANGER-3865:
--
{quote}Is this built to work with all plugins, or just hive?
{quote}
[~barbara] - replacing of user attribute expressions in the mask value
specified in Ranger policies works for all plugins.
> support for using user attributes in masking expressions
>
>
> Key: RANGER-3865
> URL: https://issues.apache.org/jira/browse/RANGER-3865
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-3865.patch
>
>
> RANGER-3550 introduced support for referencing user attributes in row-filter
> expressions.
> Extending use of user attributes in masking expressions can help address more
> use cases, including the following:
> Restrict users to see email address of customers in user's country only;
> email address of other customers must be masked:
> {code:java}
> CASE WHEN country = '${{USER.country}}' THEN {col} ELSE mask({col}) END{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] [Assigned] (RANGER-3858) On dev-support, service creation and ranger-kafka-plugin setup are failed
[ https://issues.apache.org/jira/browse/RANGER-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Kulkarni reassigned RANGER-3858: -- Assignee: Abhay Kulkarni > On dev-support, service creation and ranger-kafka-plugin setup are failed > - > > Key: RANGER-3858 > URL: https://issues.apache.org/jira/browse/RANGER-3858 > Project: Ranger > Issue Type: Bug > Components: build-infra >Affects Versions: 2.3.0 >Reporter: YUBI LEE >Assignee: Abhay Kulkarni >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > There are 2 bugs in dev-support. > 1. create-ranger-services.py > "service_not_exists" returns 0 even though there is no service. > 2. ranger-kafka-setup.sh > "authorizer.class.name=org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer" > should be appended after a newline. > If not, kafka fails to start with wrong configuration. > PR: https://github.com/apache/ranger/pull/170/files -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74097: RANGER-3858: On dev-support, service creation and ranger-kafka-plugin setup are failed
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74097/ --- Review request for ranger, Abhishek Kumar, Yubo Li, and Madhan Neethiraj. Bugs: RANGER-3858 https://issues.apache.org/jira/browse/RANGER-3858 Repository: ranger Description --- There are 2 bugs in dev-support. 1. create-ranger-services.py "service_not_exists" returns 0 even though there is no service. 2. ranger-kafka-setup.sh "authorizer.class.name=org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer" should be appended after a newline. If not, kafka fails to start with wrong configuration. Diffs - dev-support/ranger-docker/scripts/create-ranger-services.py 7ce541d66 dev-support/ranger-docker/scripts/ranger-kafka-setup.sh c6edce6b9 Diff: https://reviews.apache.org/r/74097/diff/1/ Testing --- Created a docker images and created and ran containers. Verified that services are created correctly in the Ranger-admin. Thanks, Abhay Kulkarni
Re: Review Request 74097: RANGER-3858: On dev-support, service creation and ranger-kafka-plugin setup are failed
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74097/#review224642 --- Ship it! Ship It! - Abhishek Kumar On Aug. 24, 2022, 11:49 p.m., Abhay Kulkarni wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74097/ > --- > > (Updated Aug. 24, 2022, 11:49 p.m.) > > > Review request for ranger, Abhishek Kumar, Yubo Li, and Madhan Neethiraj. > > > Bugs: RANGER-3858 > https://issues.apache.org/jira/browse/RANGER-3858 > > > Repository: ranger > > > Description > --- > > There are 2 bugs in dev-support. > > 1. create-ranger-services.py > > "service_not_exists" returns 0 even though there is no service. > > 2. ranger-kafka-setup.sh > > "authorizer.class.name=org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer" > should be appended after a newline. > If not, kafka fails to start with wrong configuration. > > > Diffs > - > > dev-support/ranger-docker/scripts/create-ranger-services.py 7ce541d66 > dev-support/ranger-docker/scripts/ranger-kafka-setup.sh c6edce6b9 > > > Diff: https://reviews.apache.org/r/74097/diff/1/ > > > Testing > --- > > Created a docker images and created and ran containers. Verified that > services are created correctly in the Ranger-admin. > > > Thanks, > > Abhay Kulkarni > >
[jira] [Created] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
Selvamohan Neethiraj created RANGER-3866:
Summary: Ranger Build based on Docker is failing with HTTP 503
error ...
Key: RANGER-3866
URL: https://issues.apache.org/jira/browse/RANGER-3866
Project: Ranger
Issue Type: Bug
Components: build-infra
Reporter: Selvamohan Neethiraj
Assignee: Selvamohan Neethiraj
{code:java}
=> ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
=> CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa 0.0s
=> CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c 0.0s
=> [ 2/26] RUN mkdir /tools 0.2s
--
>
http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
--
failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
[
https://issues.apache.org/jira/browse/RANGER-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-3866:
-
Attachment: 0001-RANGER-3866-updated-build-script-to-use-latest-cento.patch
> Ranger Build based on Docker is failing with HTTP 503 error ...
> ---
>
> Key: RANGER-3866
> URL: https://issues.apache.org/jira/browse/RANGER-3866
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
>Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
>Priority: Major
> Attachments:
> 0001-RANGER-3866-updated-build-script-to-use-latest-cento.patch
>
>
> {code:java}
> => ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
> => CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa
> 0.0s
> => CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c
> 0.0s
> => [ 2/26] RUN mkdir /tools
> 0.2s
> --
> >
> http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
> --
> failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74099: RANGER-3866 : Docker based build script fails due to incorrect maven link and other script issues.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74099/ --- Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Ramesh Mani, and Velmurugan Periasamy. Bugs: RANGER-3866 https://issues.apache.org/jira/browse/RANGER-3866 Repository: ranger Description --- Restructured to have its own Dockerfile and also updated centos, maven versions to latest. Diffs - Dockerfile PRE-CREATION build_ranger_using_docker.sh 9aadfb5f7 docker-mvn.sh PRE-CREATION Diff: https://reviews.apache.org/r/74099/diff/1/ Testing --- Tested on Ubuntu Docker and also on Mac M2 Docker. I am able to build ranger without any issue after applying the patch. Thanks, Selvamohan Neethiraj
Re: Review Request 74099: RANGER-3866 : Docker based build script fails due to incorrect maven link and other script issues.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74099/ --- (Updated Aug. 24, 2022, 11:23 p.m.) Review request for ranger, Don Bosco Durai, Madhan Neethiraj, Ramesh Mani, and Velmurugan Periasamy. Changes --- Updated diff file after removing some debug code. Bugs: RANGER-3866 https://issues.apache.org/jira/browse/RANGER-3866 Repository: ranger Description --- Restructured to have its own Dockerfile and also updated centos, maven versions to latest. Diffs (updated) - Dockerfile PRE-CREATION build_ranger_using_docker.sh 9aadfb5f72d2662eff648c52ec6e7df52d7d2e12 docker-mvn.sh PRE-CREATION Diff: https://reviews.apache.org/r/74099/diff/2/ Changes: https://reviews.apache.org/r/74099/diff/1-2/ Testing --- Tested on Ubuntu Docker and also on Mac M2 Docker. I am able to build ranger without any issue after applying the patch. Thanks, Selvamohan Neethiraj
[jira] [Updated] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
[
https://issues.apache.org/jira/browse/RANGER-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-3866:
-
Attachment: (was:
0001-RANGER-3866-updated-build-script-to-use-latest-cento.patch)
> Ranger Build based on Docker is failing with HTTP 503 error ...
> ---
>
> Key: RANGER-3866
> URL: https://issues.apache.org/jira/browse/RANGER-3866
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
>Affects Versions: 3.0.0
>Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> RANGER-3866-updated-build-script-to-use-latest-cento-wo-debug.diff
>
>
> {code:java}
> => ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
> => CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa
> 0.0s
> => CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c
> 0.0s
> => [ 2/26] RUN mkdir /tools
> 0.2s
> --
> >
> http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
> --
> failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3866) Ranger Build based on Docker is failing with HTTP 503 error ...
[
https://issues.apache.org/jira/browse/RANGER-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Selvamohan Neethiraj updated RANGER-3866:
-
Attachment:
RANGER-3866-updated-build-script-to-use-latest-cento-wo-debug.diff
> Ranger Build based on Docker is failing with HTTP 503 error ...
> ---
>
> Key: RANGER-3866
> URL: https://issues.apache.org/jira/browse/RANGER-3866
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
>Affects Versions: 3.0.0
>Reporter: Selvamohan Neethiraj
>Assignee: Selvamohan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> RANGER-3866-updated-build-script-to-use-latest-cento-wo-debug.diff
>
>
> {code:java}
> => ERROR http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apac 0.0s
> => CANCELED https://www.apache.org/dist/maven/maven-3/3.6.3/binaries/apa
> 0.0s
> => CACHED [ 1/26] FROM docker.io/library/centos@sha256:a27fd8080b517143c
> 0.0s
> => [ 2/26] RUN mkdir /tools
> 0.2s
> --
> >
> http://www-us.apache.org/dist/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz:
> --
> failed to load cache key: invalid response status 503 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3108) NPE in RangerPolicyRepository.init
[
https://issues.apache.org/jira/browse/RANGER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584574#comment-17584574
]
Yi kaifei commented on RANGER-3108:
---
[~rmani] Shall we cherry-pick this patch to version 2.3.0 ? Currently, we use
logback instead of log4j, it default log level is debug, this NPE is easy to
trigger
> NPE in RangerPolicyRepository.init
> --
>
> Key: RANGER-3108
> URL: https://issues.apache.org/jira/browse/RANGER-3108
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.2.0
>Reporter: Andrew Wong
>Assignee: Ramesh Mani
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-3108-NPE-in-RangerPolicyRepository.init.patch,
> ranger_client-test.txt
>
>
> Over the past few days, Kudu's {{RangerClientTestBase.TestLogging}} has
> failed consistently when trying to access the Ranger plugin with unreleased
> bits that are aligned with Ranger's {{master}} branch, at least from the
> stack trace line numbers.
> {code:java}
> 2020-12-03 23:59:46.333 [ERROR - main] (RangerBasePlugin.java:309)
> setPolicies: policy engine initialization failed! Leaving current policy
> engine as-is. Exception :
> java.lang.NullPointerException: null
> at
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:1075)
> ~[kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:326)
> ~[kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:277)
> ~[kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:195)
> ~[kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:82)
> ~[kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:246)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:260)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:142)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:185)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.kudu.subprocess.ranger.authorization.RangerKuduAuthorizer.init(RangerKuduAuthorizer.java:90)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.kudu.subprocess.ranger.RangerProtocolHandler.(RangerProtocolHandler.java:45)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> at
> org.apache.kudu.subprocess.ranger.RangerSubprocessMain.main(RangerSubprocessMain.java:39)
> [kudu-subprocess.jar:1.13.0.internal-version-SNAPSHOT]
> {code}
> Poking around the codebase a bit, it seems like the line in question was
> [added
> recently|https://github.com/apache/ranger/blame/master/agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyRepository.java#L1075]
> (6 days ago as of writing this), while the Ranger code Kudu-side hasn't been
> touched recently at all, leading me to suspect this being a Ranger plugin
> issue rather than improper use of the plugin on our end.
> The failing Kudu test can be found
> [here|https://github.com/apache/kudu/blob/master/src/kudu/ranger/ranger_client-test.cc#L405].
> The gist of the test is that it starts a Ranger server, creates a simple
> policy, and tries to authorize some requests by sending requests over a named
> pipe to a Java process that runs a long-lived Ranger plugin (the first of
> which fails, presumably because of this NPE).
--
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&focusedCommentId=17584615#comment-17584615
]
Madhan Neethiraj commented on RANGER-3866:
--
[~sneethiraj] - I suggest to remove these docker scripts, given a more
comprehensive setup is available in dev-support/ranger-docker - more info at
[https://github.com/apache/ranger/tree/master/dev-support/ranger-docker].
> 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)
