[jira] [Created] (FLINK-35469) Unstable test case 'testProject' of JdbcDynamicTableSourceITCase

2024-05-27 Thread RocMarshal (Jira) 
RocMarshal created FLINK-35469:
--

 Summary: Unstable test case 'testProject' of 
JdbcDynamicTableSourceITCase
 Key: FLINK-35469
 URL: https://issues.apache.org/jira/browse/FLINK-35469
 Project: Flink
  Issue Type: Bug
Reporter: RocMarshal


https://github.com/apache/flink-connector-jdbc/actions/runs/9263628064/job/25482376215?pr=119



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-35468) [Connectors/Pulsar] update isEnableAutoAcknowledgeMessage config comment

2024-05-27 Thread zhou zhuohan (Jira) 
zhou zhuohan created FLINK-35468:


 Summary: [Connectors/Pulsar] update isEnableAutoAcknowledgeMessage 
config comment
 Key: FLINK-35468
 URL: https://issues.apache.org/jira/browse/FLINK-35468
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: pulsar-4.1.0
Reporter: zhou zhuohan
 Fix For: pulsar-4.1.0


Since we [deleted {{shared}} and {{key-shared}} subscription 
type|https://issues.apache.org/jira/browse/FLINK-30413] in pulsar source 
connector, I think it is better to remove these subscription type in 
{{isEnableAutoAcknowledgeMessage}} option comment to prevent misunderstanding.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Add Flink CDC Channel to Apache Flink Slack Workspace

2024-05-27 Thread Leonard Xu 


Thanks Zhongqiang for the proposal, we need the Channel and I should have been 
created it but not yet, +1 from my side.

Best,
Leonard

> 2024年5月28日 上午11:54，gongzhongqiang  写道：
> 
> Hi devs,
> 
> I would like to propose adding a dedicated Flink CDC channel to the Apache
> Flink Slack workspace.
> 
> Creating a channel focused on Flink CDC will help community members easily
> find previous discussions
> and target new discussions and questions to the correct place. Flink CDC is
> a sufficiently distinct component
> within the Apache Flink ecosystem, and having a dedicated channel will make
> it viable and useful for
> those specifically working with or interested in this technology.
> 
> Looking forward to your feedback and support on this proposal.
> 
> 
> Best,
> Zhongqiang Gong

[DISCUSS] Add Flink CDC Channel to Apache Flink Slack Workspace

2024-05-27 Thread gongzhongqiang 
Hi devs,

I would like to propose adding a dedicated Flink CDC channel to the Apache
Flink Slack workspace.

Creating a channel focused on Flink CDC will help community members easily
find previous discussions
and target new discussions and questions to the correct place. Flink CDC is
a sufficiently distinct component
within the Apache Flink ecosystem, and having a dedicated channel will make
it viable and useful for
those specifically working with or interested in this technology.

Looking forward to your feedback and support on this proposal.


Best,
Zhongqiang Gong

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

2024-05-27 Thread Xuannan Su 
+1 (non-binding)

Best regards,
Xuannan

On Mon, May 27, 2024 at 3:43 PM Jark Wu  wrote:
>
> +1 (binding)
>
> Best,
> Jark
>
> On Mon, 27 May 2024 at 14:29, Hang Ruan  wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Hang
> >
> > gongzhongqiang  于2024年5月27日周一 14:16写道：
> >
> > > +1 (non-binding)
> > >
> > > Best,
> > > Zhongqiang Gong
> > >
> > > Jane Chan  于2024年5月24日周五 09:52写道：
> > >
> > > > Hi all,
> > > >
> > > > I'd like to start a vote on FLIP-457[1] after reaching a consensus
> > > through
> > > > the discussion thread[2].
> > > >
> > > > The vote will be open for at least 72 hours unless there is an
> > objection
> > > or
> > > > insufficient votes.
> > > >
> > > >
> > > > [1]
> > > >
> > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=307136992
> > > > [2] https://lists.apache.org/thread/1sthbv6q00sq52pp04n2p26d70w4fqj1
> > > >
> > > > Best,
> > > > Jane
> > > >
> > >
> >

[jira] [Created] (FLINK-35467) The flink-cdc.sh script of flink-cdc-3.1.0 cannot read the correct Flink configuration information specified by the flink-conf.yaml through the FLINK_CONF_DIR environmen

2024-05-27 Thread Justin.Liu (Jira) 
Justin.Liu created FLINK-35467:
--

 Summary: The flink-cdc.sh script of flink-cdc-3.1.0 cannot read 
the correct Flink configuration information specified by the flink-conf.yaml 
through the FLINK_CONF_DIR environment variable.
 Key: FLINK-35467
 URL: https://issues.apache.org/jira/browse/FLINK-35467
 Project: Flink
  Issue Type: Improvement
  Components: Flink CDC
Affects Versions: cdc-3.1.0
 Environment: Environment Information:
flink-1.17.1
flink-cdc-3.1.0
Reporter: Justin.Liu


Problem Description:
When starting our Flink service, we use the FLINK_CONF_DIR environment variable 
to specify the flink-conf.yaml to a directory other than $FLINK_HOME/conf. The 
flink-conf.yaml directory under $FLINK_HOME/conf is incorrect.

When submitting CDC tasks using the flink-cdc.sh script of flink-cdc-3.1.0, we 
attempted to let flink-cdc read information from the correct flink-conf.yaml 
configuration file through the FLINK_CONF_DIR environment variable. However, it 
failed, and it still reads the configuration information from the 
flink-conf.yaml under $FLINK_HOME/conf, causing task submission failures.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-35466) Cannot pass all columns to SQL UDFs using `*`

