[RESULT][VOTE] FLIP-323: Support Attached Execution on Flink Application Completion for Batch Jobs
Hi Everyone, Thank you for the review and votes, am happy to announce that FLIP-323<https://cwiki.apache.org/confluence/display/FLINK/FLIP-323%3A+Support+Attached+Execution+on+Flink+Application+Completion+for+Batch+Jobs> has been accepted. There are 9 votes, 3 binding and 6 nonbinding, no disapproving votes.<https://lists.apache.org/thread/26o276cttnv226rr7w1ro6vsz3hq07nq> Venkatakrishnan Sworirajan Dong Lin *Binding Jing Ge *binding Weihua Hu *binding Ahmed Hamdy Samrat Deb Matt Wang Liu Ron Conrad Jam Best, Allison Chang
[VOTE] FLIP-323: Support Attached Execution on Flink Application Completion for Batch Jobs
Hi everyone, Would like to start the VOTE for FLIP-323<https://cwiki.apache.org/confluence/display/FLINK/FLIP-323%3A+Support+Attached+Execution+on+Flink+Application+Completion+for+Batch+Jobs> which proposes to introduce attached execution for batch jobs. The discussion thread can be found here<https://lists.apache.org/thread/d3toldk6qqjh2fnbmqthlfkj9rc6lwgl>: Best, Allison Chang
[jira] [Created] (FLINK-32875) Enable limiting number of retained jobs for the local job archive directory in flink history server
Allison Chang created FLINK-32875: - Summary: Enable limiting number of retained jobs for the local job archive directory in flink history server Key: FLINK-32875 URL: https://issues.apache.org/jira/browse/FLINK-32875 Project: Flink Issue Type: New Feature Affects Versions: 1.16.1 Reporter: Allison Chang Fix For: 1.18.0 Currently the Flink history server limits the number of job archives stored using the history.server.retained-jobs configuration, which sets the limit for both the local cache as well as remote directories. We want to decouple the local cache limit from the remote directory which stores the job archives so that we are not limited by the size of a local filesystem where Flink History server is deployed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[DISCUSS] FLIP-323: Support Attached Execution on Flink Application Completion for Batch Jobs
Hi all, I am opening this thread to discuss this proposal to support attached execution on Flink Application Completion for Batch Jobs. The link to the FLIP proposal is here: https://cwiki.apache.org/confluence/display/FLINK/FLIP-323%3A+Support+Attached+Execution+on+Flink+Application+Completion+for+Batch+Jobs This FLIP proposes adding back attached execution for Application Mode. In the past attached execution was supported for the per-job mode, which will be deprecated and we want to include this feature back into Application mode. Please reply to this email thread and share your thoughts/opinions. Thank you! Allison Chang
[jira] [Created] (FLINK-31981) Enabling waiting on the Flink Application to complete before returning to Flink client for batch jobs
Allison Chang created FLINK-31981: - Summary: Enabling waiting on the Flink Application to complete before returning to Flink client for batch jobs Key: FLINK-31981 URL: https://issues.apache.org/jira/browse/FLINK-31981 Project: Flink Issue Type: New Feature Components: Deployment / YARN Affects Versions: 1.16.1 Reporter: Allison Chang Fix For: 1.16.2 Currently the Flink Client by default will immediately complete when it hits RUNNING state - we want to make it configurable for batch jobs so that the client only completes when the flink application has fully completed running, rather than just returning upon submission of the job. This allows us to have richer information about whether the underlying application has completed successfully or failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
