[
https://issues.apache.org/jira/browse/FLINK-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679090#comment-14679090
]
Fabian Hueske commented on FLINK-2106:
--------------------------------------
A driver manages the different physical execution strategies of one operation
and should not perform semantically different operations.
So I would choose option 2, i.e., adding three drivers (just as you listed) and
three new DriverStrategies:
* `LEFT_OUTER_MERGE`
* `RIGHT_OUTER_MERGE`
* `FULL_OUTER_MERGE`
and also rename `MERGE` to `INNER_MERGE`.
> Add outer joins to API, Optimizer, and Runtime
> ----------------------------------------------
>
> Key: FLINK-2106
> URL: https://issues.apache.org/jira/browse/FLINK-2106
> Project: Flink
> Issue Type: Sub-task
> Components: Java API, Local Runtime, Optimizer, Scala API
> Reporter: Fabian Hueske
> Assignee: Ricky Pogalz
> Priority: Minor
> Fix For: pre-apache
>
>
> Add left/right/full outer join methods to the DataSet APIs (Java, Scala), to
> the optimizer, and the runtime of Flink.
> Initially, the execution strategy should be a sort-merge outer join
> (FLINK-2105) but can later be extended to hash joins for left/right outer
> joins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
