[ https://issues.apache.org/jira/browse/FLINK-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474400#comment-17474400 ]
zlzhang0122 commented on FLINK-12607: ------------------------------------- _The parameter of the ArchivedExecutionConfigBuilder.setMaxParallelism() maybe error, and I have created a [pr-18337|https://github.com/apache/flink/pull/18337] to fix it._ > Introduce a REST API that returns the maxParallelism of a job > ------------------------------------------------------------- > > Key: FLINK-12607 > URL: https://issues.apache.org/jira/browse/FLINK-12607 > Project: Flink > Issue Type: Improvement > Components: Runtime / REST > Affects Versions: 1.6.3 > Reporter: Akshay Kanfade > Assignee: John Phelan > Priority: Minor > Labels: pull-request-available, starter > Fix For: 1.13.0 > > > Today, Flink does not offer any way to get the maxParallelism for a job and > it's operators through any of the REST APIs. Since, the internal state > already tracks maxParallelism for a job and it's operators, we should expose > this via the REST APIs so that application developer can get more insights on > the current state. > There can be two approaches on how we can do this - > Approach 1 : > Modify the existing rest API response model to additionally expose a new > field 'maxParallelism'. Some of the REST APIs that would be affected by this > |h5. */jobs/:jobid/vertices/:vertexid*| > |h5. */jobs/:jobid*| > > Approach 2 : > Create a new REST API that would only return maxParallelism for a job and > it's operators. -- This message was sent by Atlassian Jira (v8.20.1#820001)