[HIVE-6364] HiveServer2 - Request serving thread should get class loader from existing SessionState

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Component/s: HiveServer2
• Assignee: Unassigned
• Reporter: Jaideep Dhok
• Created: 04/Feb/14 12:37
• Updated: 23/Mar/14 16:56
• Resolved: 23/Mar/14 16:56

Description

SessionState is created for each session in HS2. If we do any add jars, a class loader is set in the SessionState's conf object. This class loader should also be set in each thread that serves request of the same session.

Scenario (both requests are in the same session)-

// req 1
add jar foo.jar // Served by thread th1, this updates class loader and sets in SessionState.conf

// req2 served by th2, such that th1 != th2
CREATE TEMPORARY FUNCTION foo_udf AS 'some class in foo.jar' 
// This can throw class not found error, because although 
// the new thread (th2) gets the same session state as th1,
// the class loader is different (Thread.currentThread.getContextClassLoader()

Issue Links

• duplicates: HIVE-3969 Session state for hive server should be cleaned-up