[
https://issues.apache.org/jira/browse/TAJO-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385714#comment-14385714
]
ASF GitHub Bot commented on TAJO-1344:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/473#issuecomment-87399705
@hyunsik, thanks for the nice suggestion. It is definitely a better
solution.
However, I have a different opinion on detailed implementation.
The first option that initialize each function invocation implementation at
the first function call is deprecated, so it is not a good choice.
And the second option using EvalNode::Bind() seems to initialize
schema-dependent variables. Even though we still can change the specification
of TAJO-1436, the current one looks good. Since relations have different
schemas, schema-dependent variables should be initialized for each schema.
However, function invocation implementation does not depend on relations'
schema. I think that it would be better to initialize when an instance of
```FunctionEval``` is created.
What do you think?
> 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)
