[KINDLY REMINDER] Flink 2.1 Release Sync 06/04/2025

Hi, everyone! The next release sync will be held at the following time. - 14:00, June 4, BJT (GMT+8) - 08:00, June 4, CET (GMT+2) - 23:00, June 4, PT (GMT-7) Everyone is welcome to join via Google Meet [1]. The topics to be discussed can be found at the Status / Follow-ups section of the release

Re: [DISCUSS] FLIP-531: Initiate Flink Agents as a new Sub-Project

Thanks Xintong, Sean, and Chris for initiating Flink Agents sub-project. Big +1 for this proposal in the AI Agent era. Best, Ron Dian Fu 于2025年5月22日周四 09:31写道： > Thanks for the proposal. It's a promising direction to bring Flink's > event driven processing capacity into AI agent. Looking forwa

[SUMMARY] Flink 2.1 Release Sync 05/21/2025

Hi, devs, This is the third meeting for Flink 2.1 release cycle. I'd like to share the information synced in the meeting. - Feature Freeze It is worth noting that there are only 4 weeks left until the feature freeze time(June 21, 2025), and developers need to pay attention to the feature free

Re: storage partition join (bucket join) implementation in flink

+1 for it, a great feature. Best, Ron Lu Niu 于2025年5月20日周二 06:27写道： > Hi Flink Developers, > > We’ve noticed that storage partition join is currently not supported in > Flink. For reference, Spark has supported this feature for some time (see: > https://issues.apache.org/jira/browse/SPARK-37375

Re: [VOTE] FLIP-486: Introduce a new DeltaJoin

+1(binding) Best, Ron Xuyang 于2025年5月20日周二 09:42写道： > Hi, devs. > I'd like to start a vote on FLIP-486: Introduce a new DeltaJoin[1], which > has been discussed in this thread[2]. > The vote will be open for at least 72 hours unless there is an objection > or not enough votes. > > > [1] > https

Re: 2025/05/15 CHI Western time zone workgroup meeting minutes

Hi, David Thanks for pushing this work, I can help to merge them. Best, Ron David Radley 于2025年5月17日周六 00:47写道： > Hi all, > We held the 23rd Chi meeting. > > * The open PR numbers are down to under 200 now – much more > manageable. I am curious if anyone thinks this is too aggressive. >

Re: Re: Re: Re: [DISCUSS] FLIP-486: Introduce a new DeltaJoin

okup syntax. However, it > may > >> be necessary to pursue a separate FLIP to address this. > >> > >> 6. Schema with indexes in the table can be retrieved by using the > >> `getTable` on `Catalog`. I do not want the engine to create indexes >

Re: [VOTE] FLIP-516: Multi-Way Join Operator

+1 (binding) Best, Ron Hao Li 于2025年5月10日周六 02:35写道： > +1 (non-binding) > > Thanks, > Hao > > On Fri, May 9, 2025 at 3:41 AM Arvid Heise wrote: > > > +1 (binding) > > > > Cheers > > > > On Wed, May 7, 2025 at 6:37 PM Gustavo de Morais > > > wrote: > > > > > Hi everyone, > > > > > > I'd like t

Re: [VOTE]FLIP-519: Introduce async lookup key ordered mode

+1(binding) Best, Ron Lincoln Lee 于2025年5月12日周一 09:55写道： > +1 (binding) > > > Best, > Lincoln Lee > > > shuai xu 于2025年5月9日周五 17:46写道： > > > Hi devs, > > > > Thank you for providing feedback on FLIP-519: Introduce async lookup key > > ordered mode[1]. > > I'd like to start a vote on this FLIP

Re: [DISCUSS] Flink 1.20.2 release

+1 Best, Ron Gabor Somogyi 于2025年5月8日周四 23:52写道： > Thanks for volunteering +1. > > G > > > On Thu, May 8, 2025 at 5:45 PM Ferenc Csaky > wrote: > > > Hello devs, > > > > I would like to start a discussion about the next patch release for 1.20. > > The 1.20.1 version was released almost 3 month

Re: [DISCUSS] Flink 1.19.3 release

+1 Best, Ron Gabor Somogyi 于2025年5月9日周五 00:06写道： > Thanks for volunteering +1. > > G > > > On Thu, May 8, 2025 at 5:49 PM Ferenc Csaky > wrote: > > > Hello devs, > > > > I would like to start a discussion about the next patch release for 1.19. > > The 1.19.2 version was released almost 3 month

Re: [VOTE] FLIP-525: Model ML_PREDICT, ML_EVALUATE Implementation Design

+1 (binding) Best, Ron Shengkai Fang 于2025年5月9日周五 09:49写道： > +1 (binding) > > Best, > Shengkai > > Mayank Juneja 于2025年5月9日周五 03:18写道： > > > +1 (non-binding) > > > > On Thu, May 8, 2025 at 11:02 AM Hao Li wrote: > > > > > Hi everyone, > > > > > > I'd like to start a vote on FLIP-525: Model ML

Re: [DISCUSS] FLIP-526: Model ML_PREDICT, ML_EVALUATE Table API

Hi, Hao +1 for the proposal. Due to [1][2] having supported serialize table API to SQL, so I've one question: whether the predict or evaluate introduced in this FLIP can be serialized to SQL? [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-393%3A+Make+QueryOperations+SQL+serializable

Re: Re: [DISCUSS] FLIP-486: Introduce a new DeltaJoin

Hi, Xuyang Thanks for initiating this FLIP, which is of great value in solving the Streaming Join that troubles many users. Big +1 for it. For the overall design of FLIP, I have the following questions: 1. Can you explain the currently supported Join types in FLIP, such as Inner, Left, and Right

Re: [DISCUSS] FLIP-516: Multi-Way Join Operator

Hi, Gustavo Sorry for the late participation in the FLIP discussion, this is a great feature to solve the headache of the stream join, Big +1. Regarding the new config option `table.optimizer.multi-join.enabled`, I have a question: is this option only effective in streaming mode, what is its beha

Re: [VOTE] FLIP-521: Integrating Variant Type into Flink: Enabling Efficient Semi-Structured Data Processing

+1(binding) Best, Ron weijie guo 于2025年5月7日周三 21:15写道： > +1（binding) > > Best regards, > > Weijie > > > Xintong Song 于2025年5月7日周三 19:37写道： > > > +1 (binding) > > > > Best, > > > > Xintong > > > > > > > > On Wed, May 7, 2025 at 7:00 PM Lincoln Lee > wrote: > > > > > +1 (binding) > > > > > > >

