yes, But since the jobName is passed, it already passes through a long call chain. You mean that you suggest that I refactor these methods, add a parameter and pass the jobDescription in the batch call chain: `execution -> createProgramPlan -> createProgramPlan - > translateToPlan` instead of using properties? The main consideration is: ExecutionConfig is only used to store information that the Task must read at runtime?
[ Full content available at: https://github.com/apache/flink/pull/6266 ] This message was relayed via gitbox.apache.org for [email protected]
