This is an automated email from the ASF dual-hosted git repository.

abhi pushed a change to branch kumaab-ci-docker-fix
in repository https://gitbox.apache.org/repos/asf/ranger.git


    omit a25b96c0e Update docker compose command in CI
     add 2e34537fa RANGER-4911: support validity-schedule in datasets/projects 
to enable automatic expiry
     add 8bb2053f8 Fix maven build - add jetbrains repository (#380)
     add 2658002cf Update docker compose command in CI

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   (a25b96c0e)
            \
             N -- N -- N   refs/heads/kumaab-ci-docker-fix (2658002cf)

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.

No new revisions were added by this update.

Summary of changes:
 .../org/apache/ranger/plugin/model/RangerGds.java  | 24 ++++--
 .../policyengine/gds/GdsDatasetEvaluator.java      | 88 +++++++++++++---------
 .../policyengine/gds/GdsProjectEvaluator.java      | 70 ++++++++++-------
 .../apache/ranger/plugin/util/ServiceGdsInfo.java  | 28 +++++--
 .../src/test/resources/plugin/hive_gds_info.json   | 56 +++++++++++++-
 .../resources/plugin/test_base_plugin_hive.json    |  8 +-
 .../gds/test_gds_policy_engine_hive.json           | 40 +++++++---
 pom.xml                                            | 14 ++--
 .../apache/ranger/common/ServiceGdsInfoCache.java  |  2 +
 9 files changed, 229 insertions(+), 101 deletions(-)

Reply via email to