tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-177) Call by reference bug in MergeJoinExec
Date Tue, 10 Sep 2013 11:03:51 GMT

    [ https://issues.apache.org/jira/browse/TAJO-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762951#comment-13762951
] 

Jihoon Son commented on TAJO-177:
---------------------------------

When MemSortExec is used as inputs, MergeJoinExec works well.

However, ExternalSortExec is used as inputs, using call by reference leads unexpected operations.
                
> Call by reference bug in MergeJoinExec
> --------------------------------------
>
>                 Key: TAJO-177
>                 URL: https://issues.apache.org/jira/browse/TAJO-177
>             Project: Tajo
>          Issue Type: Bug
>          Components: physical operator
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>             Fix For: 0.2-incubating
>
>
> While comparing and storing tuples in a list temporally, their copies should be stored.
> This issue includes following works
> * Create a function clone() in Tuple and VTuple
> * Change from using call by reference to using call by value

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message