[
https://issues.apache.org/jira/browse/RANGER-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2654:
-----------------------------------------
Fix Version/s: (was: master)
> refactor RangerBasePlugins to remove static servicePluginsMap
> --------------------------------------------------------------
>
> Key: RANGER-2654
> URL: https://issues.apache.org/jira/browse/RANGER-2654
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: RANGER-2654-3.patch, RANGER-2654.patch
>
>
> Currently RangerBasePlugin has a static member {{servicePluginsMap}}, which
> is used in following cases:
> 1. to notify plugin of change in auth-context, like updates to tags
> 2. to get audit provider for the plugin, from
> RangerDefaultAuditHandler.logAuthzAudit()
> #1 can be addressed by moving the notification details to RangerAuthContext
> #2 can be addressed by getting the audit provider from the global
> audit-provider factory instance. This move (of static) from
> plugin->audit-factory would enable multiple plugin instances to use same
> audit provider.
> In addition, much of the state information in RangerBasePlugin (like
> serviceName, serviceType, appId, etc.) should be moved to another class, like
> RangerPluginConfig.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
