[
https://issues.apache.org/jira/browse/FLINK-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289713#comment-17289713
]
Robert Metzger commented on FLINK-12607:
----------------------------------------
Sorry for my delayed response.
Yes, you can set maxParallelism for an entire streaming job + on individual
operators.
I don't fully understand why you are suggesting to call it
"job-max-parallelism", instead of "max-parallelism". Isn't it clear from the
REST endpoint name that this is scoped to the job, and not a vertex?
For testing: I would just recommend extending the existing REST endpoint tests.
Overall, the change looks pretty good already, I guess you can open a PR soon,
so that we can do a line-by-line review.
> 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: starter
>
> 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.3.4#803005)
