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

dhavalshah9131 pushed a change to branch ds_RANGER-5215_us
in repository https://gitbox.apache.org/repos/asf/ranger.git


    omit 6d46c54a5 RANGER-5215 : Policy authroisation fails for Ranger Plugins 
in case of users/groups converted by Ranger userysnc as per given Regex
    omit 6325ed3fa RANGER-5223: Audit logs not generated for Dataset 
modifications (Labels, Keywords, isEnabled)
    omit 1d4ff9cde RANGER-5155 : Service Definition with empty configs causes 
Ranger UI rendering issues (#577)
    omit eff7f1256 RANGER-5180: GDS feature support on Oracle database
    omit 4555d7dc4 RANGER-5191: Fix typo in the log message in RangerRESTClient 
(#557)
    omit ca8fcec7e RANGER-5216: added unit tests for Atlas authorizer (#581)
    omit 4407d6ce1 RANGER-5213: Add Support for isEnabled Filter and 
Full/Partial Text Search on Labels and Keywords in Dataset Search
    omit 1cb013855 RANGER-5215 : Policy authroisation fails for Ranger Plugins 
in case of users/groups converted by Ranger userysnc as per given Regex
     add 44e27a4fe RANGER-5213: Add Support for isEnabled Filter and 
Full/Partial Text Search on Labels and Keywords in Dataset Search
     add 109dc779e RANGER-5216: added unit tests for Atlas authorizer (#581)
     add 35dd720d8 RANGER-5191: Fix typo in the log message in RangerRESTClient 
(#557)
     add 30b1988fc RANGER-5180: GDS feature support on Oracle database
     add dd85a691a RANGER-5155 : Service Definition with empty configs causes 
Ranger UI rendering issues (#577)
     add 1e03bcaa7 RANGER-5223: Audit logs not generated for Dataset 
modifications (Labels, Keywords, isEnabled)
     add f969e3e13 RANGER-5215 : Policy authroisation fails for Ranger Plugins 
in case of users/groups converted by Ranger userysnc as per given Regex
     add be624fbfa RANGER-5215 : Policy authroisation fails for Ranger Plugins 
in case of users/groups converted by Ranger userysnc as per given Regex

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   (6d46c54a5)
            \
             N -- N -- N   refs/heads/ds_RANGER-5215_us (be624fbfa)

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:

Reply via email to