[
https://issues.apache.org/jira/browse/HIVE-21409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796834#comment-16796834
]
Shawn Weeks edited comment on HIVE-21409 at 3/20/19 6:14 AM:
-------------------------------------------------------------
So far I've identified that the Apache Atlas Hook and the RangerHiveAuthorizer
are both modifying the current threads classloader without consideration for
the current threads existing classloader. It probably wouldn't be an issue if
they were just adding to the classloader but it looks like they're completely
replacing it with one from another session.
was (Author: absolutesantaja):
So far I've identified that the Apache Atlas Hook and the RangerHiveAuthorizer
are both modify the current threads classloader without consideration for the
current threads existing classloader. It probably wouldn't be an issue if they
were just adding to the classloader but it looks like they're completely
replacing it with one from another session.
> Initial SessionState ClassLoader Reused For Subsequent Sessions
> ---------------------------------------------------------------
>
> Key: HIVE-21409
> URL: https://issues.apache.org/jira/browse/HIVE-21409
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Shawn Weeks
> Priority: Minor
> Attachments: create_class.sql, run.sql, setup.sql
>
>
> It appears that the first ClassLoader attached to a SessionState Static
> Instance is being reused as the parent for all future sessions. This causes
> any libraries added to the class path on the initial session to be added to
> future sessions. It also appears that further sessions may be adding jars to
> this initial ClassLoader as well leading to the class path getting more and
> more polluted. This occurring on a build including HIVE-11878. I've included
> some examples that greatly exaggerate the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
