You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/01/22 08:10:20 UTC

[jira] [Work started] (TAJO-539) Change some EvalNode::eval to directly return a Datum value

     [ https://issues.apache.org/jira/browse/TAJO-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on TAJO-539 started by Hyunsik Choi.

> Change some EvalNode::eval to directly return a Datum value
> -----------------------------------------------------------
>
>                 Key: TAJO-539
>                 URL: https://issues.apache.org/jira/browse/TAJO-539
>             Project: Tajo
>          Issue Type: Improvement
>          Components: operator/expression
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>
> After TAJO-501, we can ensure that all expressions except for AggregationFunctionCallEval can be evaluated by calling once eval() instead of calling eval followed by terminate. In addition, current EvalNode implementation involves unnecessary memory consumption to keep EvalContext for all expressions which are not even aggregation eval. 
> If we change EvalNode::eval() to directly return a Datum value, it would be reduce the memory consumption and CPU costs.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)