Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9E255100D8 for ; Fri, 14 Mar 2014 19:32:58 +0000 (UTC) Received: (qmail 41820 invoked by uid 500); 14 Mar 2014 19:32:51 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 41419 invoked by uid 500); 14 Mar 2014 19:32:46 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 41376 invoked by uid 500); 14 Mar 2014 19:32:45 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 41371 invoked by uid 99); 14 Mar 2014 19:32:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Mar 2014 19:32:45 +0000 Date: Fri, 14 Mar 2014 19:32:44 +0000 (UTC) From: "Jason Dere (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-6672) JARs loaded by permanent functions don't work properly with HiveServer2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jason Dere created HIVE-6672: -------------------------------- Summary: JARs loaded by permanent functions don't work properly with HiveServer2 Key: HIVE-6672 URL: https://issues.apache.org/jira/browse/HIVE-6672 Project: Hive Issue Type: Bug Components: HiveServer2, UDF Reporter: Jason Dere Permanent functions which specify JAR files to load do not seem to work properly with HiveServer2. While the function can be created and see with SHOW FUNCTIONS, doing DESCRIBE FUNCTION or using the UDF in a query results in java.lang.ClassNotFoundException. It looks like the JAR is only added to the classloader of the very first thread which references the UDF. Subsequent threads will have a different class loader which may not have loaded the JAR, but because the UDF is already in the FunctionRegistry these threads do not attempt to load the resources for the UDF. -- This message was sent by Atlassian JIRA (v6.2#6252)