[SUMMARY] Flink 2.1 Release Sync 05/07/2025

Hi, devs, This is the second meeting for Flink 2.1 release cycle. I'd like to share the information synced in the meeting. - Feature Freeze It is worth noting that there are only 7 weeks left until the feature freeze time(June 21, 2025), and developers need to pay attention to the feature fre

Re: [DISCUSS] FLIP-525: Model ML_PREDICT, ML_EVALUATE Implementation Design

need to copy it during the > planning stage and apply mutations to the provider. But it may not be used > for now. I'm also ok to remove it. > > > Hope this answers your question. > > Thanks, > Hao > > > On Tue, May 6, 2025 at 7:49 PM Ron Liu wrote: > > >

Re: [VOTE] FLIP-520: Simplify StructuredType handling

+1(binding) Best, Ron Hao Li 于2025年5月7日周三 00:08写道： > +1 (non-binding) > > Thanks for driving this! > > Hao > > On Tue, May 6, 2025 at 8:27 AM Ferenc Csaky > wrote: > > > +1 (binding) > > > > Thanks for driving this! > > > > Best, > > Ferenc > > > > > > > > > > On Tuesday, May 6th, 2025 at 14:5

Re: [DISCUSS] FLIP-525: Model ML_PREDICT, ML_EVALUATE Implementation Design

Hi, Hao Thanks for starting this proposal, it's a great feature, +1. Since I was missing some context, I went to FLIP-437. Combining these two FLIPs, I have the following three questions: 1. Why is it necessary to define the task option in the WITH clause of the Model DDL, and what is its purpose

[KINDLY REMINDER] Flink 2.1 Release Sync 07/05/2025

Hi, everyone! The next release sync will be held at the following time. - 14:00, May 7, BJT (GMT+8) - 08:00, May 7, CET (GMT+2) - 23:00, May 6, PT (GMT-7) Everyone is welcome to join via Google Meet [1]. The topics to be discussed can be found at the Status / Follow-ups section of the release wik

Re: [DISCUSS] FLIP-527 Support EXPLAIN EXECUTE STATEMENT SET Syntax in Flink SQL

Hi, Ramin Thanks for starting this proposal. After glancing at the content of FLIP, I have a question, how valuable is it to introduce this new syntax, if users want to EXPLAIN STATEMENT SET, the EXPLAIN keyword itself has to be written, how much does it cost to remove the EXECUTE keyword at this

Re: [DISCUSS] FLIP-519: Introduce async lookup key ordered mode

Hi, Shuai Thanks for driving this proposal. The FLIP looks good to me overall, +1 for it. I have a small question about the table's contents. When 'table.exec.async-lookup.key-ordered-enabled=true' and 'table.exec.async-lookup.output-mode=ORDERD', the lookup join in key ordered should be 'yes', n

