[jira] [Commented] (FLINK-12607) Introduce a REST API that returns the maxParallelism of a job

["Congxian Qiu(klion26) (JIRA)" <ji...@apache.org>]

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

Congxian Qiu(klion26) commented on FLINK-12607:
-----------------------------------------------

Thanks for filing the issue, I like this improvement, so that people can know this metric easily.

Before this improvement, I think we can calculate this by using the formula in the doc[1]

[1][https://ci.apache.org/projects/flink/flink-docs-stable/ops/production_ready.html#set-maximum-parallelism-for-operators-explicitly]

> 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
>            Priority: Minor
>
> 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
(v7.6.3#76005)