Hi Bart,
yup, this is a bug. AFAIK it is now known, would you like to open the Jira
issue for it? If not, I can also open one.
The problem is in the interaction of how chaining works in the streaming
API with object reuse. As you said, with how it is implemented it serially
calls the two map funct
(For reference, I'm in 1.0.3)
I have a job that looks like this:
DataStream input = ...
input
.map(MapFunction...)
.addSink(...);
input
.map(MapFunction...)
?.addSink(...);
If I do not call enableObjectReuse() it works, if I do call enableObjectReuse()
it throws:
java