[SUMMARY] Flink 2.1 Release Sync 04/23/2025

Hi, devs Today we had our first meeting for Flink 2.1 release cycle. I'd like to share the info synced in the meeting. 1. Feature freezing and release: - Feature Freeze: June 21, 2025, 00:00 CEST(UTC+2) - Release: End of July 2025 2. Update 2.1 Release page: Flink 2.1 release has been ki

[KINDLY REMINDER] Flink 2.1 Release Sync 23/04/2025

Hi, everyone! The first release sync will be held at the following time. - 14:00, Apr 23, BJT (GMT+8) - 08:00, Apr 23, CET (GMT+2) - 23:00, Apr 22, PT (GMT-7) Everyone is welcome to join via Google Meet [1]. The topics to be discussed can be found at the Status / Follow-ups section of the release

Re: [ANNOUNCE] New Apache Flink Committer - Yanquan Lv

Congratulations! Best, Ron shuai xu 于2025年4月17日周四 15:50写道： > Congratulations, Yanquan! > > Best, > Xu Shuai > > > 2025年4月17日 14:27，Xuyang 写道： > > > > Congratulations, Yanquan! > >

Re: Re: [ANNOUNCE] New Apache Flink Committer - Xiqian Yu

Congratulations! Best, Ron Xuyang 于2025年4月17日周四 14:22写道： > Congratulations, Xiqian! > > > > > > -- > > Best！ > Xuyang > > > > > > 在 2025-04-17 14:01:28，"shuai xu" 写道： > >Congratulations! > > > >Best, > >Xu Shuai > > > >> 2025年4月17日 13:54，Lincoln Lee 写道： > >> > >> Congratulations, Xiqi

Recording Feature FLIP to Flink 2.1 Release Wiki

Hi everyone, Flink 2.1 has officially entered the release cycle, as the release manager, I kindly remind you to register the relevant Feature FLIPs to be completed in this release to the wiki document [1], so that we can better track the progress and push Flink to keep moving forward. [1] https:/

Re: [DISCUSS] Planning Flink 2.1

Hi everyone, The discussion has been ongoing for a long time, and there is currently 1 RM candidate, so the final release manager of 2.1 is Ron Liu. We will do the first release sync on April 23, 2025, at 9 am (UTC+2) and 3 pm (UTC+8). Welcome to the meeting! Best regards, Ron Ron Liu 于2025年3月

Re: [DISCUSS] Planning Flink 2.1

se rather than a point release. For example > > https://commons.apache.org/releases/versioning.html, > > > > Kind regards, David. > > > > > > From: Jark Wu > > Date: Tuesday, 25 March 2025 at 06:52 > > To: dev@flink.apache.o

[DISCUSS] Planning Flink 2.1

Hi everyone, With the release announcement of Flink 2.0, it's a good time to kick off discussion of the next release 2.1. - Release Managers I'd like to volunteer as one of the release managers this time. It has been good practice to have a team of release managers from different backgrounds, so

Re: [VOTE] FLIP-506: Support Reuse Multiple Table Sinks in Planner

+1(binding) Best, Ron Jingsong Li 于2025年3月10日周一 15:44写道： > +1 > > On Mon, Mar 10, 2025 at 1:56 PM Lincoln Lee > wrote: > > > > +1 (binding) > > > > > > Best, > > Lincoln Lee > > > > > > xiangyu feng 于2025年3月10日周一 13:33写道： > > > > > Hi devs, > > > > > > All comments in the discussion thread[1]

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

ove this ambiguity in the FLIP[1]. When > this ability is enabled, the sink can support reuse with different target > columns which means the sink digest should **not include** this > information. > > @Lincoln, looking forward to hear you back for the response. > > Also, @Ron L

Re: [ANNOUNCE] New Apache Flink Committer - Feng Jin

Congratulations Best, Ron Yuepeng Pan 于2025年2月21日周五 09:57写道： > Congratulations ! > > > Best, > Yuepeng. > > > > > > At 2025-02-21 09:52:46, "Lincoln Lee" wrote: > >Hi everyone, > > > >On behalf of the PMC, I'm happy to announce that Feng Jin has become a > >new Flink Committer! > > > >Feng Jin

Re: [ANNOUNCE] New Apache Flink Committer - Xuyang

Congratulations, you deserve it. Best, Ron Lincoln Lee 于2025年2月20日周四 09:50写道： > Hi everyone, > > On behalf of the PMC, I'm happy to announce that Xuyang has become a > new Flink Committer! > > Xuyang has been contributing to the Flink community since Sep 15, 2021, he > has > driven and contrib

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

