This is an automated email from the ASF dual-hosted git repository.
pradeep pushed a change to branch RANGER-4076_master
in repository https://gitbox.apache.org/repos/asf/ranger.git
discard 1cb016ba2 RANGER-5475: add JWT support in RangerRESTClient (#831)
discard 2c20ae82a RANGER-4706: Change jdk version to 17 in docker
discard eeeb18757 RANGER-4706: Migrate from com.sun.jersey 1.x to glassfish
jersey 2.x
discard 7889b3ab1 RANGER-4076: Document update for required environment
variable
discard ec56416e3 RANGER-4076: Fix TestCase failures in
TestRecordFilterJavaScript
discard 6fd3bbe37 RANGER-4076: Ranger KMS changes for JDK17 build
discard 9131f86ae RANGER-4076: Fix TestCase failures in
RangerRequestScriptEvaluatorTest
discard 91ee400f7 RANGER-4076: Unix Auth Client remove deprecated APIs
discard 47136a5a6 RANGER-4076: Remove Nashorn Script Engine
discard 5cc7c1e4a RANGER-4076: pom & config changes for jdk17 build
discard c46223de2 Revert "RANGER-5475: add JWT support in RangerRESTClient
(#831)"
add aa9f9bc25 RANGER-5465: Handle upgrade failure caused by the Java patch
during the Ranger DB upgrade (#835)
add 5ea59e017 RANGER-5477:XML External Entity Injection Security issue in
Ranger (#834)
new 547fdf6b8 Revert "RANGER-5475: add JWT support in RangerRESTClient
(#831)"
new a16101e67 RANGER-4076: pom & config changes for jdk17 build
new 5eddf7182 RANGER-4076: Remove Nashorn Script Engine
new 039a96166 RANGER-4076: Unix Auth Client remove deprecated APIs
new 3fee43eb1 RANGER-4076: Fix TestCase failures in
RangerRequestScriptEvaluatorTest
new c6ac32b65 RANGER-4076: Ranger KMS changes for JDK17 build
new 6b01b3691 RANGER-4076: Fix TestCase failures in
TestRecordFilterJavaScript
new e9e20b3dc RANGER-4076: Document update for required environment
variable
new 911a4fba1 RANGER-4706: Migrate from com.sun.jersey 1.x to glassfish
jersey 2.x
new 1ebecee2b RANGER-4706: Change jdk version to 17 in docker
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1cb016ba2)
\
N -- N -- N refs/heads/RANGER-4076_master (1ebecee2b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 10 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../ranger/plugin/util/RangerRESTClient.java | 141 +++++----------------
.../ranger/utils/install/XmlConfigChanger.java | 3 +
.../org/apache/ranger/db/XXSecurityZoneDao.java | 15 +++
...tchPreSql_057_ForUpdateToUniqueGUID_J10052.java | 7 +-
...ForUpdateToUniqueResoureceSignature_J10053.java | 8 +-
.../main/resources/META-INF/jpa_named_queries.xml | 6 +
...tchPreSql_057_ForUpdateToUniqueGUID_J10052.java | 2 +-
.../tagsync/sink/tagadmin/TagAdminRESTSink.java | 2 +-
.../process/RangerUgSyncRESTClient.java | 8 +-
9 files changed, 67 insertions(+), 125 deletions(-)
