[ https://issues.apache.org/jira/browse/FLINK-27060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539960#comment-17539960 ]
Martijn Visser commented on FLINK-27060: ---------------------------------------- [~ConradJam] I do think that this ticket should be included in the FLIP-91 discussion that's currently ongoing https://cwiki.apache.org/confluence/display/FLINK/FLIP-91%3A+Support+SQL+Gateway - I don't think this ticket can be picked up without that discussion being completed and voted on > Extending /jars/:jarid/run API to support setting Flink configs > --------------------------------------------------------------- > > Key: FLINK-27060 > URL: https://issues.apache.org/jira/browse/FLINK-27060 > Project: Flink > Issue Type: Improvement > Components: Runtime / REST > Reporter: Zhanghao Chen > Priority: Major > > *Background* > Users want to submit job via Flink REST API instead of Flink CLI which is > more heavy-weight in certain scenarios, for example, a lightweight data > processing workflow system that has Flink related systems. > Currently, the /jars/:jarid/run API > ([https://nightlies.apache.org/flink/flink-docs-master/docs/ops/rest_api/#jars-jarid-run)] > only supports a few selected Flink config options listed in the doc > (parallelism、savepoint path and allow non-restored state), which is > insufficient for practical use. > *Proposed Changes* > Extending the /jars/:jarid/run API with an additional request body parameter > "configs", which is a map of flink configuration option-value pairs set by > users. > For backward compatibility, we can retain the existing body parameters like > "allowNonRestoredState", and when there's conflicting configurations, let the > values set explicitly with existing body parameters take higher precedence > over the values set by configs. -- This message was sent by Atlassian Jira (v8.20.7#820007)