[ 
https://issues.apache.org/jira/browse/HIVE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695603#action_12695603
 ] 

Ashish Thusoo commented on HIVE-309:
------------------------------------

I see your use case Richard. I think a more reasonable approach - which Prasad 
mentioned  is that we could extend the UDF api to give out all the meta 
information about that particular UDF and use that to create the registration 
table. That way, jars are truely plug and play. To me creating a .properties is 
just creating another repository for metadata. I think we should either store 
the metadata with the object itself (as in the approach mentioned here) or for 
a repository use the metastore. Does this sound more reasonable Richard?


> FunctionRegistry should allow loading UDFs and UDAFs from property file
> -----------------------------------------------------------------------
>
>                 Key: HIVE-309
>                 URL: https://issues.apache.org/jira/browse/HIVE-309
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Richard Lee
>            Assignee: Richard Lee
>         Attachments: hive-external-functions-2.diff, 
> hive-external-functions.diff, hive-external-functions2.diff, 
> hive-external-functions3.diff, hive-external-functions4.diff, 
> hive-external-functions5.diff
>
>
> FunctionRegistry.java hard code all UDF, UDAF definitions in a static 
> initializer.  There is no way to add new functions without directly modifying 
> this file.  
> FunctionRegistry SHOULD look for a property file in which new functions and 
> their implementations can be specified.  This will allow third parties to 
> extend hive without maintaining patches against the codebase. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to