[
https://issues.apache.org/jira/browse/FLINK-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899353#comment-15899353
]
ASF GitHub Bot commented on FLINK-5980:
---------------------------------------
GitHub user ifndef-SleePy opened a pull request:
https://github.com/apache/flink/pull/3487
[FLINK-5980] Expose max-parallelism value in RuntimeContext.
Add new method named getMaxParallelismOfSubtasks in RuntimeContext.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alibaba/flink jira-5980
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3487.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3487
----
commit b7844d43d053d447a905fa727916683e06ec583d
Author: biao.liub <[email protected]>
Date: 2017-03-07T12:11:10Z
[FLINK-5980] Expose max-parallelism value in RuntimeContext.
----
> Expose max-parallelism value in RuntimeContext
> ----------------------------------------------
>
> Key: FLINK-5980
> URL: https://issues.apache.org/jira/browse/FLINK-5980
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Reporter: Biao Liu
> Assignee: Biao Liu
> Priority: Minor
>
> I am implementing a custom source function. I want to keep all progresses in
> a ListState to support dynamically scaling just like what FlinkKafkaConsumer
> did. And I think the max-parallelism value is ideal length for the ListState
> in my scenario. But I realize that currently the max-parallelism value is not
> visible to UDF.
> I propose exposing the max-parallelism value in RuntimeContext. It will be
> useful in dynamically scaling scenario.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
