+1 Thanks for driving this,It makes the REST API that runs the job more powerful and complete
Best JasonLee ---- Replied Message ---- | From | zhengyu chen<jam.gz...@gmail.com> | | Date | 08/15/2022 18:06 | | To | <dev@flink.apache.org> | | Subject | [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api | Hi all, We would like to start a discussion thread on FLIP-256 Support Job Dynamic Parameter With Flink Rest Api <https://cwiki.apache.org/confluence/display/FLINK/FLIP-256+Support+Job+Dynamic+Parameter+With+Flink+Rest+Api> [1] After the user submits the jar package, running a job through restapi (/jars/:jarid/run) [2] can only pass in (allowNonRestoredState, savepointPath, programArg, entry-class, parallelism) parameters, which is obvious with the diversification of job parameters (eg Checkpoint address) This solves the problem that the user can pass in other parameters when submitting a job, avoiding the user to define these job parameters in the code, resulting in the need to repackage the job for each modification There was some interest from users [3] from a meetup and the mailing list. Looking forward to comments and feedback, thanks! [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-256+Support+Job+Dynamic+Parameter+With+Flink+Rest+Api [2] https://nightlies.apache.org/flink/flink-docs-master/docs/ops/rest_api/#jars-jarid-run [3] https://issues.apache.org/jira/browse/FLINK-27060 -- Best ConradJam
