You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Madhan Neethiraj (Jira)" <ji...@apache.org> on 2019/11/26 23:29:00 UTC
[jira] [Created] (RANGER-2654) refactor RangerBasePlugins to remove
static servicePluginsMap
Madhan Neethiraj created RANGER-2654:
----------------------------------------
Summary: 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
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)