You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2013/09/10 13:03:51 UTC
[jira] [Commented] (TAJO-177) Call by reference bug in
MergeJoinExec
[ 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