[
https://issues.apache.org/jira/browse/TAJO-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696392#comment-14696392
]
ASF GitHub Bot commented on TAJO-680:
-------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/620#discussion_r37046923
--- Diff:
tajo-plan/src/main/java/org/apache/tajo/plan/joinorder/JoinOrderingUtil.java ---
@@ -139,6 +141,11 @@ public static boolean
isAssociativeJoin(JoinGraphContext context, JoinEdge leftE
* (A full B) full C | A full (B full C) | Equivalent
* ==============================================================
*
+<<<<<<< HEAD
+ * Cross, Semi and Anti joins follow the rule of the Inner join.
+ *
+=======
+>>>>>>> c50a5dadff90fa90709abbce59856e834baa4867
--- End diff --
You may miss this line which seems to be inserted by git merge phase.
> Improve the IN operator to support sub queries
> ----------------------------------------------
>
> Key: TAJO-680
> URL: https://issues.apache.org/jira/browse/TAJO-680
> Project: Tajo
> Issue Type: Improvement
> Components: distributed query plan, SQL Parser
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Fix For: 0.11.0
>
> Attachments: Distributed plan.png, Logical plan.png
>
>
> Currently, the IN operator can be used with only sets of values.
> We need to improve it to support sub queries as the following example query.
> {noformat}
> tajo> select * from nation where n_regionkey in (select r_regionkey from
> region);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
