[
https://issues.apache.org/jira/browse/FLINK-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865514#comment-16865514
]
Aljoscha Krettek commented on FLINK-12691:
------------------------------------------
I think this is a tricky one. In order to allow changing configuration based on
received events, we would have to add some interface that allows observing
received events and to then effect some change in configuration.
One thing that comes to mind is to add a new interface
{{AsyncObserverFunction}} (or something like it) that can observe records being
received and also gets an interface that allows changing configuration. After
introducing this, we would need to make changes to the queue and timeout (and
potentially other parameters), which are currently final, or instantiated when
the operator is brought up.
> 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)