2024-05-27 Thread Gyula Fora (Jira) 
Gyula Fora created FLINK-35466:
--

 Summary: Cannot pass all columns to SQL UDFs using `*`
 Key: FLINK-35466
 URL: https://issues.apache.org/jira/browse/FLINK-35466
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / API, Table SQL / Planner
Affects Versions: 1.18.1
Reporter: Gyula Fora


The SQL API does not allow calling UDFs using all the columns of a given table 
using * notation such as:
{noformat}
tableEnv.executeSql("SELECT MyFun(Orders.*) FROM Orders").print();{noformat}
The above call fails with the following error:
{noformat}
org.apache.flink.table.api.ValidationException: SQL validation failed. At line 
1, column 21: Unknown field '*'
at 
org.apache.flink.table.planner.calcite.FlinkPlannerImpl.org$apache$flink$table$planner$calcite$FlinkPlannerImpl$$validate(FlinkPlannerImpl.scala:200)
at 
org.apache.flink.table.planner.calcite.FlinkPlannerImpl.validate(FlinkPlannerImpl.scala:117)
 at 
org.apache.flink.table.planner.operations.SqlNodeToOperationConversion.convert(SqlNodeToOperationConversion.java:261)
at 
org.apache.flink.table.planner.delegation.ParserImpl.parse(ParserImpl.java:106) 
 at 
org.apache.flink.table.api.internal.TableEnvironmentImpl.executeSql(TableEnvironmentImpl.java:728)
   at com.apple.pie.flink.utils.testing.Test2.test(Test2.java:29)  at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)   at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
   at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
  at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
   at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
at 
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
  at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
   at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:214)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:210)
 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:135)
  at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:66)
   at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
   at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
   at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
   at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)   at

[jira] [Created] (FLINK-35465) Introduce BatchJobRecoveryHandler for recovery of batch jobs from JobMaster failures.

2024-05-27 Thread Junrui Li (Jira) 
Junrui Li created FLINK-35465:
-

 Summary: Introduce BatchJobRecoveryHandler for recovery of batch 
jobs from JobMaster failures.
 Key: FLINK-35465
 URL: https://issues.apache.org/jira/browse/FLINK-35465
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Coordination
Reporter: Junrui Li






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Flink CDC 3.2 Release Planning

2024-05-27 Thread Leonard Xu 
Hey, Xiqian

> In 3.2 KO plannings, it is expected to add some strongly demanded feature to 
> meet YAML pipeline job users’ needs [1]. However, 0 out of 10 3.2 feature 
> tickets have been completed till now, and it’s very unlikely for us to catch 
> up with planned feature freeze (May 25th) and release deadline (June 1st) [2].
> 
> I hereby suggest postponing release schedule by 2 weeks, extending feature 
> freeze day to June 8th and release day to June 15th. Considering its wide 
> affect, please leave your comments & concerns about this suggestion.

Thanks for the proposal, +1 for extending 2 weeks as the 3.1 release requires 
more work than expected.


Best,
Leonard

