[
https://issues.apache.org/jira/browse/TAJO-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159362#comment-14159362
]
ASF GitHub Bot commented on TAJO-1092:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/178
TAJO-1092: Improve the function system to allow other function
implementation types.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1092
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/178.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #178
----
commit 149b92afe0d5a2903ddd55b4e788482e3344477b
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-04T22:23:10Z
TAJO-1092: Improve the function system to allow other function
implementation types.
commit 6df2f9f4d7c38f751b761f9dbdd224cc3c89b2ad
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-04T22:23:37Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into
TAJO-1092
commit f6fe193152dc8a121def75b925bdde0e102a2cac
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-05T00:09:49Z
Refactored code generation for function binding.
* Moved some methods to TajoGeneratorAdaptor.
* Refactored method signatures of isMatched and isCompatible.
* Fixed unit test bugs of TestEvalCodeGenerator.
----
> Improve the function system to allow other function implementation types
> ------------------------------------------------------------------------
>
> Key: TAJO-1092
> URL: https://issues.apache.org/jira/browse/TAJO-1092
> Project: Tajo
> Issue Type: Improvement
> Components: function/udf
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.9.1, block_iteration
>
>
> In the current function system, each function implementation is a single Java
> class subclassed from org.apache.tajo.catalog.function.Function.
> In this approach, there are many rooms for improvement. This approach always
> uses Datum as input and output values of functions, creating unnecessary
> objects. It does not likely to exploit given information included query
> statements; for example, some parameters are constants or variables.
> In this issue, I propose the improvement to allow the function system to
> support other function implementation types. In addition, I propose three
> function implementation types:
> - legacy Java class function provided by the current Tajo
> - static method in Java class
> - code generation by ASM
> Later, we could expand this feature to allow Pig or Hive functions in Tajo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
