[
https://issues.apache.org/jira/browse/FLINK-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790633#comment-14790633
]
ASF GitHub Bot commented on FLINK-2689:
---------------------------------------
GitHub user fhueske opened a pull request:
https://github.com/apache/flink/pull/1136
[FLINK-2689] [runtime] Fix reuse of null object for solution set Joins and
CoGroups
Reuse object can become null if not match is found in the hash table. The
next look-up will happen with a null-valued reuse object and fail.
This patch takes care that the reuse object does not become null.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fhueske/flink solutionSetJoinFix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1136.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1136
----
commit aa223335af19c5ff779c5f689a7f26cd8732c705
Author: Fabian Hueske <[email protected]>
Date: 2015-09-16T14:56:06Z
[FLINK-2689] [runtime] Fix reuse of null object for solution set Joins and
CoGroups.
----
> Reusing null object for joins with SolutionSet
> ----------------------------------------------
>
> Key: FLINK-2689
> URL: https://issues.apache.org/jira/browse/FLINK-2689
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime
> Affects Versions: 0.9, 0.10
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Fix For: 0.10, 0.9.2
>
>
> Joins and CoGroups with a solution set have outer join semantics because a
> certain key might not have been inserted into the solution set yet. When
> probing a non-existing key, the CompactingHashTable will return null.
> In object reuse mode, this null value is used as reuse object when the next
> key is probed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
