flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2106) Add outer joins to API, Optimizer, and Runtime
Date Wed, 26 Aug 2015 08:52:46 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712732#comment-14712732

ASF GitHub Bot commented on FLINK-2106:

Github user fhueske commented on the pull request:

    @r-pogalz I would implement API and optimizer together in one issue. IMO it is easier
to start from the API and then work your way through API to optimizer and finally use your
runtime code. However, you cannot add the API without adding the optimizer part. So, I would
do both in one issue.

> 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

View raw message