You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/10/02 09:10:33 UTC
[jira] [Created] (TAJO-1092) Improve the function system to allow
other function implementation types
Hyunsik Choi created TAJO-1092:
----------------------------------
Summary: 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
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)