[VOTE] Apache Flink CDC Release 3.5.0, release candidate #2

2025-09-22 Thread Yanquan Lv
Hi everyone, Please review and vote on the release candidate #2 for the version 3.5.0 of Apache Flink CDC, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) *Release Overview* As an overview, the release consists of the following: a) Flin

Re: [VOTE] Apache Flink CDC Release 3.5.0, release candidate #1

2025-09-21 Thread Yanquan Lv
:19写道: > -1 > I think it is a blocker , by https://github.com/apache/flink-cdc/pull/4129 > > On 2025/09/19 08:43:44 Yanquan Lv wrote: > > Hi everyone, > > Please review and vote on the release candidate #1 for the version 3.5.0 > of > > Apache Flink CDC, > >

[VOTE] Apache Flink CDC Release 3.5.0, release candidate #1

2025-09-19 Thread Yanquan Lv
Hi everyone, Please review and vote on the release candidate #1 for the version 3.5.0 of Apache Flink CDC, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) *Release Overview* As an overview, the release consists of the following: a) Flin

[jira] [Created] (FLINK-38380) MySQL cdc may skip data in the GTID disordered scenario even after GTID merged

2025-09-18 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38380: -- Summary: MySQL cdc may skip data in the GTID disordered scenario even after GTID merged Key: FLINK-38380 URL: https://issues.apache.org/jira/browse/FLINK-38380 Project

[DISCUSS] Release Flink CDC version 3.5.0

