[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:
-
Labels: (was: auto-closed)
Priority: Not a Priority (was: Minor)
> 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: Not a Priority
>
> 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
(v8.3.4#803005)
[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
]
Flink Jira Bot updated FLINK-12691:
---
Labels: auto-closed (was: stale-minor)
> 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
> Labels: auto-closed
>
> 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
(v8.3.4#803005)
[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
]
Flink Jira Bot updated FLINK-12691:
---
Labels: stale-minor (was: )
> 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
> Labels: stale-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
(v8.3.4#803005)
[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)
[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)
[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)
