Yeah it looks like 1.1.0+cdh5.4.3+151 backported HIVE-2573<https://issues.apache.org/jira/browse/HIVE-2573>, which has the bug you are seeing (fixed in HIVE-10288).
________________________________ From: Chagarlamudi, Prasanth <prasanth.chagarlam...@epsilon.com> Sent: Thursday, February 11, 2016 2:07 PM To: user@hive.apache.org Subject: RE: Hive Permanent functions not working after a cluster restart. Fyi Bastian, This is fixed in version 1.2. https://issues.apache.org/jira/browse/HIVE-10288 If you are using cloudera distribution ? This issue is fixed in CHD 5.5 version. I wasn’t able to find an alternative so far than to look for a latest version or recreate them every time you restart. Thanks Prasanth Chagarlamudi From: Bastian Kronenbitter [mailto:bastian.kronenbit...@adello.com] Sent: Thursday, February 11, 2016 2:20 AM To: user@hive.apache.org Subject: RE: Hive Permanent functions not working after a cluster restart. Hi all, We face the same problem. Every time we restart the hive server, permanent functions are not working. We are also using the hive 1.1 version of CDH5. Listing the functions using “SHOW FUNCTIONS” shows the permanent functions, but without the database prefix they normally have. We use a mysql metastore db and looking into it, I see the permanent functions in FUNCS and the corresponding resources in FUNC_RU. Dropping the functions and creating them again solves the problem (until the next restart). Any help or pointer is very much appreciated. Best regards, Bastian From: Surendra , Manchikanti [mailto:surendra.manchika...@gmail.com]<mailto:[mailto:surendra.manchika...@gmail.com]> Sent: Mittwoch, 10. Februar 2016 20:09 To: user@hive.apache.org<mailto:user@hive.apache.org> Subject: Re: Hive Permanent functions not working after a cluster restart. Please check your metastore database tables refreshing after a restart ? Permanent functions will be stored in DB. -- Surendra Manchikanti On Wed, Feb 10, 2016 at 7:58 AM, Chagarlamudi, Prasanth <prasanth.chagarlam...@epsilon.com<mailto:prasanth.chagarlam...@epsilon.com>> wrote: Hi Surendra, Its Derby. Thanks Prasanth C From: Surendra , Manchikanti [mailto:surendra.manchika...@gmail.com<mailto:surendra.manchika...@gmail.com>] Sent: Tuesday, February 09, 2016 3:44 PM To: user@hive.apache.org<mailto:user@hive.apache.org> Subject: Re: Hive Permanent functions not working after a cluster restart. Hi, What's your meta store DB. Is it Derby (Internal) or external Database? Regards, Surendra M On Fri, Feb 5, 2016 at 10:07 AM, Chagarlamudi, Prasanth <prasanth.chagarlam...@epsilon.com<mailto:prasanth.chagarlam...@epsilon.com>> wrote: I created permanent functions(rather than temp functions) in Hive to use it across different sessions. It all works fine until I actually restart the hive server or cluster for any reason. So is this the intended functionality of Permanent functions? Here is the hive doc link for Permanent functions. https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Create/Drop/ReloadFunction 1) Placed my utils jar for hive in hdfs location hdfs:///opt/myUtiljars/myUtil.jar 2) Create function schemaName.myFunctName as ‘com.myclass.name<http://com.myclass.name>’ using ‘hdfs:///opt/myUtiljars/myUtil.jar’ 3) Select schemaName.myFunctName() from tableName; This is what I did to create a permanent function through beeline. And this is working fine in other beeline sessions as well. Now after I restart the servers I was able to see the functions name in “show functions;” command but I cannot use this function in any of my queries. When I issue the command in 3) Error: Error while compiling statement: FAILED: SemanticException Line 0:-1 Invalid function schemaName.myFunctName ' (state=42000,code=40000) I would like to create Permanent functions as mentioned above and I don’t want to deal with them every time I restart. Any corrections(if I am missing anything) or suggestion are greatly appreciated. Thanks in advance Prasanth Chagarlamudi ________________________________ This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You. ________________________________ This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You. ________________________________ This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You.
