As far as I can tell, the only way the outputTargets in DistributedPipeline
get cleaned out is in MRPipeline.runAsync. If I were to bypass runAsync and
instead directly utilize MRPipeline.plan and MRExecutor.execute, would
there be ill effects if I wanted to continue to use that same pipeline to
run additional jobs?

Reply via email to