> 
> Regards,
> Xiqian
> 
> [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=607
> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=303794651
> 
> 
> De : Peter Huang 
> Date : jeudi, 9 mai 2024 à 23:31
> À : dev@flink.apache.org 
> Objet : Re: [DISCUSS] Flink CDC 3.2 Release Planning
> Thanks Qingsheng for driving the release!
> 
> +1. I also would like to provide some help on CDC 3.2.
> 
> 
> Best Regards
> Peter Huang
> 
> On Thu, May 9, 2024 at 3:21 AM Xiqian YU  wrote:
> 
>> Thanks Qingsheng for driving the release!
>> 
>> +1. Would love to provide my help on CDC 3.2.
>> 
>> Regards,
>> Xiqian
>> 
>> De : Hang Ruan 
>> Date : jeudi, 9 mai 2024 à 17:50
>> À : dev@flink.apache.org 
>> Objet : Re: [DISCUSS] Flink CDC 3.2 Release Planning
>> Thanks Qinsheng for driving.
>> 
>> I would like to provide some helps for this verison too. +1.
>> 
>> Best,
>> Hang
>> 
>> Hongshun Wang  于2024年5月9日周四 14:16写道：
>> 
>>> Thanks Qinsheng for driving,
>>> +1 from my side.
>>> 
>>> Besi,
>>> Hongshun
>>> 
>>> On Wed, May 8, 2024 at 11:41 PM Leonard Xu  wrote:
>>> 
 +1 for the proposal code freeze date and RM candidate.
 
 Best,
 Leonard
 
> 2024年5月8日 下午10:27，gongzhongqiang  写道：
> 
> Hi Qingsheng
> 
> Thank you for driving the release.
> Agree with the goal and I'm willing to help.
> 
> Best,
> Zhongqiang Gong
> 
> Qingsheng Ren  于2024年5月8日周三 14:22写道：
> 
>> Hi devs,
>> 
>> As we are in the midst of the release voting process for Flink CDC
 3.1.0, I
>> think it's a good time to kick off the upcoming Flink CDC 3.2
>> release
>> cycle.
>> 
>> In this release cycle I would like to focus on the stability of
>> Flink
 CDC,
>> especially for the newly introduced YAML-based data integration
>> framework. To ensure we can iterate and improve swiftly, I propose
>> to
 make
>> 3.2 a relatively short release cycle, targeting a feature freeze by
>>> May
 24,
>> 2024.
>> 
>> For developers that are interested in participating and contributing
>>> new
>> features in this release cycle, please feel free to list your
>> planning
>> features in the wiki page [1].
>> 
>> I'm happy to volunteer as a release manager and of course open to
>> work
>> together with someone on this.
>> 
>> What do you think?
>> 
>> Best,
>> Qingsheng
>> 
>> [1]
>> 
>>> https://cwiki.apache.org/confluence/display/FLINK/Flink+CDC+3.2+Release
>> 
 
 
>>> 
>>

[jira] [Created] (FLINK-35464) Flink CDC 3.1 breaks operator state compatiblity

2024-05-27 Thread yux (Jira) 
yux created FLINK-35464:
---

 Summary: Flink CDC 3.1 breaks operator state compatiblity
 Key: FLINK-35464
 URL: https://issues.apache.org/jira/browse/FLINK-35464
 Project: Flink
  Issue Type: Bug
  Components: Flink CDC
Affects Versions: cdc-3.1.0
Reporter: yux
 Fix For: cdc-3.1.1


Flink CDC 3.1 changed how SchemaRegistry [de]serializes state data, which 
causes any checkpoint states saved with earlier version could not be restored 
in version 3.1.0.

This could be resolved by adding serialization versioning control logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Flink 1.19.1 release

2024-05-27 Thread weijie guo 
+1 for releasing 1.19.1 and Hong as RM.

Thank you for volunteering!

Best regards,

Weijie


Rui Fan <1996fan...@gmail.com> 于2024年5月27日周一 11:45写道：

> +1 for release 1.19.1 and Hong as release manager.
>
> We are really looking forward to this version, thank you.
>
> Best,
> Rui
>
> On Mon, May 27, 2024 at 11:05 AM Xintong Song 
> wrote:
>
> > +1 for the 1.19.1 release and +1 for Hong as the release manager.
> >
> > Hong, if you need help on PMC-related steps and Danny is not available,
> > please feel free to reach out to me on slack.
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Mon, May 27, 2024 at 9:44 AM Leonard Xu  wrote:
> >
> > > +1 for the 1.19.1 release and +1 for Hong as release manager.
> > >
> > > Best,
> > > Leonard
> > >
> > > > 2024年5月25日 上午2:55，Danny Cranmer  写道：
> > > >
> > > > +1 for the 1.19.1 release and +1 for Hong as release manager.
> > >
> > >
> >
>

Re: [DISCUSS] Flink CDC 3.2 Release Planning

2024-05-27 Thread Muhammet Orazov 

Hey Xiqian,

+1 to the change of schedule

Thanks and best,
Muhammet

On 2024-05-27 02:36, Xiqian YU wrote:

Hi devs,

Glad to see Flink CDC 3.1’s successful release! Also noticed that it’s 
a delayed release due to license compliance chores, which took more 
than half a month to process.


In 3.2 KO plannings, it is expected to add some strongly demanded 
feature to meet YAML pipeline job users’ needs [1]. However, 0 out of 
10 3.2 feature tickets have been completed till now, and it’s very 
unlikely for us to catch up with planned feature freeze (May 25th) and 
release deadline (June 1st) [2].


I hereby suggest postponing release schedule by 2 weeks, extending 
feature freeze day to June 8th and release day to June 15th. 
Considering its wide affect, please leave your comments & concerns 
about this suggestion.


Regards,
Xiqian

[1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=607
[2] 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=303794651



De : Peter Huang 
Date : jeudi, 9 mai 2024 à 23:31
À : dev@flink.apache.org 
Objet : Re: [DISCUSS] Flink CDC 3.2 Release Planning
Thanks Qingsheng for driving the release!

+1. I also would like to provide some help on CDC 3.2.


Best Regards
Peter Huang

On Thu, May 9, 2024 at 3:21 AM Xiqian YU  wrote:


Thanks Qingsheng for driving the release!

+1. Would love to provide my help on CDC 3.2.

Regards,
Xiqian

De : Hang Ruan 
Date : jeudi, 9 mai 2024 à 17:50
À : dev@flink.apache.org 
Objet : Re: [DISCUSS] Flink CDC 3.2 Release Planning
Thanks Qinsheng for driving.

I would like to provide some helps for this verison too. +1.

Best,
Hang

Hongshun Wang  于2024年5月9日周四 14:16写道：

> Thanks Qinsheng for driving,
> +1 from my side.
>
> Besi,
> Hongshun
>
> On Wed, May 8, 2024 at 11:41 PM Leonard Xu  wrote:
>
> > +1 for the proposal code freeze date and RM candidate.
> >
> > Best,
> > Leonard
> >
> > > 2024年5月8日 下午10:27，gongzhongqiang  写道：
> > >
> > > Hi Qingsheng
> > >
> > > Thank you for driving the release.
> > > Agree with the goal and I'm willing to help.
> > >
> > > Best,
> > > Zhongqiang Gong
> > >
> > > Qingsheng Ren  于2024年5月8日周三 14:22写道：
> > >
> > >> Hi devs,
> > >>
> > >> As we are in the midst of the release voting process for Flink CDC
> > 3.1.0, I
> > >> think it's a good time to kick off the upcoming Flink CDC 3.2
release
> > >> cycle.
> > >>
> > >> In this release cycle I would like to focus on the stability of
Flink
> > CDC,
> > >> especially for the newly introduced YAML-based data integration
> > >> framework. To ensure we can iterate and improve swiftly, I propose
to
> > make
> > >> 3.2 a relatively short release cycle, targeting a feature freeze by
> May
> > 24,
> > >> 2024.
> > >>
> > >> For developers that are interested in participating and contributing
> new
> > >> features in this release cycle, please feel free to list your
planning
> > >> features in the wiki page [1].
> > >>
> > >> I'm happy to volunteer as a release manager and of course open to
work
> > >> together with someone on this.
> > >>
> > >> What do you think?
> > >>
> > >> Best,
> > >> Qingsheng
> > >>
> > >> [1]
> > >>
> https://cwiki.apache.org/confluence/display/FLINK/Flink+CDC+3.2+Release
> > >>
> >
> >
>

Re: [DISCUSS] Flink CDC 3.2 Release Planning

2024-05-27 Thread He Wang 
+1 for the new schedule. I think it can reduce the work pressure of the
committers, and it's also good for ensuring the code quality.

On Mon, May 27, 2024 at 10:37 AM Xiqian YU  wrote:

> Hi devs,
>
> Glad to see Flink CDC 3.1’s successful release! Also noticed that it’s a
> delayed release due to license compliance chores, which took more than half
> a month to process.
>
> In 3.2 KO plannings, it is expected to add some strongly demanded feature
> to meet YAML pipeline job users’ needs [1]. However, 0 out of 10 3.2
> feature tickets have been completed till now, and it’s very unlikely for us
> to catch up with planned feature freeze (May 25th) and release deadline
> (June 1st) [2].
>
> I hereby suggest postponing release schedule by 2 weeks, extending feature
> freeze day to June 8th and release day to June 15th. Considering its wide
> affect, please leave your comments & concerns about this suggestion.
>
> Regards,
> Xiqian
>
> [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=607
> [2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=303794651
>
>
> De : Peter Huang 
> Date : jeudi, 9 mai 2024 à 23:31
> À : dev@flink.apache.org 
> Objet : Re: [DISCUSS] Flink CDC 3.2 Release Planning
> Thanks Qingsheng for driving the release!
>
> +1. I also would like to provide some help on CDC 3.2.
>
>
> Best Regards
> Peter Huang
>
> On Thu, May 9, 2024 at 3:21 AM Xiqian YU  wrote:
>
> > Thanks Qingsheng for driving the release!
> >
> > +1. Would love to provide my help on CDC 3.2.
> >
> > Regards,
> > Xiqian
> >
> > De : Hang Ruan 
> > Date : jeudi, 9 mai 2024 à 17:50
> > À : dev@flink.apache.org 
> > Objet : Re: [DISCUSS] Flink CDC 3.2 Release Planning
> > Thanks Qinsheng for driving.
> >
> > I would like to provide some helps for this verison too. +1.
> >
> > Best,
> > Hang
> >
> > Hongshun Wang  于2024年5月9日周四 14:16写道：
> >
> > > Thanks Qinsheng for driving,
> > > +1 from my side.
> > >
> > > Besi,
> > > Hongshun
> > >
> > > On Wed, May 8, 2024 at 11:41 PM Leonard Xu  wrote:
> > >
> > > > +1 for the proposal code freeze date and RM candidate.
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > > > 2024年5月8日 下午10:27，gongzhongqiang  写道：
> > > > >
> > > > > Hi Qingsheng
> > > > >
> > > > > Thank you for driving the release.
> > > > > Agree with the goal and I'm willing to help.
> > > > >
> > > > > Best,
> > > > > Zhongqiang Gong
> > > > >
> > > > > Qingsheng Ren  于2024年5月8日周三 14:22写道：
> > > > >
> > > > >> Hi devs,
> > > > >>
> > > > >> As we are in the midst of the release voting process for Flink CDC
> > > > 3.1.0, I
> > > > >> think it's a good time to kick off the upcoming Flink CDC 3.2
> > release
> > > > >> cycle.
> > > > >>
> > > > >> In this release cycle I would like to focus on the stability of
> > Flink
> > > > CDC,
> > > > >> especially for the newly introduced YAML-based data integration
> > > > >> framework. To ensure we can iterate and improve swiftly, I propose
> > to
> > > > make
> > > > >> 3.2 a relatively short release cycle, targeting a feature freeze
> by
> > > May
> > > > 24,
> > > > >> 2024.
> > > > >>
> > > > >> For developers that are interested in participating and
> contributing
> > > new
> > > > >> features in this release cycle, please feel free to list your
> > planning
> > > > >> features in the wiki page [1].
> > > > >>
> > > > >> I'm happy to volunteer as a release manager and of course open to
> > work
> > > > >> together with someone on this.
> > > > >>
> > > > >> What do you think?
> > > > >>
> > > > >> Best,
> > > > >> Qingsheng
> > > > >>
> > > > >> [1]
> > > > >>
> > >
> https://cwiki.apache.org/confluence/display/FLINK/Flink+CDC+3.2+Release
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release flink-connector-opensearch v1.2.0, release candidate #1

2024-05-27 Thread Hang Ruan 
+1 (non-binding)

- verified signatures
- verified hashsums
- built from source code with JDK 1.8 succeeded
- checked release notes
- reviewed the web PR
- check the jar is built with JDK 1.8

Best,
Hang

Leonard Xu  于2024年5月22日周三 21:07写道：

> +1 (binding)
>
> - verified signatures
> - verified hashsums
> - built from source code with JDK 1.8 succeeded
> - checked Github release tag
> - checked release notes
> - reviewed the web PR
>
> Best,
> Leonard
>
> > 2024年5月16日 上午6:58，Andrey Redko  写道：
> >
> > +1 (non-binding), thanks Sergey!
> >
> > On Wed, May 15, 2024, 5:56 p.m. Sergey Nuyanzin 
> wrote:
> >
> >> Hi everyone,
> >> Please review and vote on release candidate #1 for
> >> flink-connector-opensearch v1.2.0, as follows:
> >> [ ] +1, Approve the release
> >> [ ] -1, Do not approve the release (please provide specific comments)
> >>
> >>
> >> The complete staging area is available for your review, which includes:
> >> * JIRA release notes [1],
> >> * the official Apache source release to be deployed to dist.apache.org
> >> [2],
> >> which are signed with the key with fingerprint
> >> F7529FAE24811A5C0DF3CA741596BBF0726835D8 [3],
> >> * all artifacts to be deployed to the Maven Central Repository [4],
> >> * source code tag v1.2.0-rc1 [5],
> >> * website pull request listing the new release [6].
> >> * CI build of the tag [7].
> >>
> >> The vote will be open for at least 72 hours. It is adopted by majority
> >> approval, with at least 3 PMC affirmative votes.
> >>
> >> Note that this release is for Opensearch v1.x
> >>
> >> Thanks,
> >> Release Manager
> >>
> >> [1] https://issues.apache.org/jira/projects/FLINK/versions/12353812
> >> [2]
> >>
> >>
> https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-1.2.0-rc1
> >> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >> [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1734
> >> [5]
> >>
> >>
> https://github.com/apache/flink-connector-opensearch/releases/tag/v1.2.0-rc1
> >> [6] https://github.com/apache/flink-web/pull/740
> >> [7]
> >>
> >>
> https://github.com/apache/flink-connector-opensearch/actions/runs/9102334125
> >>
>
>

Re: [VOTE] FLIP-443: Interruptible watermark processing

2024-05-27 Thread Stefan Richter 

+1 (binding)



> On 24. May 2024, at 09:59, Martijn Visser  wrote:
> 
> +1 (binding)
> 
> On Fri, May 24, 2024 at 7:31 AM weijie guo  >
> wrote:
> 
>> +1(binding)
>> 
>> Thanks for driving this!
>> 
>> Best regards,
>> 
>> Weijie
>> 
>> 
>> Rui Fan <1996fan...@gmail.com> 于2024年5月24日周五 13:03写道：
>> 
>>> +1(binding)
>>> 
>>> Best,
>>> Rui
>>> 
>>> On Fri, May 24, 2024 at 12:01 PM Yanfei Lei  wrote:
>>> 
 Thanks for driving this!
 
 +1 (binding)
 
 Best,
 Yanfei
 
 Zakelly Lan  于2024年5月24日周五 10:13写道：
 
> 
> +1 (binding)
> 
> Best,
> Zakelly
> 
> On Thu, May 23, 2024 at 8:21 PM Piotr Nowojski >> 
 wrote:
> 
>> Hi all,
>> 
>> After reaching what looks like a consensus in the discussion thread
 [1], I
>> would like to put FLIP-443 [2] to the vote.
>> 
>> The vote will be open for at least 72 hours unless there is an
 objection or
>> insufficient votes.
>> 
>> [1]
>> https://www.google.com/url?q=https://lists.apache.org/thread/flxm7rphvfgqdn2gq2z0bb7kl007olpz=gmail-imap=171714246900=AOvVaw1sxqcTTJfXbE_qaBA0l1FH
>> [2] 
>> https://www.google.com/url?q=https://cwiki.apache.org/confluence/x/qgn9EQ=gmail-imap=171714246900=AOvVaw3yQ55VLWPxkY2OHXf0k72Q
>> 
>> Bets,
>> Piotrek

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

2024-05-27 Thread Hang Ruan 
+1 (non-binding)

- verified signatures
- verified hashsums
- built from source code with JDK 11 succeed
- checked release notes
- reviewed the web PR

Best,
Hang

Leonard Xu  于2024年5月22日周三 21:02写道：

>
> > +1 (binding)
> >
> > - verified signatures
> > - verified hashsums
> > - built from source code with JDK 1.8 succeeded
> > - checked Github release tag
> > - checked release notes
> > - reviewed the web PR
>
> Supply more information about build from source code with JDK 1.8
>
> > - built from source code with JDK 1.8 succeeded
> It’s correct as we don’t activate opensearch2 profile by default.
>
> - built from source code with JDK 1.8 and -Popensearch2 failed
> - built from source code with JDK 11 and -Popensearch2 succeeded
>
> Best,
> Leonard
>
>
> >
> >
> >> 2024年5月16日 上午6:58，Andrey Redko  写道：
> >>
> >> +1 (non-binding), thanks Sergey!
> >>
> >> On Wed, May 15, 2024, 6:00 p.m. Sergey Nuyanzin 
> wrote:
> >>
> >>> Hi everyone,
> >>> Please review and vote on release candidate #1 for
> >>> flink-connector-opensearch v2.0.0, as follows:
> >>> [ ] +1, Approve the release
> >>> [ ] -1, Do not approve the release (please provide specific comments)
> >>>
> >>>
> >>> The complete staging area is available for your review, which includes:
> >>> * JIRA release notes [1],
> >>> * the official Apache source release to be deployed to dist.apache.org
> >>> [2],
> >>> which are signed with the key with fingerprint
> >>> F7529FAE24811A5C0DF3CA741596BBF0726835D8 [3],
> >>> * all artifacts to be deployed to the Maven Central Repository [4],
> >>> * source code tag v2.0.0-rc1 [5],
> >>> * website pull request listing the new release [6].
> >>> * CI build of the tag [7].
> >>>
> >>> The vote will be open for at least 72 hours. It is adopted by majority
> >>> approval, with at least 3 PMC affirmative votes.
> >>>
> >>> Note that this release is for Opensearch v2.x
> >>>
> >>> Thanks,
> >>> Release Manager
> >>>
> >>> [1] https://issues.apache.org/jira/projects/FLINK/versions/12354674
> >>> [2]
> >>>
> >>>
> https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-2.0.0-rc1
> >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >>> [4]
> >>>
> https://repository.apache.org/content/repositories/orgapacheflink-1735/
> >>> [5]
> >>>
> >>>
> https://github.com/apache/flink-connector-opensearch/releases/tag/v2.0.0-rc1
> >>> [6] https://github.com/apache/flink-web/pull/741
> >>> [7]
> >>>
> >>>
> https://github.com/apache/flink-connector-opensearch/actions/runs/9102980808
> >>>
> >
>
>

Re: [DISCUSS] The performance of serializerHeavyString starts regress since April 3

2024-05-27 Thread Rui Fan 
Thanks Sam for the comment!

> It looks like the most recent run of JDK 11 saw a big improvement of the
> performance of the test.

I guess that improvement is a fluctuation. You can double check the
performance results[1] of the last few days. The performance isn't
recovered.

> That improvement seems related to which is a fix for FLINK-35215.

I fixed an issue related to kryo serialization in FLINK-35215. IIUC,
serializerHeavyString doesn't use the kryo serialization. I try to
run serializerHeavyString demo locally, and didn't see the
kryo serialization related code is called.

Please correct me if I'm wrong, thanks~

[1]
http://flink-speed.xyz/timeline/#/?exe=6=serializerHeavyString=on=on=off=3=200

Best,
Rui

On Thu, May 23, 2024 at 1:27 PM Sam Barker  wrote:

> It looks like the most recent run of JDK 11 saw a big improvement[1] of the
> performance of the test. That improvement seems related to [2] which is a
> fix for FLINK-35215 [3]. That suggests to me that the test isn't as
> isolated to the performance of the code its trying to test as would be
> ideal. However I've only just started looking at the test suite and trying
> to run locally so I'm not very well placed to judge.
>
> It does however suggest that this shouldn't be a blocker for the release.
>
>
>
> [1] http://flink-speed.xyz/changes/?rev=c1baf07d76=6=3
> [2]
>
> https://github.com/apache/flink/commit/c1baf07d7601a683f42997dc35dfaef4e41bc928
> [3] https://issues.apache.org/jira/browse/FLINK-35215
>
> On Wed, 22 May 2024 at 00:15, Piotr Nowojski  wrote:
>
> > Hi,
> >
> > Given what you wrote, that you have investigated the issue and couldn't
> > find any easy explanation, I would suggest closing this ticket as "Won't
> > do" or "Can not reproduce" and ignoring the problem.
> >
> > In the past there have been quite a bit of cases where some benchmark
> > detected a performance regression. Sometimes those can not be reproduced,
> > other times (as it's the case here), some seemingly unrelated change is
> > causing the regression. The same thing happened in this benchmark many
> > times in the past [1], [2], [3], [4]. Generally speaking this benchmark
> has
> > been in the spotlight a couple of times [5].
> >
> > Note that there have been cases where this benchmark did detect a
> > performance regression :)
> >
> > My personal suspicion is that after that commons-io version bump,
> > something poked JVM/JIT to compile the code a bit differently for string
> > serialization causing this regression. We have a couple of benchmarks
> that
> > seem to be prone to such semi intermittent issues. For example the same
> > benchmark was subject to this annoying pattern [6], that I've spotted in
> > quite a bit of benchmarks over the years [6]:
> >
> > [image: image.png]
> > (https://imgur.com/a/AoygmWS)
> >
> > Where benchmark results are very stable within a single JVM fork. But
> > between two forks, they can reach two different "stable" levels. Here it
> > looks like 50% of the chance of getting stable "200 records/ms" and 50%
> > chances of "250 records/ms".
> >
> > A small interlude. Each of our benchmarks run in 3 different JVM forks,
> 10
> > warm up iterations and 10 measurement iterations. Each iteration
> > lasts/invokes the benchmarking method at least for one second. So by
> "very
> > stable" results, I mean that for example after the 2nd or 3rd warm up
> > iteration, the results stabilize < +/-1%, and stay on that level for the
> > whole duration of the fork.
> >
> > Given that we are repeating the same benchmark in 3 different forks, we
> > can have by pure chance:
> > - 3 slow fork - total average 200 records/ms
> > - 2 slow fork, 1 fast fork - average 216 r/ms
> > - 1 slow fork, 2 fast forks - average 233 r/ms
> > - 3 fast forks - average 250 r/ms
> >
> > So this benchmark is susceptible to enter some different semi stable
> > states. As I wrote above, I guess something with the commons-io version
> > bump just swayed it to a different semi stable state :( I have never
> gotten
> > desperate enough to actually dig further what's exactly causing this kind
> > of issues.
> >
> > Best,
> > Piotrek
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-18684
> > [2] https://issues.apache.org/jira/browse/FLINK-27133
> > [3] https://issues.apache.org/jira/browse/FLINK-27165
> > [4] https://issues.apache.org/jira/browse/FLINK-31745
> > [5]
> >
> https://issues.apache.org/jira/browse/FLINK-35040?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Resolved%2C%20Closed)%20AND%20text%20~%20%22serializerHeavyString%22
> > [6]
> >
> http://flink-speed.xyz/timeline/#/?exe=1=serializerHeavyString=on=on=off=2=1000
> >
> > wt., 21 maj 2024 o 12:50 Rui Fan <1996fan...@gmail.com> napisał(a):
> >
> >> Hi devs:
> >>
> >> We(release managers of flink 1.20) wanna update one performance
> >> regresses to the flink dev mail list.
> >>
> >> # Background:
> >>
> >> The performance of serializerHeavyString starts

[jira] [Created] (FLINK-35463) CDC job failed when restored from checkpoint when route rule changed.

2024-05-27 Thread hk__lrzy (Jira) 
hk__lrzy created FLINK-35463:


 Summary: CDC job failed when restored from checkpoint when route 
rule changed.
 Key: FLINK-35463
 URL: https://issues.apache.org/jira/browse/FLINK-35463
 Project: Flink
  Issue Type: Improvement
  Components: Flink CDC
Reporter: hk__lrzy


*Exception:* 

 
{code:java}
java.lang.IllegalStateException: Unable to get latest schema for table 
"demo.partition_all" {code}
*Reason:* 

Now *ScheamRegister* will stored the all original tables which from source and 
all derivered table which from route rules.

Assume we have a table in mysql which named *demo.partition_all* and have route 
rule *demo1.partition_all* for it.

1. Before first checkpoint be triggered,  *ScheamRegister* will store both 
*demo.partition_all* and {*}demo1.partition_all{*}'s schema in the 
{*}SchemaManager{*}.

2. Stop the job, change route rule as {*}demo1.partition_all_1{*}, and restart 
it with checkpoint.

3. According the logical follow:
{code:java}
if (request.getSchemaChangeEvent() instanceof CreateTableEvent
&& schemaManager.schemaExists(request.getTableId())) {
  return CompletableFuture.completedFuture(
  wrap(new SchemaChangeResponse(Collections.emptyList(;
} {code}
We will not create a schema for the table *demo1.partition_all_1* and job will 
be failed when we request schema from {*}SchemaOperator{*}.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-35462) Introduce a parameter to control the chaining mode between a Flink SQL connector sink or source and its adjacent operator.

2024-05-27 Thread yuanfenghu (Jira) 
yuanfenghu created FLINK-35462:
--

 Summary: Introduce a parameter to control the chaining mode 
between a Flink SQL connector sink or source and its adjacent operator.
 Key: FLINK-35462
 URL: https://issues.apache.org/jira/browse/FLINK-35462
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Reporter: yuanfenghu


When using the flinksql connector, we can set the parallelism of the sink. 
However, when we modify the parallelism of the sink to be the same as the 
global one, the global chaining strategy may cause the two operators to be 
linked together, which will make the task unable to proceed. For checkpoint or 
savepoint recovery, we should allow explicit specification of the chaining mode 
of the connector.
 
Related issues:

 https://github.com/apache/iceberg/issues/10371



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

2024-05-27 Thread Jark Wu 
+1 (binding)

Best,
Jark

On Mon, 27 May 2024 at 14:29, Hang Ruan  wrote:

> +1 (non-binding)
>
> Best,
> Hang
>
> gongzhongqiang  于2024年5月27日周一 14:16写道：
>
> > +1 (non-binding)
> >
> > Best,
> > Zhongqiang Gong
> >
> > Jane Chan  于2024年5月24日周五 09:52写道：
> >
> > > Hi all,
> > >
> > > I'd like to start a vote on FLIP-457[1] after reaching a consensus
> > through
> > > the discussion thread[2].
> > >
> > > The vote will be open for at least 72 hours unless there is an
> objection
> > or
> > > insufficient votes.
> > >
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=307136992
> > > [2] https://lists.apache.org/thread/1sthbv6q00sq52pp04n2p26d70w4fqj1
> > >
> > > Best,
> > > Jane
> > >
> >
>

Re: [DISCUSS] Proposing an LTS Release for the 1.x Line

2024-05-27 Thread Matthias Pohl 
Hi Alex,
thanks for creating the FLIP. One question: Is it intentionally done that
the FLIP only covers the 1.x LTS version? Why don't we make the FLIP
generic to also apply to other major version upgrades?

Best,
Matthias

On Sat, May 25, 2024 at 4:55 PM Xintong Song  wrote:

> >
> > I think our starting point should be "We don't backport features, unless
> > discussed and agreed on the Dev mailing list".
>
>
> This makes perfect sense. In general, I think we want to encourage users to
> upgrade in order to use the new features. Alternatively, users can also
> choose to maintain their own custom patches based on the LTS version. I
> personally don't see why backporting new features to old releases is
> necessary. In case of exceptions, a mailing list discussion is always a
> good direction to go.
>
>
> Best,
>
> Xintong
>
>
>
> On Fri, May 24, 2024 at 9:35 PM David Radley 
> wrote:
>
> > Hi Martjin and Alex,
> > I agree with your summaries, it will be interesting to see what requests
> > there might be for back ports.
> >  Kind regards, David.
> >
> >
> >
> >
> > From: Alexander Fedulov 
> > Date: Friday, 24 May 2024 at 14:07
> > To: dev@flink.apache.org 
> > Subject: [EXTERNAL] Re: [DISCUSS] Proposing an LTS Release for the 1.x
> Line
> > @David
> > > I agree with Martijn that we only put features into version 2. Back
> > porting to v1 should not be business as usual for features, only for
> > security and stability changes.
> > Yep, this choice is explicitly reflected in the FLIP [1]
> >
> > @Martijn
> > >  I think our starting point should be "We don't backport features,
> unless
> > discussed and agreed on the Dev mailing list".
> > I agree - the baseline is that we do not do that. Only if a very
> compelling
> > argument is made and the community reaches consensus, exceptions could
> > potentially be made, but we should try to avoid them.
> >
> > [1] https://cwiki.apache.org/confluence/x/BApeEg
> >
> > Best,
> > Alex
> >
> > On Fri, 24 May 2024 at 14:38, Martijn Visser 
> > wrote:
> >
> > > Hi David,
> > >
> > > > If there is a maintainer willing to merge backported features to v1,
> as
> > > it is important to some part of the community, this should be allowed,
> as
> > > different parts of the community have different priorities and
> timelines,
> > >
> > > I don't think this is a good idea. Backporting a feature can cause
> issues
> > > in other components that might be outside the span of expertise of the
> > > maintainer that backported said feature, causing the overall stability
> to
> > > be degraded. I think our starting point should be "We don't backport
> > > features, unless discussed and agreed on the Dev mailing list". That
> > still
> > > opens up the ability to backport features but makes it clear where the
> > bar
> > > lies.
> > >
> > > Best regards,
> > >
> > > Martijn
> > >
> > > On Fri, May 24, 2024 at 11:21 AM David Radley  >
> > > wrote:
> > >
> > > > Hi,
> > > > I agree with Martijn that we only put features into version 2. Back
> > > > porting to v1 should not be business as usual for features, only for
> > > > security and stability changes.
> > > >
> > > > If there is a maintainer willing to merge backported features to v1,
> as
> > > it
> > > > is important to some part of the community, this should be allowed,
> as
> > > > different parts of the community have different priorities and
> > timelines,
> > > >  Kind regards, David.
> > > >
> > > >
> > > > From: Alexander Fedulov 
> > > > Date: Thursday, 23 May 2024 at 18:50
> > > > To: dev@flink.apache.org 
> > > > Subject: [EXTERNAL] Re: [DISCUSS] Proposing an LTS Release for the
> 1.x
> > > Line
> > > > Good point, Xintong, I incorporated this item into the FLIP.
> > > >
> > > > Best,
> > > > Alex
> > > >
> > > > On Wed, 22 May 2024 at 10:37, Xintong Song 
> > > wrote:
> > > >
> > > > > Thanks, Alex.
> > > > >
> > > > > I see one task that needs to be done once the FLIP is approved,
> which
> > > I'd
> > > > > suggest to also mention in the: To explain the LTS policy to users
> on
> > > > > website / documentation (because FLIP is developer-facing) before /
> > > upon
> > > > > releasing 1.20.
> > > > >
> > > > > Other than that, the FLIP LGTM.
> > > > >
> > > > > Best,
> > > > >
> > > > > Xintong
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 21, 2024 at 5:21 PM Alexander Fedulov <
> > > > > alexander.fedu...@gmail.com> wrote:
> > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > let's finalize this discussion. As Martijn suggested, I
> summarized
> > > this
> > > > > > thread into a FLIP [1]. Please take a look and let me know if
> > there’s
> > > > > > anything important that I might have missed.
> > > > > >
> > > > > > Best,
> > > > > > Alex
> > > > > >
> > > > > > [1] https://cwiki.apache.org/confluence/x/BApeEg
> > > > > >
> > > > > >
> > > > > > On Tue, 23 Jan 2024 at 03:30, Rui Fan <1996fan...@gmail.com>
> > wrote:
> > > > > >
> > > > > > > Thanks Martijn for the feedback!
> > > > > > >
> > >

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

2024-05-27 Thread Hang Ruan 
+1 (non-binding)

Best,
Hang

gongzhongqiang  于2024年5月27日周一 14:16写道：

> +1 (non-binding)
>
> Best,
> Zhongqiang Gong
>
> Jane Chan  于2024年5月24日周五 09:52写道：
>
> > Hi all,
> >
> > I'd like to start a vote on FLIP-457[1] after reaching a consensus
> through
> > the discussion thread[2].
> >
> > The vote will be open for at least 72 hours unless there is an objection
> or
> > insufficient votes.
> >
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=307136992
> > [2] https://lists.apache.org/thread/1sthbv6q00sq52pp04n2p26d70w4fqj1
> >
> > Best,
> > Jane
> >
>

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

2024-05-27 Thread gongzhongqiang 
+1 (non-binding)

Best,
Zhongqiang Gong

Jane Chan  于2024年5月24日周五 09:52写道：

> Hi all,
>
> I'd like to start a vote on FLIP-457[1] after reaching a consensus through
> the discussion thread[2].
>
> The vote will be open for at least 72 hours unless there is an objection or
> insufficient votes.
>
>
> [1]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=307136992
> [2] https://lists.apache.org/thread/1sthbv6q00sq52pp04n2p26d70w4fqj1
>
> Best,
> Jane
>

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

2024-05-27 Thread Feng Jin 
+1 (non-binding)

Best,
Feng Jin

On Mon, May 27, 2024 at 1:05 PM Benchao Li  wrote:

> +1 (binding)
>
> Yubin Li  于2024年5月25日周六 12:26写道：
> >
> > +1 (non-binding)
> >
> > Best,
> > Yubin
> >
> > On Fri, May 24, 2024 at 2:04 PM Rui Fan <1996fan...@gmail.com> wrote:
> > >
> > > +1(binding)
> > >
> > > Best,
> > > Rui
> > >
> > > On Fri, May 24, 2024 at 1:45 PM Leonard Xu  wrote:
> > >
> > > > +1
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > > > 2024年5月24日 下午1:27，weijie guo  写道：
> > > > >
> > > > > +1(binding)
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Weijie
> > > > >
> > > > >
> > > > > Lincoln Lee  于2024年5月24日周五 12:20写道：
> > > > >
> > > > >> +1(binding)
> > > > >>
> > > > >> Best,
> > > > >> Lincoln Lee
> > > > >>
> > > > >>
> > > > >> Jane Chan  于2024年5月24日周五 09:52写道：
> > > > >>
> > > > >>> Hi all,
> > > > >>>
> > > > >>> I'd like to start a vote on FLIP-457[1] after reaching a
> consensus
> > > > >> through
> > > > >>> the discussion thread[2].
> > > > >>>
> > > > >>> The vote will be open for at least 72 hours unless there is an
> > > > objection
> > > > >> or
> > > > >>> insufficient votes.
> > > > >>>
> > > > >>>
> > > > >>> [1]
> > > > >>>
> > > > >>
> > > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=307136992
> > > > >>> [2]
> https://lists.apache.org/thread/1sthbv6q00sq52pp04n2p26d70w4fqj1
> > > > >>>
> > > > >>> Best,
> > > > >>> Jane
> > > > >>>
> > > > >>
> > > >
> > > >
>
>
>
> --
>
> Best,
> Benchao Li
>