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 2022/02/22 21:19:00 UTC

[jira] [Updated] (RANGER-3636) Plugin classloader should use classloader of shim class as parent

     [ https://issues.apache.org/jira/browse/RANGER-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj updated RANGER-3636:
-------------------------------------
    Attachment: RANGER-3636.patch

> Plugin classloader should use classloader of shim class as parent
> -----------------------------------------------------------------
>
>                 Key: RANGER-3636
>                 URL: https://issues.apache.org/jira/browse/RANGER-3636
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: RANGER-3636.patch
>
>
> Ranger uses plugin-classloader to avoid libraries needed by plugin implementation to be visible in component's CLASSPATH (RANGER-586). For classes/resources that are not found in plugin-impl directory, the classloader uses component's (service's) classloader. Currently, current thread's classloader is used as the component's classloader. However, this may not work for services that use class isolation themselves, in which case the current thread's classloader might be different from component's classloader. A better option will be to use the classloader that loaded the plugin shim class as the component classloader.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)