[
https://issues.apache.org/jira/browse/FLINK-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652044#comment-14652044
]
ASF GitHub Bot commented on FLINK-2105:
---------------------------------------
Github user r-pogalz commented on the pull request:
https://github.com/apache/flink/pull/907#issuecomment-127293419
Hello @fhueske,
I see you noticed that we replaced all occurrences of `Record` by
`Tuple2<Integer, String>` in the InnerJoin- and OuterJoinITCases. The issue is
that we did not yet adapt the other tests (~15 test classes) using the
`TestData.Generator`. That's why we currently added a second Generator
(`TestData.TupleGenerator`) for our purposes without the usage of `Record`. But
I think it would be good to replace the old `TestData.Generator` by the new one
and adapt all usages at some point in the future.
> Implement Sort-Merge Outer Join algorithm
> -----------------------------------------
>
> Key: FLINK-2105
> URL: https://issues.apache.org/jira/browse/FLINK-2105
> Project: Flink
> Issue Type: Sub-task
> Components: Local Runtime
> Reporter: Fabian Hueske
> Assignee: Ricky Pogalz
> Priority: Minor
> Fix For: pre-apache
>
>
> Flink does not natively support outer joins at the moment.
> This issue proposes to implement a sort-merge outer join algorithm that can
> cover left, right, and full outer joins.
> The implementation can be based on the regular sort-merge join iterator
> ({{ReusingMergeMatchIterator}} and {{NonReusingMergeMatchIterator}}, see also
> {{MatchDriver}} class)
> The Reusing and NonReusing variants differ in whether object instances are
> reused or new objects are created. I would start with the NonReusing variant
> which is safer from a user's point of view and should also be easier to
> implement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
