[
https://issues.apache.org/jira/browse/FLINK-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853028#comment-16853028
]
Konstantin Knauf commented on FLINK-12691:
------------------------------------------
[~yanghua] I thought about this again and a) it is not as easy as I thought and
b) from an API perspective the {{RuntimeContext}} would probably also not be
nice, because it generally does not contain operator specific methods.
Optimally, we would have a dedicated {{Context}}, which was passed to
{{asyncInvoke}}, but this would break the API. Any ideas?
> 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)
