[
https://issues.apache.org/jira/browse/HIVE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Lee updated HIVE-309:
-----------------------------
Attachment: hive-external-functions5.diff
How embarrasing. I uploaded the same patch twice. Too many version control
systems...
This patch should have all of the files this time.
As far as the implementation debate, naturally i prefer my implementation to a
metastore implementation... but I'm not totally against a metastore based
solution. My only requirement is that adding/changing UDFs be easily
automatable. Essentially, we have a continuous integration system which
produce distributions with a build name. We "roll out" builds via a simple
rollout script.... and at the moment all it does is modify a symlink which
changes the directory HIVE_AUX_JARS_PATH points at to a specific build. If we
ever enable the web client, the rollout script will also be responsible for
restarting the hive server.
> 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.