hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nemon Lou (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-9095) permanent functions' ClassLoader should be global instead of per-session
Date Sat, 13 Dec 2014 07:31:14 GMT

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

Nemon Lou updated HIVE-9095:
----------------------------
    Description: 
FunctionRegistry.mFunctions is static. That means that in HS2 case, all users will share the
same UDF class object from  mFunctions ,which lead to share the same classloader that load
this class. 

First,this will make the per-session classloader useless.Because only the first classLoader
will be used to initailize the instances of the permanent UDF class.
Second, it's will cause class not found exception,when the classLoader created by the first
session has been closed before load all the classes that need.

  was:
FunctionRegistry.mFunctions is static. That means that in HS2 case, all users will share the
same UDF class object from  mFunctions ,which lead to share the same classloader that load
this class. 

First,this will make the per-session classloader useless.Because only the first classLoader
will be used to initailize the instances of the permanent UDF class.
Second, it's will cause class not found exception,when the classLoader created by the first
session be closed before load all the classes that need.


> permanent functions' ClassLoader should be global instead of per-session
> ------------------------------------------------------------------------
>
>                 Key: HIVE-9095
>                 URL: https://issues.apache.org/jira/browse/HIVE-9095
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, UDF
>    Affects Versions: 0.14.0, 0.13.1
>            Reporter: Nemon Lou
>
> FunctionRegistry.mFunctions is static. That means that in HS2 case, all users will share
the same UDF class object from  mFunctions ,which lead to share the same classloader that
load this class. 
> First,this will make the per-session classloader useless.Because only the first classLoader
will be used to initailize the instances of the permanent UDF class.
> Second, it's will cause class not found exception,when the classLoader created by the
first session has been closed before load all the classes that need.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message