[
https://issues.apache.org/jira/browse/FLINK-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902558#comment-15902558
]
ASF GitHub Bot commented on FLINK-5980:
---------------------------------------
Github user ifndef-SleePy commented on the issue:
https://github.com/apache/flink/pull/3487
Thank you, Stephan and zentol.
Good question and suggestion. I didn't consider it too much for batch jobs.
Also I think it's a bad idea that naming the variable "numberOfKeyGroups"
in TaskInfo. Keeping max-parallelism is better. It's more common and makes much
more sense for other scenarios.
I will make sure it can work with batch jobs, and update this PR later.
> 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)
