[
https://issues.apache.org/jira/browse/TAJO-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150045#comment-15150045
]
ASF GitHub Bot commented on TAJO-1686:
--------------------------------------
Github user eminency commented on a diff in the pull request:
https://github.com/apache/tajo/pull/929#discussion_r53128977
--- Diff: tajo-core/src/main/java/org/apache/tajo/worker/TajoWorker.java ---
@@ -200,6 +200,7 @@ public void serviceInit(Configuration conf) throws
Exception {
historyReader = new HistoryReader(workerContext.getWorkerName(),
this.systemConf);
FunctionLoader.loadUserDefinedFunctions(systemConf);
+ HiveFunctionLoader.loadHiveUDFs(systemConf);
--- End diff --
If any duplicate exists, it is already designed to raise
AmbiguousFunctionException.
So this point might be skipped.
> Allow Tajo to use Hive UDF
> --------------------------
>
> Key: TAJO-1686
> URL: https://issues.apache.org/jira/browse/TAJO-1686
> Project: Tajo
> Issue Type: New Feature
> Components: Function/UDF
> Reporter: Jaehwa Jung
> Assignee: Jongyoung Park
>
> Hive has been widely used in this area. Many users have maintained lots of
> big tables through Hive metastore using HiveQL and UDFs. Currently, Tajo
> provides own UDF and Hive users can implement their UDFs in Tajo. But if we
> can wrap Hive UDF in Tajo, it seems that they would be able to use Tajo
> easily for their analysis infrastructure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)