[
https://issues.apache.org/jira/browse/FLINK-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849983#comment-16849983
]
Akshay Kanfade commented on FLINK-12607:
----------------------------------------
[~till.rohrmann]. Yes, I will be happy to work on it and will start working on
this soon(mostly next week). And yes, for the first approach, I was planning to
add it to the JobVertexDetailsInfo.
[~klion26] Thank you for your inputs. About the implementation, I had a brief
look at the code workflow before filing this issue and thought this might just
be a single line change here -
[https://github.com/apache/flink/blob/4caec0d4bab497d7f9a8d9fec4680089117593df/flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/job/JobVertexDetailsHandler.java#L153]
ExecutionJobVertex has maxParallelism as a member. However, I haven't verified
that it is set. But, I hope so because that's what gets utilized while taking
decisions for savepoint compatibility -
[https://code.amazon.com/packages/AWSKinesisAnalyticsFlink/blobs/89d206c99990f35826f2c25bfac99f47953f3ff7/--/third-party-src/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/Checkpoints.java#L177]
So, I guess we don't have to write any logic to determine the maxParallelism
for this change. Anyways, I will confirm once I start working on 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
> 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)
