[
https://issues.apache.org/jira/browse/TAJO-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385855#comment-14385855
]
Hyunsik Choi commented on TAJO-1344:
------------------------------------
Basing on the current implementation, I suggested the first option. After
TAJO-1436, you can choose the second option.
I think the following points:
* The conventional wisdom is that the constructor should be lightweight.
* function invocation implementation is only used in worker in order to
evaluate expressions.
* But, if function invocation implementation is initialized in the
constructor, the initialization will be repeated several times in the following
steps:
* in logical planner
* after plan deserialization in query master
* after plan deserialization in task runner
> Python UDF support
> ------------------
>
> Key: TAJO-1344
> URL: https://issues.apache.org/jira/browse/TAJO-1344
> Project: Tajo
> Issue Type: New Feature
> Components: function/udf
> Reporter: Hyunsik Choi
> Assignee: Jihoon Son
> Fix For: 0.11.0
>
> Attachments: TAJO-1344.patch, TAJO-1344_2.patch, TAJO-1344_3.patch,
> TAJO-1344_4.patch
>
>
> Python has abundant users and third-party libraries. This language is widely
> used in data analytic area. So, it would be great if Tajo supports Python UDF.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
