[
https://issues.apache.org/jira/browse/FLINK-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803314#comment-14803314
]
ASF GitHub Bot commented on FLINK-2689:
---------------------------------------
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1136#issuecomment-141168778
Hi @srowen, thank you for notifying us. We were trying out
https://github.com/databricks/spark-pr-dashboard on Google App Engine (because
we are also getting more and more flooded by pull requests ;) ). It seems that
we didn't properly configure and test the tool before starting it.
After you told us about the issue, we immediately stopped the tool. You can
also see from Max (@mxm)'s JIRA activity
(https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mxm) that he
stopped changing Spark JIRAs.
I'm really sorry that this has happened.
We'll manually clean up the Spark JIRAs.
> 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.9, 0.10
>
>
> 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)
