[
https://issues.apache.org/jira/browse/TAJO-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14449251#comment-14449251
]
Keuntae Park edited comment on TAJO-1517 at 4/6/15 1:15 AM:
------------------------------------------------------------
Thank you for the kind comment, [~hyunsik]
I agree with your advice about INTERSECT ALL
and going to start this issue with implementation of physical operator.
Then, I'll update GlobalPlanner and LogicalPlanner to support INTERSECT.
In my plan, INTERSECT would be implemented by INTERSECT ALL + distinct.
was (Author: sirpkt):
Thank you for the kind comment, [~hyunsik]
I agree with your advice about ```INTERSECT ALL```
and going to start this issue with implementation of physical operator.
Then, I'll update GlobalPlanner and LogicalPlanner to support INTERSECT.
In my plan, INTERSECT would be implemented by INTERSECT ALL + distinct.
> Implement INTERSECT
> -------------------
>
> Key: TAJO-1517
> URL: https://issues.apache.org/jira/browse/TAJO-1517
> Project: Tajo
> Issue Type: Sub-task
> Reporter: Keuntae Park
>
> {code}
> query1 INTERSECT [ALL] query2
> {code}
> INTERSECT returns all rows that are both in the result of query1 and in the
> result of query2.
> Duplicate rows are eliminated unless INTERSECT ALL is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
