Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Tue, 24 Sep 2013 15:40:02 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12642681.1366101909605.9766.1380037202447@arcas>
In-Reply-To: <JIRA.12642681.1366101909605@arcas>
References: <JIRA.12642681.1366101909605@arcas>
Subject: [jira] [Assigned] (TAJO-34) Outer Join
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hyunsik Choi reassigned TAJO-34:
--------------------------------

    Assignee: camelia c
    
> Outer Join
> ----------
>
>                 Key: TAJO-34
>                 URL: https://issues.apache.org/jira/browse/TAJO-34
>             Project: Tajo
>          Issue Type: New Feature
>            Reporter: Hyunsik Choi
>            Assignee: camelia c
>              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