[
https://issues.apache.org/jira/browse/KUDU-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077718#comment-18077718
]
ASF subversion and git services commented on KUDU-3769:
-------------------------------------------------------
Commit 0ba7f54e15c9f673bf3e350f30b8d5f1a4037b79 in kudu's branch
refs/heads/master from Abhishek Chennaka
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0ba7f54e1 ]
KUDU-3769 Upgrade Ranger from 2.1 to 2.6
This patch upgrades the Apache Ranger and Ranger KMS dependencies from
2.1.0 to 2.6.0. To support this upgrade, several adaptations were
required in the Kudu MiniRanger test framework:
Ranger Admin & KMS Classpath:
- Updated the Ranger KMS classpath to include 'ews/lib/*' and
'ews/webapp/WEB-INF/lib/*'. This is required to find the
EmbeddedServer class and JAXB dependencies (required for Java 11+)
which were moved in the Ranger 2.6.0 directory restructuring.
User Management:
- Ranger 2.6.0 now enforces that users must exist in the Ranger
database before a policy can be created for them. Updated
MiniRanger::AddPolicy to automatically create unique users
prior to policy submission.
Test Assertions:
- Ranger 2.6.0 automatically generates a default "EXPIRES_ON" tag
policy upon service creation. Updated policy count assertions to
use the '?serviceName=kudu' filter to ensure tests only count
explicitly created Kudu policies.
Configurations:
- Added 'ranger.spnego.kerberos.name.rules' to support proper
principal mapping during Kerberos authentication needed for fetching
the policies.
- Added the mandatory configurations - JPA/JDBC connection properties
(timeouts, validation query, and PostgreSQL dialect) to
ranger-admin-default-site.xml.
Logging Migration (Log4j to Logback):
- Ranger 2.6 migrated its internal logging engine from Log4j 1.x to Logback.
Consequently, the legacy 'log4j.properties' template was ignored, causing
the Ranger Admin server to fall back to default DEBUG logging on stdout,
which spammed the test console.
- Replaced GetRangerLog4jProperties() with GetRangerLogbackXml() to
generate a valid Logback configuration.
Change-Id: I0923669abef6512ba9a53b985a3570af9fcc1f19
Reviewed-on: http://gerrit.cloudera.org:8080/24242
Tested-by: Abhishek Chennaka <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
> Upgrade Ranger dependency version to 2.6
> ----------------------------------------
>
> Key: KUDU-3769
> URL: https://issues.apache.org/jira/browse/KUDU-3769
> Project: Kudu
> Issue Type: Bug
> Reporter: Abhishek Chennaka
> Assignee: Abhishek Chennaka
> Priority: Major
>
> Upgrade the C++ (Mini Ranger used for tests ) and Java side (Ranger client
> used to fetch ranger policies) Ranger dependency versions to 2.6
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
