Thanks Hongshun and Becket for the deep discussion.
I only have one comment for one API design:
> Deprecate the old addSplitsBack method, use a addSplitsBack with param
> isReportedByReader instead. Because, The enumerator can apply different
> reassignment policies based on the context.
Cou
Dear Flink CDC Community,
My name is LW and I am a user of Flink CDC. I am currently using Flink CDC with
a YAML configuration file to synchronize data from MySQL to Apache Paimon, and
I am very impressed with its capabilities.
I am writing to propose a new feature that I believe would be a valua
Sergey Nuyanzin created FLINK-38318:
---
Summary: Add python autoformatter to pyflink
Key: FLINK-38318
URL: https://issues.apache.org/jira/browse/FLINK-38318
Project: Flink
Issue Type: Bug
david radley created FLINK-38329:
Summary: Add labels to PRs showing the targeted version
Key: FLINK-38329
URL: https://issues.apache.org/jira/browse/FLINK-38329
Project: Flink
Issue Type:
Zakelly Lan created FLINK-38327:
---
Summary: NPE during recovery from file-merged checkpoint after FO
Key: FLINK-38327
URL: https://issues.apache.org/jira/browse/FLINK-38327
Project: Flink
Issue
Hi Ron,
Thanks again for the excellent feedback and for bringing FLIP-492 [1] into
the discussion. I want to address your points on CREATE OR REPLACE vs. CREATE
OR ALTER and the SQL standard.
*1. Semantics of REPLACE vs. ALTER*
You’re right that FLIP-492 [1] proposed CREATE OR REPLACE. However,