You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Abhishek Kumar (Jira)" <ji...@apache.org> on 2023/03/03 01:35:00 UTC

[jira] [Commented] (RANGER-4114) Consistent use of plugin property prefix in context enrichers

    [ https://issues.apache.org/jira/browse/RANGER-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695957#comment-17695957 ] 

Abhishek Kumar commented on RANGER-4114:
----------------------------------------

Merged to master: [https://github.com/apache/ranger/commit/f909c81024b03ce69fd401c259f9849a6886a57d]

> Consistent use of plugin property prefix in context enrichers
> -------------------------------------------------------------
>
>                 Key: RANGER-4114
>                 URL: https://issues.apache.org/jira/browse/RANGER-4114
>             Project: Ranger
>          Issue Type: Improvement
>          Components: plugins
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>             Fix For: 3.0.0, 2.4.0
>
>         Attachments: RANGER-4114.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Ranger plugins read configurations (like URL to Ranger) from properties having prefix {_}'ranger.plugin.' + serviceType{_}. serviceType is provided as a parameter when a plugin is instantiated, which results in plugin to use the given serviceType in property prefix - for example __ {_}ranger.plugin.hive.policy.rest.url{_}. However, context enrichers (like tag-enrichers) don't use the same property prefix; instead, derive the prefix from serviceType found in the policies downloaded from Ranger. Though these approaches usually arrive at the same property prefix, it will help or the plugin library to use consistent property prefix across all references.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)