ple+Table+Sinks+in+Planner > > Best, > Xiangyu Feng > > Ron Liu 于2025年2月19日周三 10:25写道： > >> Hi Xiangyu, >> >> Thanks for your reply, the updates LGTM overall. >> >> 1. Regarding the naming of the interface, what do you think about calling >>

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

for users, I agree to enable this in the > first > >> > place. Similar features like `table.optimizer.reuse-sub-plan-enabled` > >> and > >> > `table.optimizer.reuse-source-enabled` are also enabled by default. > From > >> > this point of view, sink re

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

T? > > - have you considered the technical implementation options and are they > feasible? > > Yes, we have already implemented the POC internally. It works well. > > Looking forward for your feedback. > > Best, > Xiangyu > > Ron Liu 于2025年2月13日周四 14:55写道： >

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

Hi, Xiangyu Thank you for proposing this FLIP, it's great work and looks very useful for users. I have the following two questions regarding the content of the FLIP: 1. Since sink reuse is very useful, should the default value be true for the newly introduced option `table.optimizer.reuse-sink-en

Re: [DISCUSSION] flink-connector-hive first release of externalized connector

+1 Best, Ron yuxia 于2025年1月14日周二 10:17写道： > Thanks Sergey for driving this work again.. > +1 for externalizing hive connector to finish all connector externalizing > for Flink.. > > Best regards, > Yuxia > > - 原始邮件 - > 发件人: "Jark Wu" > 收件人: "dev" > 发送时间: 星期二, 2025年 1 月 14日 上午 10:06:42

Re: [VOTE] CHI: Stale PR cleanup

+1(binding) Best, Ron David Radley 于2025年1月7日周二 00:43写道： > Thanks for driving this Tom. > +1 (non-binding) > David > > From: Gyula Fóra > Date: Monday, 6 January 2025 at 16:33 > To: dev@flink.apache.org > Subject: [EXTERNAL] Re: [VOTE] CHI: Stale PR cleanup > +1 (binding) > Gyula > > On Mon,

Re: Re:[DISSCUSS] Removing default error methods from the new public api stack in the table api when it implements both the new and deprecated public api stacks and the old stack is removed

ons. > > > > > > > > > > -- > > > > Best！ > > Xuyang > > > > > > > > > > 在 2025-01-03 12:55:38，"Xuyang" 写道： > > > > The discuss will be open for at least 72 hours to collect dicisions. > >

Re: [VOTE] FLIP-492: Support Query Modifications for Materialized Tables

+1(binding) Best, Ron Feng Jin 于2024年12月30日周一 09:47写道： > Hi everyone, > > I'd like to start a vote on FLIP-492: Support Query Modifications for > Materialized Tables [1] > which has been discussed in this thread [2]. > > The vote will be open for at least 72 hours unless there is an objection >

Re: [VOTE] FLIP-494: Add missing createTable/createView methods to TableEnvironment

+1(binding) Best, Ron Sergey Nuyanzin 于2024年12月20日周五 18:52写道： > Hi everyone, > > I'd like to start a vote on FLIP-494: Add missing createTable/createView > methods to TableEnvironment [1] which has been discussed in this thread > [2]. > > The vote will be open for at least 72 hours unless there

Re: [DISCUSS] FLIP-492: Support Query Modifications for Materialized Tables.

ensure state compatibility, some > simple modification scenarios can indeed be compatible. > > For now, the responsibility is left to the users. > > > Even if recovery ultimately fails, users still have the option to roll > back to the original query or start consumin

Re: [DISCUSS] FLIP-494: Add missing createTable/createView methods to TableEnvironment

