Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/988#issuecomment-131892889
I changed it to execute dangling operators now. There is, however, a
strange "feature". This code works on master:
https://gist.github.com/aljoscha/bbe74309a31a16ca8413. It catches away the
exception that results from not being able to determine the output type of the
generic map. Then, when execute is called it executes just fine up until (and
including) the generic map as can be seen from the `println` output.
With this PR this won't work anymore. The upon `execute` the the
StreamGraphBuilder tries to build the StreamGraph from the graph of
Transformations. It encounters the dangling map for which the output type
cannot be determined and then it fails.
This behavior is problematic since the TestStreamEnvironment is reused for
several streaming tests. Tests fail in seemingly unconnected parts of the code
because dangling operators without type information still linger in the
execution environment. I mentioned this here:
https://issues.apache.org/jira/browse/FLINK-2508
I have a quick fix for this, for now. I think, however, that the streaming
tests need to be consolidated and the streaming environments also need to be
refactored a bit. (In addition to the batch exec envs, because they should
probably be reused in large parts for streaming.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
