You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (JIRA)" <ji...@apache.org> on 2019/05/31 13:42:00 UTC
[jira] [Updated] (FLINK-12691) Make Queue Capacity and Timeout of
AsyncWaitOperator changeable during runtime
[ https://issues.apache.org/jira/browse/FLINK-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Knauf updated FLINK-12691:
-------------------------------------
Description:
A user that I have recently been working with has the requirement to change the capacity and possibly the timeout during the runtime of a job.
-Conceptually, this should be possibly by just passing these parameters to the {{RichAsyncFunction}} via its RuntimeContext. The change of the timeout would only apply to future records and the change in the queue capacity would take effect immediately.
-
was:
A user that I have recently been working with has the requirement to change the capacity and possibly the timeout during the runtime of a job.
~Conceptually, this should be possibly by just passing these parameters to the {{RichAsyncFunction}} via its RuntimeContext. The change of the timeout would only apply to future records and the change in the queue capacity would take effect immediately.~
> Make Queue Capacity and Timeout of AsyncWaitOperator changeable during runtime
> ------------------------------------------------------------------------------
>
> Key: FLINK-12691
> URL: https://issues.apache.org/jira/browse/FLINK-12691
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Reporter: Konstantin Knauf
> Priority: Minor
>
> A user that I have recently been working with has the requirement to change the capacity and possibly the timeout during the runtime of a job.
> -Conceptually, this should be possibly by just passing these parameters to the {{RichAsyncFunction}} via its RuntimeContext. The change of the timeout would only apply to future records and the change in the queue capacity would take effect immediately.
> -
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)