Hi Sergey Thanks for driving this FLIP, +1. It may be a minor typo for the createTable method doc. ``` * {@code * tEnv.createTemporaryTable("MyTable", TableDescriptor.forConnector("datagen") * .schema(Schema.newBuilder() * .column("f0", DataTypes.STRING()) * .build()) * .option(DataGenOpt

Re: [VOTE] FLIP-489: Add missing dropTable/dropView methods to TableEnvironment

+1(binding) Best, Ron Leonard Xu 于2024年12月15日周日 16:12写道： > Thanks Sergey for driving this FLIP, > > +1(binding) > > Best, > Leonard > > > > > > On Dec 13, 2024, at 6:48 PM, Timo Walther wrote: > > > > +1 (binding) > > > > Thanks, > > Timo > > > > > > On 13.12.24 01:37, Jim Hughes wrote: > >> H

Re: [VOTE]FLIP-480: Support to deploy script in application mode

+1(binding) Best, Ron Gyula Fóra 于2024年11月12日周二 01:27写道： > + 1(binding) > > Thanks for answering my concerns/questions. > > Gyula > > On Fri, Nov 8, 2024 at 11:16 AM Gyula Fóra wrote: > > > Hey! > > > > Sorry, bit late to the party, I have added a concern to the discussion > > related to the g

Re: [ANNOUNCE] New Apache Flink Committer - Junrui Li

Congratulations Junrui Best, Ron wenjin 于2024年11月7日周四 11:57写道： > Congratulations Junrui~ > > Best regards, > Wenjin > > > 2024年11月5日 19:59，Zhu Zhu 写道： > > > > Hi everyone, > > > > On behalf of the PMC, I'm happy to announce that Junrui Li has become a > > new Flink Committer! > > > > Junrui ha

Re: [DISCUSS] FLIP-480: Support to deploy script in application mode

Hi, Shengkai Thanks for your quick response. It looks good to me. Best Ron Shengkai Fang 于2024年10月31日周四 10:08写道： > Hi, Ron! > > > I noticed that you say this FLIP focuses on supporting deploy sql > scripts to the application cluster, does it mean that it only supports > non-interactive gatewa

Re: [DISCUSS] FLIP-480: Support to deploy script in application mode

hether it is possible to specify a local jar? Best, Ron Ron Liu 于2024年10月30日周三 10:57写道： > Hi, Shengkai > > Thanks for initializing this FLIP, supports application mode for SQL > Gateway is a great job. The FLIP design looks good to me. > > > I've read the FLIP-316 which me

Re: [DISCUSS] FLIP-480: Support to deploy script in application mode

Hi, Shengkai Thanks for initializing this FLIP, supports application mode for SQL Gateway is a great job. The FLIP design looks good to me. I've read the FLIP-316 which mentions supporting deploying SQL job to application clusters for interactive or non-interactive gateway mode. But I noticed t

Re: [VOTE] FLIP-473: Introduce New SQL Operators Based on Asynchronous State APIs

+1(binding) Best, Ron Zakelly Lan 于2024年8月21日周三 11:16写道： > +1 (binding) > > Best, > Zakelly > > On Wed, Aug 21, 2024 at 10:33 AM Xuyang wrote: > > > Hi, everyone. > > > > I would like to start a vote on FLIP-473: Introduce New SQL Operators > Based > > > > on Asynchronous State APIs [1]. The d

Re: [VOTE] FLIP-470: Support Adaptive Broadcast Join

+1(binding) Best, Ron Zhu Zhu 于2024年8月12日周一 13:35写道： > +1 (binding) > > Thanks, > Zhu > > Lincoln Lee 于2024年8月12日周一 13:09写道： > > > +1 > > > > Best, > > Lincoln Lee > > > > > > Xia Sun 于2024年8月12日周一 09:57写道： > > > > > Hi everyone, > > > > > > Thanks for all the feedback about FLIP-470: Support

Re: [VOTE] FLIP-469: Supports Adaptive Optimization of StreamGraph

+1(binding) Best, Ron weijie guo 于2024年7月29日周一 10:03写道： > +1(binding) > > Best regards, > > Weijie > > > Junrui Lee 于2024年7月29日周一 09:38写道： > > > Hi everyone, > > > > Thanks for all the feedback about FLIP-469: Supports Adaptive > Optimization > > of StreamGraph [1]. The discussion thread can b

Re: [DISCUSS] FLIP-469: Supports Adaptive Optimization of StreamGraph

the list type always be > > order-preserving > > > > Yes, we will ensure that the order in which this config parameter is > > loaded is consistent with the order set by the user. The execution order > > will also follow this sequence. > > > > 3.are all > >

Re: [DISCUSS] FLIP-470: Support Adaptive Broadcast Join

are enabled (e.g., > `table.optimizer.adaptive.join.broadcast-threshold` is not -1), the > corresponding strategy will be configured. This optimization is independent > of the specific SQL query, although it might not produce any actual effect. > > Best, > Xia > > Ron Liu 于2024年7月

Re: [VOTE] FLIP-468: Introducing StreamGraph-Based Job Submission

+1(binding) Best, Ron Rui Fan <1996fan...@gmail.com> 于2024年7月26日周五 11:50写道： > Thanks Junrui for driving this proposal! > > +1(binding) > > Best, > Rui > > On Fri, Jul 26, 2024 at 11:02 AM Junrui Lee wrote: > > > Hi everyone, > > > > Thanks for all the feedback about FLIP-468: Introducing Stream

Re: [DISCUSS] FLIP-469: Supports Adaptive Optimization of StreamGraph

One additional question: for a JobEvent, are all StreamGraphOptimizationStrategy traversed and executed once? Best, Ron Ron Liu 于2024年7月24日周三 13:59写道： > Hi, Junrui > > Thanks for the proposal, this design allows the Flink engine to become > smarter by doing more dynamic opti

Re: [DISCUSS] FLIP-470: Support Adaptive Broadcast Join

Hi, Xia This FLIP looks good to me, +1. I've two questions: 1. >> Accordingly, in terms of implementation, we will delay the codegen and creation of the join operators until runtime. How are you delaying codegen to runtime, the current runtime is not SQL planner aware. in other words, how do I

Re: [DISCUSS] FLIP-469: Supports Adaptive Optimization of StreamGraph

Hi, Junrui Thanks for the proposal, this design allows the Flink engine to become smarter by doing more dynamic optimizations at runtime. so +1 from my side. For your FLIP, I've one minor question. Regarding the StreamGraphOptimizationStrategy, you mentioned introducing the option `execution.bat

