[
https://issues.apache.org/jira/browse/FLINK-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Hueske closed FLINK-2708.
--------------------------------
Resolution: Not A Problem
Thanks for opening this issue.
However, null values are actually fine in this case, because joining with a
solution set has outer join semantic and the join function must be able to
handle null values.
Thanks, Fabian
> Potential null pointer dereference in JoinWithSolutionSetFirstDriver#run()
> --------------------------------------------------------------------------
>
> Key: FLINK-2708
> URL: https://issues.apache.org/jira/browse/FLINK-2708
> Project: Flink
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Minor
>
> {code}
> while (this.running && ((probeSideRecord =
> probeSideInput.next(probeSideRecord)) != null)) {
> IT1 matchedRecord =
> prober.getMatchFor(probeSideRecord, buildSideRecord);
> joinFunction.join(matchedRecord,
> probeSideRecord, collector);
> }
> {code}
> The return value from getMatchFor() should be checked to avoid NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
