[jira] [Commented] (FLINK-29501) Allow overriding JobVertex parallelisms during job submission

["Chesnay Schepler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-29501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612640#comment-17612640 ] 

Chesnay Schepler commented on FLINK-29501:
------------------------------------------

Why can't this be handled within the application with a main method argument?

> Allow overriding JobVertex parallelisms during job submission
> -------------------------------------------------------------
>
>                 Key: FLINK-29501
>                 URL: https://issues.apache.org/jira/browse/FLINK-29501
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Configuration, Runtime / REST
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Minor
>
> It is a common scenario that users want to make changes to the parallelisms in the JobGraph. For example, because they discover that the job needs more or less resources. There is the option to do this globally via the job parallelism. However, for fine-tuned jobs jobs with potentially many branches, tuning on the job vertex level is required.
> This is to propose a way such that users can apply a mapping \{{jobVertexId => parallelism}} before the job is submitted without having to modify the JobGraph manually.
> One way to achieving this would be to add an optional map field to the Rest API jobs endpoint. However, in deployment modes like the application mode, this might not make sense because users do not have control the rest endpoint.
> Similarly to how other job parameters are passed in the application mode, we propose to add the overrides as a configuration parameter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)