On 15.09.20 07:00, Xuannan Su wrote:
Thanks for your comment. I agree that we should not introduce tight coupling with PipelineExecutor to the execution environment. With that in mind, to distinguish the per-job and session mode, we can introduce a new method, naming isPerJobModeExecutor, in the PipelineExecutorFactory or PipelineExecutor so that the execution environment can recognize per-job mode without instanced checks on the PipelineExecutor. What do you think? Any thoughts or suggestions are very welcome.
I think this would just sidestep the problem. Can't we just ignore it? With per-job mode the cache will not be there and the program will fall back to re-execute the whole graph. That shouldn't be a problem.
Best, Aljoscha
