[
https://issues.apache.org/jira/browse/FLINK-29713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622561#comment-17622561
]
Peter Vary commented on FLINK-29713:
------------------------------------
The main goal is to have a possibility to add a new sink, when a new type of
data has arrived.
Imagine a job where the incoming data defines the sinks, like a Kafka topics or
a database tables. We start with a set of known data types. The main task will
create the appropriate topics and sinks based on the current known data types.
Later a new record arrives with a new type which needs a new sink. The job
needs to be reconfigured and a new sink needs to be added.
This way the Flink job can dynamically adjust itself to handle the incoming
data.
> Kubernetes operator should restart failed jobs
> ----------------------------------------------
>
> Key: FLINK-29713
> URL: https://issues.apache.org/jira/browse/FLINK-29713
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Fix For: kubernetes-operator-1.3.0
>
>
> It would be good to have the possibility to restart the Flink Application if
> it goes to {{FAILED}} state.
> This could be used to restart, and reconfigure the job dynamically in the
> application {{main}} method if the current application can not handle the
> incoming data
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
