Hi Do,
the easiest way is to avoid using methods which trigger an eager execution
(collect, count, print) but to define sinks instead. Alternatively, you can
persist intermediate results by writing them to disk and continue
processing from there. That way, you won't re-calculate all parts of your
Hi all,
Right now, in Flink, if I call to 2 action operators (print, count,
collect, ) consecutively, Flink will create 2 independent execution plans.
A simple example:
DataSet text = env.fromElements(
"Some text ….",
);
