Siyao Meng created HDDS-8320:
--------------------------------
Summary: Remove exclusion of jackson from ranger-intg
Key: HDDS-8320
URL: https://issues.apache.org/jira/browse/HDDS-8320
Project: Apache Ozone
Issue Type: Task
Reporter: Siyao Meng
Assignee: Siyao Meng
It turns out excluding jackson might have broken actual ranger-intg client
usage:
{code}
E 23/03/28 20:05:54 INFO rpc.RpcClient: Creating Tenant:
'tenant303241680030324', with new volume: 'tenant303241680030324'
E at
org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:232)
E at
org.apache.ranger.plugin.util.RangerRESTClient.getClient(RangerRESTClient.java:215)
E at
org.apache.ranger.plugin.util.RangerRESTClient.post(RangerRESTClient.java:576)
E at
org.apache.ranger.RangerClient.invokeREST(RangerClient.java:422)
E at
org.apache.ranger.RangerClient.lambda$responseHandler$0(RangerClient.java:464)
E at
org.apache.ranger.RangerClient.responseHandler(RangerClient.java:462)
E at org.apache.ranger.RangerClient.callAPI(RangerClient.java:527)
E at
org.apache.ranger.RangerClient.createRole(RangerClient.java:334)
E Caused by: java.lang.ClassNotFoundException:
org.codehaus.jackson.jaxrs.JacksonJsonProvider
E ... 26 more
{code}
Unfortunately our acceptance tests didn't cover the actual Ranger client
testing because the infra is not there yet. iirc [~djo10] is trying to improve
the docker dev env to spin up actual Ranger, at which point we could write new
acceptance tests that uses ranger-intg client to run against actual Ranger
Admin Server.
cc [~adoroszlai]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
