[
https://issues.apache.org/jira/browse/TAJO-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636308#comment-13636308
]
Alexander Sibetheros commented on TAJO-34:
------------------------------------------
I searched through the files mentioned above but was unable to find where Inner
Join was implemented. Could someone point me towards that direction(Function
name) so I can figure out how much work is needed in order to implement Outer
Join. Also I have not been able to find the parser mentioned.
> Outer Join
> ----------
>
> Key: TAJO-34
> URL: https://issues.apache.org/jira/browse/TAJO-34
> Project: Tajo
> Issue Type: New Feature
> Reporter: Hyunsik Choi
> Labels: gsoc, gsoc2013, join, mentor
>
> h3. Background
> The current Tajo does not support outer join. The parser part for outer join
> was already implemented.
> h3. Proposal
> In this issue, we should improve LogicalPlanner/LogicalOptimizer to deal with
> outer joins. Then, we should adopt outer join to existing physical join
> operators like HashJoinExec and MergeJoinExec.
--
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
