You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Dilli Arumugam (JIRA)" <ji...@apache.org> on 2015/03/15 02:53:38 UTC
[jira] [Updated] (RANGER-314) Remove custom class loader used by
ranger admin for resource lookup
[ https://issues.apache.org/jira/browse/RANGER-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dilli Arumugam updated RANGER-314:
----------------------------------
Attachment: RANGER-314.1.patch
patch
> Remove custom class loader used by ranger admin for resource lookup
> -------------------------------------------------------------------
>
> Key: RANGER-314
> URL: https://issues.apache.org/jira/browse/RANGER-314
> Project: Ranger
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Fix For: 0.5.0
>
> Attachments: RANGER-314.1.patch
>
>
> Remove custom class loader used by ranger admin for resource lookup
> Right now ranger admin resource lookup for hdfs, hive and hbase are relying custom classloader org.apache.ranger.plugin.client.HadoopClassLoader. This requires us to define property name to site file (e.g. core-site.xml) mapping in resourcenamemap.properties.
> We should try to eliminate the need for the custom class loader and the need to maintain property name to site file mapping to make it easy to onboard new plugins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)