[
https://issues.apache.org/jira/browse/FLINK-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-202.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: pre-apache)
0.8.0
Solution set returns null on lookups of missing entries.
> Workset Iterations: "No Match Found" Behaviour of Solution Set Join
> -------------------------------------------------------------------
>
> Key: FLINK-202
> URL: https://issues.apache.org/jira/browse/FLINK-202
> Project: Flink
> Issue Type: Improvement
> Reporter: GitHub Import
> Labels: github-import
> Fix For: 0.8.0
>
>
> If I do a solution set match and there is no corresponding entry in the
> solution set index a RuntimeException is thrown and the job fails. Therefore
> the initial solution set must already contain every element which will be in
> the final solution set.
> I'm not sure if this is a real limitation, but I find it inconvenient. When I
> was playing around with the workset connected components I couldn't just use
> parts of my test data, because it resulted in a solution set join where
> records couldn't be matched.
> I just wanted to think out loudly here. Did anybody else find this
> inconvenient? What alternative should we provide?
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/202
> Created by: [uce|https://github.com/uce]
> Labels: core, enhancement,
> Created at: Wed Oct 23 23:24:29 CEST 2013
> State: open
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