2025-09-18 Thread Yanquan Lv
Hi everyone, I want to kick off the discussion for Flink CDC release v3.5.0. Flink CDC v3.5.0 [1] adds new connectors (e.g., Fluss/PostgreSQL) to expand database compatibility and introduces significant optimizations for multi-table synchronization scenarios (e.g., improved performance for large-

[jira] [Created] (FLINK-38362) Reduce the time cost in checkpoint when writing many tables to StarRocks sink

2025-09-16 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38362: -- Summary: Reduce the time cost in checkpoint when writing many tables to StarRocks sink Key: FLINK-38362 URL: https://issues.apache.org/jira/browse/FLINK-38362 Project

[jira] [Created] (FLINK-38359) Avoid writing Record with update before/delete rowKind to Paimon append only table.

2025-09-16 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38359: -- Summary: Avoid writing Record with update before/delete rowKind to Paimon append only table. Key: FLINK-38359 URL: https://issues.apache.org/jira/browse/FLINK-38359

[jira] [Created] (FLINK-38358) Ignore trailing spaces in table capturing rules

2025-09-16 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38358: -- Summary: Ignore trailing spaces in table capturing rules Key: FLINK-38358 URL: https://issues.apache.org/jira/browse/FLINK-38358 Project: Flink Issue Type

[RESULT][VOTE] FLIP-535: Introduce RateLimiter to Source

2025-09-03 Thread Yanquan Lv
Hi devs, I am happy to announce that "FLIP-535: Introduce RateLimiter to Source"[1] has been accepted with 7 approving votes (3 binding)[2]: - Shengkai Fang (binding) - Leonard Xu (binding) - Poorvank Bhatia (non-binding) - Xiqian YU (non-binding) - Jiangang Liu (non-binding) -

Re: [VOTE] FLIP-535: Introduce RateLimiter to Source

2025-09-03 Thread Yanquan Lv
Hi all, Thanks all for voting. I'm closing the vote and I will post the result in a separate email. Zexian WU 于2025年8月21日周四 11:18写道: > Hi all, > > I'd like to start a vote on FLIP-535: Introduce RateLimiter to Source [1], > which has been discussed in this thread [2]. > > Thanks to my co-author

Re: [VOTE] FLIP-535: Introduce RateLimiter to Source

2025-09-03 Thread Yanquan Lv
+1(binding), and I am committed to driving forward the subsequent work items. Best, Yanquan Jiangang Liu 于2025年9月3日周三 15:59写道: > +1 (non-binding). > > Best Regards, > Jiangang Liu > > Xiqian YU 于2025年9月3日周三 15:04写道: > > > +1 (non-binding). > > > > Best Regards, > > Xiqian > > > > > 2025年8月21日

[jira] [Created] (FLINK-38279) Failed to restore job when using MySQL Source with scan.startup.mode=snapshot in streaming mode

2025-08-22 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38279: -- Summary: Failed to restore job when using MySQL Source with scan.startup.mode=snapshot in streaming mode Key: FLINK-38279 URL: https://issues.apache.org/jira/browse/FLINK-38279

[jira] [Created] (FLINK-38248) The default value of '0000-00-00 00:00:00' for MySQL TIMESTAMP fields is not supported in downstream systems.

2025-08-14 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38248: -- Summary: The default value of '-00-00 00:00:00' for MySQL TIMESTAMP fields is not supported in downstream systems. Key: FLINK-38248 URL: https://issues.apache.org/j

[jira] [Created] (FLINK-38247) MySqlChunkSplitter may continuously generate splits when using BIGINT UNSIGNED as primary key

2025-08-14 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38247: -- Summary: MySqlChunkSplitter may continuously generate splits when using BIGINT UNSIGNED as primary key Key: FLINK-38247 URL: https://issues.apache.org/jira/browse/FLINK-38247

[jira] [Created] (FLINK-38238) Failed to process MySQL table with varchar(0) column

2025-08-13 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38238: -- Summary: Failed to process MySQL table with varchar(0) column Key: FLINK-38238 URL: https://issues.apache.org/jira/browse/FLINK-38238 Project: Flink Issue Type

Re: [ANNOUNCE] New Apache Flink PMC Member - Ron Liu

2025-08-12 Thread Yanquan Lv
Congrats, Ron! Best Regards, Yanquan Lincoln Lee 于2025年8月13日周三 10:41写道: > On behalf of the PMC, I'm very happy to announce a new Apache Flink PMC > Member > - Ron Liu. > > Ron has been a dedicated and invaluable contributor to the Flink community > for > several years. He became a committer in

[KINDLY REMINDER] Flink CDC 3.5.0 Feature Freeze

2025-08-08 Thread Yanquan Lv
Hi, devs As mentioned in the Kick-off email, we plan to release *Flink CDC 3.5.0* at the end of August. Since the core development work(Fluss/PostgreSQL connector, optimization for multi-table synchronization scenarios) has been completed, we plan to implement a *feature freeze* on *August 24th*.

[jira] [Created] (FLINK-38213) Failed

2025-08-07 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38213: -- Summary: Failed Key: FLINK-38213 URL: https://issues.apache.org/jira/browse/FLINK-38213 Project: Flink Issue Type: Sub-task Reporter: Yanquan Lv

[jira] [Created] (FLINK-38206) Update Paimon Table based on upstream schema to avoid inconsistent table structures

2025-08-06 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38206: -- Summary: Update Paimon Table based on upstream schema to avoid inconsistent table structures Key: FLINK-38206 URL: https://issues.apache.org/jira/browse/FLINK-38206

[jira] [Created] (FLINK-38204) When using route in pipeline, failed to write to MaxCompute sink

2025-08-06 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38204: -- Summary: When using route in pipeline, failed to write to MaxCompute sink Key: FLINK-38204 URL: https://issues.apache.org/jira/browse/FLINK-38204 Project: Flink

[jira] [Created] (FLINK-38203) Failed case: FlussPipelineITCase.testInsertExistTableWithMoreColumns

2025-08-06 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38203: -- Summary: Failed case: FlussPipelineITCase.testInsertExistTableWithMoreColumns Key: FLINK-38203 URL: https://issues.apache.org/jira/browse/FLINK-38203 Project: Flink

[jira] [Created] (FLINK-38191) [Document] Add document for Fluss pipeline connector

2025-08-05 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38191: -- Summary: [Document] Add document for Fluss pipeline connector Key: FLINK-38191 URL: https://issues.apache.org/jira/browse/FLINK-38191 Project: Flink Issue Type

[jira] [Created] (FLINK-38186) Failed case: NewlyAddedTableITCase.testJobManagerFailoverForNewlyAddedTableWithAheadBinlog

2025-08-04 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38186: -- Summary: Failed case: NewlyAddedTableITCase.testJobManagerFailoverForNewlyAddedTableWithAheadBinlog Key: FLINK-38186 URL: https://issues.apache.org/jira/browse/FLINK-38186

[jira] [Created] (FLINK-38185) Failed case: IcebergWriterTest.testWriteWithAllSupportedTypes

2025-08-04 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38185: -- Summary: Failed case: IcebergWriterTest.testWriteWithAllSupportedTypes Key: FLINK-38185 URL: https://issues.apache.org/jira/browse/FLINK-38185 Project: Flink

[jira] [Created] (FLINK-38156) Pipeline E2E tests are currently bound to fail.

2025-07-29 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38156: -- Summary: Pipeline E2E tests are currently bound to fail. Key: FLINK-38156 URL: https://issues.apache.org/jira/browse/FLINK-38156 Project: Flink Issue Type

Re: [DISCUSS] FLIP-529 Connections in Flink SQL and Table API

2025-07-27 Thread Yanquan Lv
Hi Mayank and Hao, Thanks for the updates and comments. Here are some of my opinions: (1) I agree with the design of SecretStore. I hope to add the results of the 'SHOW Connections' query to the document, 'secret.id' should be included in the results, This helps us establish the association betwee

[jira] [Created] (FLINK-38139) Schema changes still caused issues after enabling scan.parse.online.schema.changes.enabled

2025-07-23 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38139: -- Summary: Schema changes still caused issues after enabling scan.parse.online.schema.changes.enabled Key: FLINK-38139 URL: https://issues.apache.org/jira/browse/FLINK-38139

Re: [VOTE] Release flink-connector-aws v5.1.0, release candidate #1

2025-07-21 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK8 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog and LGTM Best, Yanquan Daren Wong 于2025年7月7日周一 18:41写道: > +1 (non-bi

[jira] [Created] (FLINK-38119) [Unstable test]IcebergWriterTest.testWriteWithAllSupportedTypes:344

2025-07-17 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-38119: -- Summary: [Unstable test]IcebergWriterTest.testWriteWithAllSupportedTypes:344 Key: FLINK-38119 URL: https://issues.apache.org/jira/browse/FLINK-38119 Project: Flink

Re: Need invite link for the Flink community on Slack

2025-05-28 Thread Yanquan Lv
Hi, Siva. You can use this link[1] to join Flink community on Slack. We will update the link on getting-help page later. [1] https://apache-flink.slack.com/join/shared_invite/zt-36qpbfpc0-wtlsC7lmeEUy5cw0VTHdag#/shared-invite/email Siva Ram Gujju 于2025年5月29日周四 02:30写道: > Hello, > > The invite

[jira] [Created] (FLINK-37855) Reduce the time cost in MySqlSchemaUtils#listTables

2025-05-27 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37855: -- Summary: Reduce the time cost in MySqlSchemaUtils#listTables Key: FLINK-37855 URL: https://issues.apache.org/jira/browse/FLINK-37855 Project: Flink Issue Type

Re: [Discuss] Flink CDC 3.4 Kick Off, [Discuss] Flink CDC 3.5 Kick Off

2025-05-26 Thread Yanquan Lv
sorry for the title and update: [Discuss] Flink CDC 3.5 Kick Off Yanquan Lv 于2025年5月27日周二 11:36写道: > Hi devs, > > As FlinkCDC 3.4 was released recently, it's a good time to kick off the > upcoming Flink CDC 3.5 release cycle. > > In the past two major versions, w

[Discuss] Flink CDC 3.4 Kick Off, [Discuss] Flink CDC 3.5 Kick Off

2025-05-26 Thread Yanquan Lv
Hi devs, As FlinkCDC 3.4 was released recently, it's a good time to kick off the upcoming Flink CDC 3.5 release cycle. In the past two major versions, we have made significant optimizations to the capability of schema evolution, this feature is quite stable now. In this version, we will focus on

[jira] [Created] (FLINK-37847) [umbrella] Unstable test in FlinkCDC project

2025-05-25 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37847: -- Summary: [umbrella] Unstable test in FlinkCDC project Key: FLINK-37847 URL: https://issues.apache.org/jira/browse/FLINK-37847 Project: Flink Issue Type

[jira] [Created] (FLINK-37846) [Unstable test] MysqlToKafkaE2eITCase.testSyncWholeDatabaseWithDebeziumJson

2025-05-25 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37846: -- Summary: [Unstable test] MysqlToKafkaE2eITCase.testSyncWholeDatabaseWithDebeziumJson Key: FLINK-37846 URL: https://issues.apache.org/jira/browse/FLINK-37846 Project

[jira] [Created] (FLINK-37837) Always Add create.table to include.schema.changes option

2025-05-22 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37837: -- Summary: Always Add create.table to include.schema.changes option Key: FLINK-37837 URL: https://issues.apache.org/jira/browse/FLINK-37837 Project: Flink Issue

[ANNOUNCE] Apache Flink CDC 3.4.0 released

2025-05-16 Thread Yanquan Lv
The Apache Flink community is very happy to announce the release of Apache Flink CDC 3.4.0. Apache Flink CDC is a distributed data integration tool for real time data and batch data, bringing the simplicity and elegance of data integration via YAML to describe the data movement and transformation

[RESULT] [VOTE] Apache Flink CDC Release 3.4.0, release candidate #3

2025-05-15 Thread Yanquan Lv
I'm happy to announce that we have unanimously approved this release. There are 9 approving votes, 4 of which are binding: * Xiqian YU non-binding * Ferenc Csaky non-binding * Tianzhu non-binding * ouyangwulin non-binding * Leonard Xu binding * Zakelly Lan binding * Xingbo Huang binding *

[jira] [Created] (FLINK-37786) Infer schema information from the state of Source and emit it to avoid maintaining state in PreTransform

2025-05-13 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37786: -- Summary: Infer schema information from the state of Source and emit it to avoid maintaining state in PreTransform Key: FLINK-37786 URL: https://issues.apache.org/jira/browse/FLINK

Re: [VOTE] Apache Flink CDC Release 3.4.0, release candidate #3

2025-05-13 Thread Yanquan Lv
gt; > > > > > > > > > > Best, > > > > Zakelly > > > > > > > > On Wed, May 7, 2025 at 10:57 AM Leonard Xu > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > - verified

[VOTE] Apache Flink CDC Release 3.4.0, release candidate #3

2025-04-29 Thread Yanquan Lv
Hi everyone, Please review and vote on the release candidate #3 for the version 3.4.0 of Apache Flink CDC, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) *Release Overview* As an overview, the release consists of the following: a) Flink

Re: [VOTE] Apache Flink CDC Release 3.4.0, release candidate #2

2025-04-29 Thread Yanquan Lv
merged. > > > > [1] https://issues.apache.org/jira/browse/FLINK-37104 > > [2] https://issues.apache.org/jira/browse/FLINK-37738 > > [3] > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12355589 > > > > Best >

[jira] [Created] (FLINK-37743) Add benchmark test for Flink CDC Pipeline job

2025-04-28 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37743: -- Summary: Add benchmark test for Flink CDC Pipeline job Key: FLINK-37743 URL: https://issues.apache.org/jira/browse/FLINK-37743 Project: Flink Issue Type

[VOTE] Apache Flink CDC Release 3.4.0, release candidate #2

2025-04-27 Thread Yanquan Lv
Hi everyone, Please review and vote on the release candidate #2 for the version 3.4.0 of Apache Flink CDC, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) *Release Overview* As an overview, the release consists of the following: a) Flin

Re: [VOTE] Apache Flink CDC Release 3.4.0, release candidate #1

2025-04-27 Thread Yanquan Lv
but seems it’s still > labeled as 3.4-SNAPSHOT. Maybe we should recompile it with the latest > release-3.4 branch? > > Best Regards, > Xiqian > > > 2025年4月27日 17:33,Yanquan Lv 写道: > > > > Hi everyone, > > > > Please review and vote on the release can

[VOTE] Apache Flink CDC Release 3.4.0, release candidate #1

2025-04-27 Thread Yanquan Lv
Hi everyone, Please review and vote on the release candidate #1 for the version 3.4.0 of Apache Flink CDC, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) *Release Overview* As an overview, the release consists of the following: a) Fl

[DISCUSS] Release Flink CDC version 3.4.0

2025-04-26 Thread Yanquan Lv
Hi everyone, Flink CDC v3.4.0 [1] has already updated Flink dependency to 1.20, added Iceberg pipeline sink and introduced many important features like Batch execution mode. The major development work we mentioned in the 3.4.0 kick off has been completed. and I think it's a good time to start the

[jira] [Created] (FLINK-37734) Update version to 3.5-SNAPSHOT and update related docs

2025-04-26 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37734: -- Summary: Update version to 3.5-SNAPSHOT and update related docs Key: FLINK-37734 URL: https://issues.apache.org/jira/browse/FLINK-37734 Project: Flink Issue

[jira] [Created] (FLINK-37731) Update dependency of Paimon to 1.1 and add support for Postpone Bucket

2025-04-25 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37731: -- Summary: Update dependency of Paimon to 1.1 and add support for Postpone Bucket Key: FLINK-37731 URL: https://issues.apache.org/jira/browse/FLINK-37731 Project: Flink

[jira] [Created] (FLINK-37726) Read incremental data for existing tables

2025-04-24 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37726: -- Summary: Read incremental data for existing tables Key: FLINK-37726 URL: https://issues.apache.org/jira/browse/FLINK-37726 Project: Flink Issue Type

[jira] [Created] (FLINK-37713) SchemaManager was recreated in SchemaRegistry after job failover

2025-04-22 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37713: -- Summary: SchemaManager was recreated in SchemaRegistry after job failover Key: FLINK-37713 URL: https://issues.apache.org/jira/browse/FLINK-37713 Project: Flink

[jira] [Created] (FLINK-37712) Table

2025-04-21 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37712: -- Summary: Table Key: FLINK-37712 URL: https://issues.apache.org/jira/browse/FLINK-37712 Project: Flink Issue Type: Bug Reporter: Yanquan Lv

Re: [VOTE] Release flink-connector-kafka v4.0.0, release candidate #3

2025-04-21 Thread Yanquan Lv
Gentle ping for more binding votes. Tom Cooper 于2025年4月17日周四 20:09写道: > Hi Arvid, > > Thanks for looking at this. I can confirm that updated sources now compile > on my Fedora box. I still get the following warning when running tar -xf: > > tar: Ignoring unknown extended header keyword > 'LIBARC

Re: [VOTE] Release flink-connector-jdbc v3.3.0, release candidate #2

2025-04-18 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK8 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog - Check all CI action passing Hang Ruan 于2025年4月17日周四 20:37写道: > Hi e

[jira] [Created] (FLINK-37699) Overwrite the parameters of the created Paimon table through table options

2025-04-18 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37699: -- Summary: Overwrite the parameters of the created Paimon table through table options Key: FLINK-37699 URL: https://issues.apache.org/jira/browse/FLINK-37699 Project

Re: [VOTE] Release flink-connector-jdbc v4.0.0, release candidate #2

2025-04-17 Thread Yanquan Lv
Hi, Hang. I found that there is a failure in Flink Connector JDBC CI Backwards Compatibility[1], and the cause is pom.xml of flink-connector-jdbc-backward-compatibility is still 4.0-SNAPSHOT. We need to modify it to the correct version, so I -1 for this. [1] https://github.com/apache/flink-connect

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

2025-04-16 Thread Yanquan Lv
Congratulations! Best, Yanquan Jiabao Sun 于2025年4月16日周三 20:25写道: > Congrats Xiqian! > > Best, > Jiabao > > On 2025/04/16 07:25:19 Leonard Xu wrote: > > Hi everyone, > > > > On behalf of the PMC, I'm happy to let you know that Xiqian Yu has > become a new Flink Committer! > > > > Since joining t

[jira] [Created] (FLINK-37676) Add a cache for TableId in Selector to improve performance

2025-04-15 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37676: -- Summary: Add a cache for TableId in Selector to improve performance Key: FLINK-37676 URL: https://issues.apache.org/jira/browse/FLINK-37676 Project: Flink Issue

[jira] [Created] (FLINK-37673) The transformation of table metadata should only be effective for the first matching rule

2025-04-14 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37673: -- Summary: The transformation of table metadata should only be effective for the first matching rule Key: FLINK-37673 URL: https://issues.apache.org/jira/browse/FLINK-37673

[jira] [Created] (FLINK-37667) Make PostTransformOperator always chain with before Operator

2025-04-13 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37667: -- Summary: Make PostTransformOperator always chain with before Operator Key: FLINK-37667 URL: https://issues.apache.org/jira/browse/FLINK-37667 Project: Flink

Re: [VOTE] Release flink-connector-kafka v4.0.0, release candidate #3

2025-04-11 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK17 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog and LGTM - Run a sql test for Kafka Source & Sink with Flink 2.0 clust

Re: [VOTE] Release flink-connector-elasticsearch v4.0.0, release candidate #2

2025-04-11 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK17 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog and LGTM - Run a datagen to elasticsearch7 test with Flink 2.0 cluster

Re: [VOTE] Release flink-connector-kafka v4.0.0, release candidate #2

2025-04-10 Thread Yanquan Lv
to a unique prefix > (e.g. org.apache.flink.connector.kafka). > Then SQL module will simply use that relocation transitively. > WDYT? > > Best, > > Arvid > > On Wed, Apr 9, 2025 at 6:38 PM Yanquan Lv wrote: > > > I checked: > > - Review JIRA release notes

Re: [VOTE] Release flink-connector-jdbc v3.3.0, release candidate #1

2025-04-10 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK8 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog Hang Ruan 于2025年4月10日周四 11:57写道: > Hi everyone, > Please review and v

[jira] [Created] (FLINK-37644) Include guava dependency to package of Kafka connector release and shade

2025-04-09 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37644: -- Summary: Include guava dependency to package of Kafka connector release and shade Key: FLINK-37644 URL: https://issues.apache.org/jira/browse/FLINK-37644 Project: Flink

Re: [VOTE] Release flink-connector-kafka v4.0.0, release candidate #2

2025-04-09 Thread Yanquan Lv
I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK17 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog - Verify that the major version is 55 I am trying to use the jar flink-sql-connector-k

Re: [VOTE] Release flink-connector-elasticsearch v4.0.0, release candidate #1

2025-04-09 Thread Yanquan Lv
Hi, Weijie. Sorry for reply again, But I found that the major version of the release jar is 52 using `javap -classpath flink-sql-connector-elasticsearch7-4.0.0-2.0.jar -verbose org.apache.flink.connector.elasticsearch.Elasticsearch7ApiCallBridge | grep version`, Is this not as expected? Do we need

Re: [VOTE] Release flink-connector-elasticsearch v3.1.0, release candidate #1

2025-04-09 Thread Yanquan Lv
> 1.17...). > > Anyway, what you mentioned is really a meaningful feature, but I would > prefer to include it in next release. WDYT? > > > Best regards, > > Weijie > > > Yanquan Lv 于2025年4月9日周三 11:30写道: > > > I checked: > > - Review JIRA re

Re: [VOTE] Release flink-connector-kafka v4.0.0, release candidate #1

2025-04-09 Thread Yanquan Lv
Sorry for the previous conclusion, I have confirmed again and found that the major version is 52, as you and Xiqian mentioned. But fortunately, we can confirm and discover the actual problem. Arvid Heise 于2025年4月8日周二 22:09写道: > Hi everyone, > Please review and vote on release candidate #1 for fl

Re: [VOTE] Release flink-connector-kudu v2.0.0, release candidate #1

2025-04-09 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK11 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog and LGTM Ferenc Csaky 于2025年3月28日周五 21:34写道: > Hi everyone, > > Ple

Re: [VOTE] Release flink-connector-elasticsearch v4.0.0, release candidate #1

2025-04-08 Thread Yanquan Lv
+1 (non-binding) I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK11 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog and LGTM - Run a datagen to elasticsearch7 test with Flink 2.0 cluster

[jira] [Created] (FLINK-37636) Weekly CI failure

2025-04-08 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37636: -- Summary: Weekly CI failure Key: FLINK-37636 URL: https://issues.apache.org/jira/browse/FLINK-37636 Project: Flink Issue Type: Improvement Components

Re: [VOTE] Release flink-connector-kafka v4.0.0, release candidate #1

2025-04-08 Thread Yanquan Lv
Hi, Arvid. Thanks for your efforts in this release. I noticed that this released version was compiled using JDK 17, and there is also flink-connector-elasticsearch[1] support for Flink 2.0 release, which is compiled using JDK 11. I checked the compiled version of Flink 2.0 release, which is also j

Re: [VOTE] Release flink-connector-elasticsearch v3.1.0, release candidate #1

2025-04-08 Thread Yanquan Lv
I checked: - Review JIRA release notes - Verify hashes and verify signatures - Build success from source with JDK11 & maven3.8.6 - Source code artifacts matching the current release - Read the announcement blog and LGTM I noticed that we have supported ElasticSearch8 in this release and provided t

Re: [ANNOUNCE] New Apache Flink PMC Member - Sergey Nuyanzin

2025-04-08 Thread Yanquan Lv
Congrations, Sergey! Best, Yanquan > 2025年4月3日 14:54,Dawid Wysakowicz 写道: > > On behalf of the PMC, I'm very happy to announce a new Apache Flink PMC > Member > - Sergey Nuyanzin. > > Sergey has been a dedicated and invaluable contributor to the Flink > community for several years. He became a

Re: [DISCUSS] FLIP-515: Dynamic Kafka Sink

2025-04-05 Thread Yanquan Lv
State is there to support situations where MDS is not accessible, it > stores the cached metadata in the state > > I hope it clarifies, > Matyas > > On Sat, Apr 5, 2025 at 9:55 AM Yanquan Lv wrote: > > > Hi, Matyas. Thanks for driving this. > > I have some ques

Re: [DISCUSS] FLIP-515: Dynamic Kafka Sink

2025-04-05 Thread Yanquan Lv
Hi, Matyas. Thanks for driving this. I have some questions and I hope you can help explain them: 1. The dynamic Kafka Sink looks like only be used in DataStream jobs currently, will it be considered to be supported in TableAPI in the future? 2. Even though we have Kafka MetaData Service, due to th

Re: [ANNOUNCE] New Apache Flink PMC Member - Zakelly Lan

2025-04-01 Thread Yanquan Lv
Congrats, Zakelly! Best, Yanquan. > 2025年4月1日 15:51,Yuan Mei 写道: > > On behalf of the PMC, I'm very happy to announce a new Apache Flink PMC Member > - Zakelly Lan. > > Zakelly has been a dedicated and invaluable contributor to the Flink > community for over five years. He became a committer e

Re: Flink Kafka Connector: Release and Kafka client versions

2025-04-01 Thread Yanquan Lv
Hi, Cooper. Thank you for bringing up the discussion about Kafka 4.0.0. I tend to release Kafka Connector 4.0 with Flink 2.0.0 and Kafka 3.9.0, or Kafka 3.8.1 if If the community is concerned about 3.9.0. Here are some of my opinions: 1. The plan for Kafka Connector 4.0.0 was proposed[1] a long

[jira] [Created] (FLINK-37590) Update the code of Python modules to adapt to Flink 2.0's pyFlink

2025-03-31 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37590: -- Summary: Update the code of Python modules to adapt to Flink 2.0's pyFlink Key: FLINK-37590 URL: https://issues.apache.org/jira/browse/FLINK-37590 Project:

[jira] [Created] (FLINK-37587) Fail to add a new column that has the same column name with source table using transform

2025-03-30 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37587: -- Summary: Fail to add a new column that has the same column name with source table using transform Key: FLINK-37587 URL: https://issues.apache.org/jira/browse/FLINK-37587

[jira] [Created] (FLINK-37577) Wait compaction only when table set deletion-vectors.enabled to true in PaimonWriter

2025-03-28 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37577: -- Summary: Wait compaction only when table set deletion-vectors.enabled to true in PaimonWriter Key: FLINK-37577 URL: https://issues.apache.org/jira/browse/FLINK-37577

[jira] [Created] (FLINK-37572) Shuffle Event by bucket and tableid to avoid data skew

2025-03-27 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37572: -- Summary: Shuffle Event by bucket and tableid to avoid data skew Key: FLINK-37572 URL: https://issues.apache.org/jira/browse/FLINK-37572 Project: Flink Issue

[jira] [Created] (FLINK-37566) table.exclude was invalid in binlog reading phase when scan.binlog.newly-added-table.enabled

2025-03-26 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37566: -- Summary: table.exclude was invalid in binlog reading phase when scan.binlog.newly-added-table.enabled Key: FLINK-37566 URL: https://issues.apache.org/jira/browse/FLINK-37566

[jira] [Created] (FLINK-37539) performance optimization in Paimon Sink to reduce end-to-end checkpoint time

2025-03-24 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37539: -- Summary: performance optimization in Paimon Sink to reduce end-to-end checkpoint time Key: FLINK-37539 URL: https://issues.apache.org/jira/browse/FLINK-37539 Project

[jira] [Created] (FLINK-37519) Add clearer logs when fail to write to YAML DataSink.

2025-03-19 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37519: -- Summary: Add clearer logs when fail to write to YAML DataSink. Key: FLINK-37519 URL: https://issues.apache.org/jira/browse/FLINK-37519 Project: Flink Issue Type

Re: [VOTE] Release 2.0.0, release candidate #2

2025-03-16 Thread Yanquan Lv
+1 (non-binding) - Verified signatures and sha512 - Compiled the project with java 17 and maven 3.8.6 - Ran a sql test for filesystem connector with csv format in standalone cluster and it worked as expected > 2025年3月10日 17:05,Xintong Song 写道: > > Hi everyone, > > There were some blocker issu

[jira] [Created] (FLINK-37462) Unstable test case in FlinkParallelizedPipelineITCase.testRegularTablesSourceInMultipleParallelism

2025-03-11 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37462: -- Summary: Unstable test case in FlinkParallelizedPipelineITCase.testRegularTablesSourceInMultipleParallelism Key: FLINK-37462 URL: https://issues.apache.org/jira/browse/FLINK-37462

[jira] [Created] (FLINK-37461) Unstable test case in MySqlToPaimonE2eITCase#testSyncWholeDatabase

2025-03-11 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37461: -- Summary: Unstable test case in MySqlToPaimonE2eITCase#testSyncWholeDatabase Key: FLINK-37461 URL: https://issues.apache.org/jira/browse/FLINK-37461 Project: Flink

[jira] [Created] (FLINK-37452) Add support for writing to Paimon Append only table.

2025-03-10 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37452: -- Summary: Add support for writing to Paimon Append only table. Key: FLINK-37452 URL: https://issues.apache.org/jira/browse/FLINK-37452 Project: Flink Issue Type

[jira] [Created] (FLINK-37386) Avoid sending too much CreateTableEvents when job failover

2025-02-26 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37386: -- Summary: Avoid sending too much CreateTableEvents when job failover Key: FLINK-37386 URL: https://issues.apache.org/jira/browse/FLINK-37386 Project: Flink

Re: [ANNOUNCE] New Apache Flink Committer - Xuyang

2025-02-19 Thread Yanquan Lv
Congratulations, Xuyang! Best, Yanquan. > 2025年2月20日 10:24,Zakelly Lan 写道: > > Congratulations, Xuyang!

[jira] [Created] (FLINK-37353) [Doc] Add doc for scan.incremental.snapshot.chunk.key-column Mysql Data Sink

2025-02-19 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37353: -- Summary: [Doc] Add doc for scan.incremental.snapshot.chunk.key-column Mysql Data Sink Key: FLINK-37353 URL: https://issues.apache.org/jira/browse/FLINK-37353 Project

[jira] [Created] (FLINK-37352) Write full changelog to Paimon Sink.

2025-02-19 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37352: -- Summary: Write full changelog to Paimon Sink. Key: FLINK-37352 URL: https://issues.apache.org/jira/browse/FLINK-37352 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-37349) Add timeout for test case that call waitForSinkSize method to avoid Infinite waiting

2025-02-18 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37349: -- Summary: Add timeout for test case that call waitForSinkSize method to avoid Infinite waiting Key: FLINK-37349 URL: https://issues.apache.org/jira/browse/FLINK-37349

[jira] [Created] (FLINK-37346) [CI] Unit Tests (mysql) / compile_and_test (8, generic) (pull_request)Failing after 60m

2025-02-18 Thread Yanquan Lv (Jira)
Yanquan Lv created FLINK-37346: -- Summary: [CI] Unit Tests (mysql) / compile_and_test (8, generic) (pull_request)Failing after 60m Key: FLINK-37346 URL: https://issues.apache.org/jira/browse/FLINK-37346

Re: Plans for JDBC connector for 1.20?

2025-02-18 Thread Yanquan Lv
support. Yes and support for the new dialects. >>>>> >>>>> It would be great to get open PRs merged to support new dialect if >>>>> possible, including: >>>>> https://github.com/apache/flink-connector-jdbc/pull/118 - this has >>> been &g

Re: Kafka connector releases

2025-02-13 Thread Yanquan Lv
imately). I'd leave that decision to >>> the two release managers for 4.0.0 mentioned before. >>> >>> One thing to note for 4.0.0 is that we need to solve the transaction >>> management issues with the KafkaSink [2]. It's blocking larger users from >>

Re: [DISCUSS] FLIP:507 Add Model DDL methods in TABLE API

2025-02-10 Thread Yanquan Lv
Hi, Yash. Thanks for driving it. +1 for this. > 2025年2月7日 05:28,Yash Anand 写道: > > Hi all! I would like to open up for discussion a new FLIP-507[1]. > Motivation This proposal aims to extend model DDL support to the Table API, > enabling a seamless development experience where users can define,

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

2025-02-10 Thread Yanquan Lv
Hi, Xiangyu. Thanks for driving this. I have a question to confirm: Considering the case that different Sources use different columns[1], will the Schema of CatalogTable[2] contain all target columns for Sources? And for SinkWriter, the data structure to be processed should be fixed. Is there a

  1   2   3   >