Hi Flink Community, Following the discussion on FLIP-528: Support EXPLAIN EXECUTE STATEMENT SET Syntax in Flink SQL, the proposal has been thoroughly discussed, and the main points have been addressed.
So, I'll be starting the voting process tomorrow. Please review the final version of the FLIP on the Flink Wiki: https://cwiki.apache.org/confluence/display/FLINK/FLIP-528%3A+Support+EXPLAIN+EXECUTE+STATEMENT+SET+Syntax+in+Flink+SQL Thank you to everyone who participated in the discussion and provided valuable feedback. Best regards, Ramin Gharib On Mon, Apr 28, 2025 at 1:03 PM Ramin Gharib <rgha...@confluent.io> wrote: > Hi Flink Community, > > I want to discuss FLIP-527: Support EXPLAIN EXECUTE STATEMENT SET Syntax > in Flink SQL. > > This FLIP proposes to extend the EXPLAIN statement in Flink SQL to > support the EXECUTE STATEMENT SET syntax. The goal is to provide users > with a way to understand the execution plan of a batch of SQL statements > before they are executed together. This will enhance debugging, > optimization, and overall understanding of how Flink processes a series of > dependent operations. > > You can find the full proposal details on the Flink Wiki at: > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-527%3A+Support+%60EXPLAIN+EXECUTE+STATEMENT+SET%60+Syntax+in+Flink+SQL > > > I'm eager to hear your thoughts, feedback, and potential concerns > regarding this proposal. > > Thanks, > > > Ramin Gharib > > [image: Confluent] <https://www.confluent.io> > > *Ramin Gharib *he/him/his > > Senior Software Engineer > > *Follow us: *[image: Blog] > <https://www.confluent.io/blog?utm_source=footer&utm_medium=email&utm_campaign=ch.email-signature_type.community_content.blog>[image: > Twitter] <https://twitter.com/ConfluentInc>[image: LinkedIn] > <https://www.linkedin.com/company/confluent/>[image: Slack] > <https://slackpass.io/confluentcommunity>[image: YouTube] > <https://youtube.com/confluent> > > [image: Try Confluent Cloud for Free] > <https://www.confluent.io/get-started?utm_campaign=tm.fm-apac_cd.inbound&utm_source=gmail&utm_medium=organic> > > >