Re: [DISCUSS] FLIP-468: Introducing StreamGraph-Based Job Submission.

izables: > > > > > > Are you suggesting that Java serialization has limitations, and that we > > should explore alternative serialization approaches? I agree that this > is a > > valuable consideration for the future. Do you think this should be > includ

Re: [VOTE] Release 1.20.0, release candidate #1

Hi, Weijie Sorry about the newly discovered bug affecting the release process. The fix pr of https://issues.apache.org/jira/browse/FLINK-35872 has been merged. Best, Ron Feng Jin 于2024年7月22日周一 10:57写道： > Hi, weijie > > -1 (non-binding) > > During our testing process, we discovered a critical

Re: [DISCUSS] FLIP-468: Introducing StreamGraph-Based Job Submission.

Hi, Junrui The FLIP proposal looks good to me. I have the same question as Fabian: > For join strategies, they are only applicable when using an optimizer (that's currently not part of Flink's runtime) with the Table API or Flink SQL. How do we plan to connect the optimizer with Flink's runtime?

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

name, type and null/not null properties. > Based on this, I don't see there will be an issue with uniqueness. Users > may define a pkey on the not null columns > only. > > - Sergio > > > On Sun, Jun 16, 2024 at 9:55 PM Ron Liu wrote: > > > Hi, Sergio > > &

Re: [ANNOUNCE] New Apache Flink Committer - Zhongqiang Gong

Congratulations, Hang! Best, Ron Geng Biao 于2024年6月17日周一 12:35写道： > Congratulations, Zhongqiang! > Best, > Biao Geng > > 发送自 Outlook for iOS > > 发件人: Zakelly Lan > 发送时间: Monday, June 17, 2024 12:11:47 PM > 收件人: dev@flink.apache.org > 主题:

Re: [ANNOUNCE] New Apache Flink Committer - Hang Ruan

