[
https://issues.apache.org/jira/browse/HADOOP-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630556#action_12630556
]
Tom White commented on HADOOP-4070:
-----------------------------------
Thanks for all your feedback. I'm working on a test case.
The reason I called it AdminWork was because I was following the terminology
used in MySQL. "DDLWork" and "DDLFunctionsWork" don't sound right as function
creation is not really a part of DDL. I can rename it something more specific -
CreateFunctionWork?
I agree that it would be good to make the mapping persistent, and add drop and
rename, but these can be done in later Jiras.
{quote}
The reason for that code was that user could specify the list of auxiliary jars
in hive-default.xml (and also by setting the hive.aux.jars.path in hive command
line client as a session variable). In which case GenericOptionsParser code
doesn't work. I think appending 'file://' is new to 19.
{quote}
Not sure about that, but HADOOP-3743 certainly changed things in that area. The
problem is that if you set the variable HIVE_AUX_JARS_PATH to say /foo then the
session variable hive.aux.jars.path is set to /foo by the hive script, rather
than file:///foo. So I've been overriding this by redefining the session
variable at the moment. What's the best way of fixing this?
> [Hive] Provide a mechanism for registering UDFs from the query language
> -----------------------------------------------------------------------
>
> Key: HADOOP-4070
> URL: https://issues.apache.org/jira/browse/HADOOP-4070
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/hive
> Reporter: Tom White
> Attachments: hadoop-4070.patch
>
>
> UDFs (user defined functions) in Hive are currently actually built-in
> functions. This issue is to develop a packaging and registration mechanism so
> users can add their own functions at runtime.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
