Re: [DISCUSS] FLIP-304: Pluggable failure handling for Apache Flink

Hello again everyone, FLIP is now updated based on our discussion! In short, FLIP-304 [1] proposes the addition of a pluggable interface that will allow users to add custom logic and enrich failures with custom metadata labels. While as discussed, custom restart strategies will be part of a differ

Re: [DISCUSS] FLIP-302: Support TRUNCATE TABLE statement

1: Actaully, considering the Flink's implementation, Flink just provides Truncate Table syntax to help user simlify data management as said in this FLIP and push the implementation of Truncate Table to external connector. Normally, the effect of TRUENCATE TABLE is same as Drop Table + Create Ta

[jira] [Created] (FLINK-31757) Optimize Flink tasks un-balanced scheduling

RocMarshal created FLINK-31757: -- Summary: Optimize Flink tasks un-balanced scheduling Key: FLINK-31757 URL: https://issues.apache.org/jira/browse/FLINK-31757 Project: Flink Issue Type: Improveme

[DISCUSS] FLIP-305: Support atomic for CREATE TABLE AS SELECT(CTAS) statement

Hi, everyone I'd like to start a discussion about FLIP-305: Support atomic for CREATE TABLE AS SELECT(CTAS) statement [1]. CREATE TABLE AS SELECT(CTAS) statement has been support, but it's not atomic. It will create the table first before job running. If the job execution fails, or is ca