Congratulations, Hang! Best, Ron Geng Biao 于2024年6月17日周一 12:35写道： > Congrats, Hang! > Best, > Biao Geng > > 发送自 Outlook for iOS > > 发件人: Zakelly Lan > 发送时间: Monday, June 17, 2024 12:12:10 PM > 收件人: dev@flink.apache.org > 主题: Re: [ANNOUNC

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

Hi, Sergio Sorry for later joining this thread. Thanks for driving this proposal, it looks great. I have a few questions: 1. Many SQL-based data processing systems, however, support schema definitions within their CTAS statements Is it possible for you to list these systems and make it part of

Re: [DISCUSSION] FLIP-457: Improve Table/SQL Configuration for Flink 2.0

Hi, Lincoln > 2. Regarding the options in HashAggCodeGenerator, since this new feature has gone through a couple of release cycles and could be considered for PublicEvolving now, cc @Ron Liu WDYT? Thanks for cc'ing me, +1 for public these options now. Best, Ron Benchao Li 于2024年5月

[RESULT][VOTE] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

Hi, Dev I'm happy to announce that FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table[1] has been accepted with 8 approving votes (4 binding) [2]. - Xuyang - Feng Jin - Lincoln Lee(binding) - Jark Wu(binding) - Ron Liu(binding) - Shengkai Fang(binding) - Keit

Re: Re: [VOTE] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

： > > > > > +1 (non-binding) > > > > > > > > > Best, > > > Feng > > > > > > > > > On Thu, May 9, 2024 at 7:37 PM Xuyang wrote: > > > > > > > +1 (non-binding) > > > > > > > >

Re: [VOTE] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

is an objection or not enough votes. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-448%3A+Introduce+Pluggable+Workflow+Scheduler+Interface+for+Materialized+Table [2] https://lists.apache.org/thread/57xfo6p25rbrhcg01dhyok46zt6jc5q1 Best, Ron Ron Liu 于2024年5月9日周四 13:52写道： > Hi Dev, T

[VOTE] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

Hi Dev, Thank you to everyone for the feedback on FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table[1][2]. I'd like to start a vote for it. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1] https://cwiki.apache.org/conf

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

Hi, Dev Thank you all for joining this thread and giving your comments and suggestions, they have helped improve this proposal and I look forward to further feedback. If there are no further comments, I'd like to close the discussion and start the voting one day later. Best, Ron Ron Liu 于

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

/blob/29736b8c01924b7da03d4bcbfd9c812a8e5a08b4/flink-table/flink-table-api-java/src/main/java/org/apache/flink/table/operations/Operation.java Best, Ron Ron Liu 于2024年5月7日周二 14:30写道： > > 4. It appears that in the section on `public interfaces`, within > `Workflow

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

ter and the caller. Best, Ron Ron Liu 于2024年5月6日周一 20:48写道： > Hi, Xuyang > > Thanks for joining this discussion > > > 1. In the sequence diagram, it appears that there is a missing step for > obtaining the refresh handler from the catalog during the suspend operation. > >

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

t appears that in the section on `public interfaces`, within > `WorkflowOperation`, `CreatePeriodicWorkflowOperation` should be changed to > > `CreateWorkflowOperation`, right? > > > > > -- > > Best！ > Xuyang > > > > > > At 2024-04-22 14:41:39, &

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

t; simply wait for the PRs to come. > > > > > After discussing with Shengkai offline, there is no need for this REST > > API > > to support multiple tables to be refreshed at the same time, so it would > be > > more appropriate to put the materialized table ide

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

ttps://github.com/apache/flink/blob/b1544e4e513d2b75b350c20dbb1c17a8232c22fd/flink-table/flink-table-api-java/src/main/java/org/apache/flink/table/catalog/listener/CatalogModificationListener.java#L31 Best, Ron Ron Liu 于2024年4月28日周日 23:53写道： > Hi, Shengkai > > Thanks for your feedback and suggestion, it looks very useful fo

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

Hi, Shengkai Thanks for your feedback and suggestion, it looks very useful for this proposal, regarding your question I made the following optimization: > *WorkflowScheduler* > 1. How to get the exception details if `modifyRefreshWorkflow` fails? > 2. Could you give us an example about how to con

Re: [VOTE] FLIP-445: Support dynamic parallelism inference for HiveSource

+1(binding) Best, Ron Rui Fan <1996fan...@gmail.com> 于2024年4月26日周五 12:55写道： > +1(binding) > > Best, > Rui > > On Fri, Apr 26, 2024 at 10:26 AM Muhammet Orazov > wrote: > > > Hey Xia, > > > > +1 (non-binding) > > > > Thanks and best, > > Muhammet > > > > On 2024-04-26 02:21, Xia Sun wrote: > > >

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

Table will be > lost? > > 2. Regarding the status information of the workflow, I am wondering if it > is necessary to provide an interface to display the backend scheduling > information? This would make it more convenient to view the execution > status of backend jobs. > >

[DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

Hi, Dev I would like to start a discussion about FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table. In FLIP-435[1], we proposed Materialized Table, which has two types of data refresh modes: Full Refresh & Continuous Refresh Mode. In Full Refresh mode, the Material

[RESULT][VOTE] FLIP-435: Introduce a New Materialized Table for Simplifying Data Pipelines

Hi, Dev I'm happy to announce that FLIP-435: Introduce a New Materialized Table for Simplifying Data Pipelines[1] has been accepted with 13 approving votes (8 binding) [2] - Ron Liu(binding) - Feng Jin - Rui Fan(binding) - Yuepeng Pan - Ahmed Hamdy - Ferenc Csaky - Lincoln Lee(binding) - Le

Re: [DISCUSS] FLIP-445: Support dynamic parallelism inference for HiveSource

Hi, Xia Thanks for updating, looks good to me. Best, Ron Xia Sun 于2024年4月18日周四 19:11写道： > Hi Ron, > Yes, presenting it in a table might be more intuitive. I have already added > the table in the "Public Interfaces | New Config Option" chapter of FLIP. > PTAL~ > > R

Re: [DISCUSS] FLIP-445: Support dynamic parallelism inference for HiveSource

> will add InferMode.NONE as one of the Enum options in InferMode class. > > Best， > Xia > > Lijie Wang 于2024年4月18日周四 13:50写道： > > > Thanks for driving the discussion. > > > > +1 for the proposal and +1 for the `InferMode.NONE` option. > > > > Best, &

Re: [DISCUSS] FLIP-445: Support dynamic parallelism inference for HiveSource

Hi, Xia Thanks for driving this FLIP. This proposal looks good to me overall. However, I have the following minor questions: 1. FLIP introduced `table.exec.hive.infer-source-parallelism.mode` as a new parameter, and the value is the enum class `InferMode`, I think the InferMode class should also

Re: [VOTE] FLIP-435: Introduce a New Materialized Table for Simplifying Data Pipelines

+1(binding) Best, Ron Ron liu 于2024年4月17日周三 14:27写道： > Hi Dev, > > Thank you to everyone for the feedback on FLIP-435: Introduce a New > Materialized Table for Simplifying Data Pipelines[1][2]. > > I'd like to start a vote for it. The vote will be open for at least 72

[VOTE] FLIP-435: Introduce a New Materialized Table for Simplifying Data Pipelines

Hi Dev, Thank you to everyone for the feedback on FLIP-435: Introduce a New Materialized Table for Simplifying Data Pipelines[1][2]. I'd like to start a vote for it. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1] https://cwiki.apache.org/conflue

Re: [ANNOUNCE] New Apache Flink Committer - Zakelly Lan

Congratulations! Best, Ron Yuan Mei 于2024年4月15日周一 10:51写道： > Hi everyone, > > On behalf of the PMC, I'm happy to let you know that Zakelly Lan has become > a new Flink Committer! > > Zakelly has been continuously contributing to the Flink project since 2020, > with a focus area on Checkpointing

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

FLIP-282 [1] has also introduced Update & Delete API for modifying table. 1. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235838061 Best, Ron Ron liu 于2024年4月12日周五 19:49写道： > Hi, jgrier > > Thanks for your insightful input. > > First of all, very much

Re: [ANNOUNCE] New Apache Flink PMC Member - Lincoln Lee

Congratulations, Lincoln! Best, Ron Junrui Lee 于2024年4月12日周五 18:54写道： > Congratulations, Lincoln! > > Best, > Junrui > > Aleksandr Pilipenko 于2024年4月12日周五 18:29写道： > > > Congratulations, Lincoln! > > > > Best Regards > > Aleksandr > > >

Re: [ANNOUNCE] New Apache Flink PMC Member - Jing Ge

Congratulations, Jing! Best, Ron Junrui Lee 于2024年4月12日周五 18:54写道： > Congratulations, Jing! > > Best, > Junrui > > Aleksandr Pilipenko 于2024年4月12日周五 18:28写道： > > > Congratulations, Jing! > > > > Best Regards, > > Aleksandr > > >

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

t; 1. Derived table -> extend the persistent semantics of derived > table > > in > > > > SQL > > > > >standard, with a strong association with query, and has industry > > > > > precedents > > > > >such as Google Looker. > > > >

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

Hi, Dev My rankings are: 1. Derived Table 2. Materialized Table 3. Live Table 4. Materialized View Best, Ron Ron liu 于2024年4月9日周二 20:07写道： > Hi, Dev > > After several rounds of discussion, there is currently no consensus on the > name of the new concept. Timo has proposed th

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

this Friday. I look forward to everyone voting on the name in this thread. Of course, we also welcome new input regarding the name. Best, Ron Ron liu 于2024年4月9日周二 19:49写道： > Hi, Dev > > Sorry for my previous statement was not quite accurate. We will hold a > vote for the name wit

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

Hi, Dev Sorry for my previous statement was not quite accurate. We will hold a vote for the name within this thread. Best, Ron Ron liu 于2024年4月9日周二 19:29写道： > Hi, Timo > > Thanks for your reply. > > I agree with you that sometimes naming is more difficult. When no on

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

> 2. Materialized Table -> similar to SQL materialized view but a table > 3. Live Table -> nice buzzword, but maybe still too close to dynamic > tables? > 4. Materialized View -> a bit broader than standard but still very similar > 5. Derived table -> taken by standard >

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

pic=tables-materialized-query [3] https://community.denodo.com/docs/html/browse/6.0/vdp/vql/materialized_tables/creating_materialized_tables/creating_materialized_tables Best, Ron Ron liu 于2024年4月7日周日 15:55写道： > Hi, Lorenzo > > Thank you for your insightful input. > > >>> I think th

Re: [DISCUSS] FLIP-435: Introduce a New Dynamic Table for Simplifying Data Pipelines

hard of course, but I would > probably > > prefer something like CREATE CONTINUOUS TABLE, CREATE REFRESH TABLE or > > CREATE LIVE TABLE. > > > > Best regards, > > > > Martijn > > > > [1] > > > https://docs.databricks.com/en/sql/language-man

  1   2   >