[RESULT][VOTE] FLIP-452: Allow Skipping Invocation of Function Calls While Constant-folding

2024-05-17 Thread Alan Sheinberg
The vote for FLIP-452: Allow Skipping Invocation of Function Calls While
Constant-folding [1] has concluded (discussion thread [2]). The vote will
be closed [3].

There were 4 approving votes, all binding, and there were no disapprovals:

- Stefan Richter (binding)
- Timo Walther (binding)
- Benchao Li (binding)
- Lincoln Lee (binding)

Therefore, FLIP-452 was accepted. Thanks for the feedback!

-Alan

[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-452%3A+Allow+Skipping+Invocation+of+Function+Calls+While+Constant-folding

[2] https://lists.apache.org/thread/ko5ndv5kr87nm011psll2hzzd0nn3ztz
[3] https://lists.apache.org/thread/2jdyj5bnj12n385td2lcdtj4fdlogp6j


Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread Muhammet Orazov

Amazing, congrats!

Thanks for your efforts!

Best,
Muhammet

On 2024-05-17 09:32, Qingsheng Ren wrote:

The Apache Flink community is very happy to announce the release of
Apache Flink CDC 3.1.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
in a data pipeline.

Please check out the release blog post for an overview of the release:
https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/

The release is available for download at:
https://flink.apache.org/downloads.html

Maven artifacts for Flink CDC can be found at:
https://search.maven.org/search?q=g:org.apache.flink%20cdc

The full release notes are available in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387

We would like to thank all contributors of the Apache Flink community
who made this release possible!

Regards,
Qingsheng Ren


Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread gongzhongqiang
Congratulations !
Thanks for all contributors.


Best,

Zhongqiang Gong

Qingsheng Ren  于 2024年5月17日周五 17:33写道:

> The Apache Flink community is very happy to announce the release of
> Apache Flink CDC 3.1.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
> in a data pipeline.
>
> Please check out the release blog post for an overview of the release:
>
> https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/
>
> The release is available for download at:
> https://flink.apache.org/downloads.html
>
> Maven artifacts for Flink CDC can be found at:
> https://search.maven.org/search?q=g:org.apache.flink%20cdc
>
> The full release notes are available in Jira:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387
>
> We would like to thank all contributors of the Apache Flink community
> who made this release possible!
>
> Regards,
> Qingsheng Ren
>


[RESULT][VOTE] FLIP-453: Promote Unified Sink API V2 to Public and Deprecate SinkFunction

2024-05-17 Thread Martijn Visser
Hi all,

I'm happy to announce that we have unanimously approved FLIP-453.
There were 12 votes, of which 4 were binding.

- weijie guo (binding)
- Ferenc Csaky (non-binding)
- Rui Fan (binding)
- Zhongqiang Gong (non-binding)
- Péter Váry (non-binding)
- Rodrigo Meneses (non-binding)
- lorenzo affetti (non-binding)
- Jing Ge (binding)
- Ahmed Hamdy (non-binding)
- Yuepeng Pan (non-binding)
- Hang Ruan (non-binding)
- Leonard Xu (binding)

Best regards,

Martijn


Re: [VOTE] FLIP-453: Promote Unified Sink API V2 to Public and Deprecate SinkFunction

2024-05-17 Thread Martijn Visser
Hi all,

Thanks for all your votes, I hereby close the vote and I'll announce the
results in a separate email.

Best regards,

Martijn

On Fri, May 17, 2024 at 11:48 AM Leonard Xu  wrote:

> +1(binding)
>
> Best,
> Leonard
>
> > 2024年5月17日 下午5:40,Hang Ruan  写道:
> >
> > +1(non-binding)
> >
> > Best,
> > Hang
> >
> > Yuepeng Pan  于2024年5月17日周五 16:15写道:
> >
> >> +1(non-binding)
> >>
> >>
> >> Best,
> >> Yuepeng Pan
> >>
> >>
> >> At 2024-05-15 21:09:04, "Jing Ge"  wrote:
> >>> +1(binding) Thanks Martijn!
> >>>
> >>> Best regards,
> >>> Jing
> >>>
> >>> On Wed, May 15, 2024 at 7:00 PM Muhammet Orazov
> >>>  wrote:
> >>>
>  Thanks Martijn driving this! +1 (non-binding)
> 
>  Best,
>  Muhammet
> 
>  On 2024-05-14 06:43, Martijn Visser wrote:
> > Hi everyone,
> >
> > With no more discussions being open in the thread [1] I would like to
> > start
> > a vote on FLIP-453: Promote Unified Sink API V2 to Public and
> >> Deprecate
> > SinkFunction [2]
> >
> > The vote will be open for at least 72 hours unless there is an
> > objection or
> > insufficient votes.
> >
> > Best regards,
> >
> > Martijn
> >
> > [1] https://lists.apache.org/thread/hod6bg421bzwhbfv60lwsck7r81dvo59
> > [2]
> >
> 
> >>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-453%3A+Promote+Unified+Sink+API+V2+to+Public+and+Deprecate+SinkFunction
> 
> >>
>
>


[jira] [Created] (FLINK-35392) SQL Lookup Join on external database failing when using 'FOR SYSTEM_TIME AS OF' statement

2024-05-17 Thread Glauber M Dantas (Jira)
Glauber M Dantas created FLINK-35392:


 Summary: SQL Lookup Join on external database failing when using 
'FOR SYSTEM_TIME AS OF' statement
 Key: FLINK-35392
 URL: https://issues.apache.org/jira/browse/FLINK-35392
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Planner
Affects Versions: 1.18.1
Reporter: Glauber M Dantas


When transforming a DataStream to a Table and then using that table in a Join 
Lookup, an exception is raised: {{{}"Temporal table join currently only 
supports 'FOR SYSTEM_TIME AS OF' left table's time attribute field"{}}}.

>From what I understood from the issue, it happens as the planner expects that 
>the Tables part of the Join are registered previously on the Catalog.

The solution was to avoid using the DataStream to Table conversion:

```
Table kinesisStreamTbl = tblEnv.fromDataStream(
                kinesisDataStream,
                Schema.newBuilder()
                        // "proc_time" would be needed to make the lookup using 
'FOR SYSTEM_TIME AS OF'; see: 
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/joins/#processing-time-temporal-join
                        .columnByExpression("proc_time", "PROCTIME()")
                        .build()
        );
```
And instead create and use a Table registered on the Catalog:

```

tblEnv.createTable("KinesisInput", TableDescriptor.forConnector("kinesis")...);

```

If you need more details, you may access the discussion at: 
https://stackoverflow.com/questions/78485099/sedona-flink-sql-lookup-on-external-database-failing-when-using-for-system-time



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


Re: [DISCUSS] FLIP-444: Native file copy support

2024-05-17 Thread lorenzo . affetti
Perfectly agree with all your considerations.
Wee said.

Thank you!
On May 16, 2024 at 10:53 +0200, Piotr Nowojski , wrote:
> Hi Lorenzo,
>
> > • concerns about memory and CPU used out of Flink's control
>
> Please note that using AWS SDKv2 would have the same concerns. In both
> cases Flink can control only to a certain extent what either the SDKv2
> library does under the hood or the s5cmd process, via configuration
> parameters. SDKv2, if configured improperly, could also overload TMs CPU,
> and it would also use extra memory. To an extent that also applies to the
> current way we are downloading/uploading files from the S3.
>
> > • deployment concerns from the usability perspective (would need to
> install s5cmd on all TMs prior to the job deploy)
>
> Yes, that's the downside.
>
> > Also, invoking an external binary would incur in some performance
> degradation possibly. Might it be that using AWS SDK would not, given its
> Java implementation, and performance could be similar?
>
> We haven't run the benchmarks for very fast checkpointing and we haven't
> measured latency impact, but please note `s5cmd` is very fast to startup.
> It's not Java after all ;) It's at least an order of magnitude below 1s, so
> the impact on Flink should be negligible, as Flink doesn't support
> checkpointing under < 1s. Especially not with uploading files to S3. I
> wouldn't be actually surprised that `s5cmd` (or AWS
> SDKv2's `TransferManager`) would actually both improve minimal e2e
> checkpointing times.
>
> > Wrapping up, I see using AWS SDK having PROs that could be traded with
> the CON of slightly worse perf than s5cmd:
> >
> > • no hurdles for the user, as the SDK would be a Flink dependency
> > • less config on the Flink side
> >
> > Do you agree?
>
> To an extent, yes. AWS SDKv2's TransferManager would also have to be
> configured properly. But I agree that the largest hurdle with `s5cmd` is
> the added operational complexity of having to supply 3rd party binary.
>
> Please also keep in mind that a lot of work for that FLIP will be in
> defining, creating and using the interfaces for batch files copy. The
> actual implementation of the fast copying file system interface and using
> `s5cmd` is not the dominant factor. So all in all, I wouldn't object if
> someone would like to take over my AWS SDKv2 PoC, and finish it off in the
> future, as an alternative for the `s5cmd`. Indeed AWS SDKv2 could at some
> point become the default setting, while `s5cmd` could remain as a faster
> alternative.
>
> Best,
> Piotrek
>
> czw., 16 maj 2024 o 09:03 
> napisał(a):
>
> > Hello Piotr and thanks for this proposal!
> > The idea sounds smart and very well grounded thank you!
> >
> > Also here, as others, I have some doubts about invoking an external binary
> > (namely s5cmd):
> >
> > • concerns about memory and CPU used out of Flink's control
> > • deployment concerns from the usability perspective (would need to
> > install s5cmd on all TMs prior to the job deploy)
> >
> >
> > Also, invoking an external binary would incur in some performance
> > degradation possibly. Might it be that using AWS SDK would not, given its
> > Java implementation, and performance could be similar?
> >
> > Wrapping up, I see using AWS SDK having PROs that could be traded with the
> > CON of slightly worse perf than s5cmd:
> >
> > • no hurdles for the user, as the SDK would be a Flink dependency
> > • less config on the Flink side
> >
> >
> > Do you agree?
> > On May 13, 2024 at 07:42 +0200, Hangxiang Yu , wrote:
> > > > > >
> > > > > > Note that for both recovery and checkpoints, there are no retring
> > > > > > mechanisms. If any part of downloading or
> > > > > > uploading fails, the job fails over, so actually using such 
> > > > > > interface
> > > > > > extension would be out of scope of this FLIP. In
> > > > > > that case, maybe if this could be extended in the future without
> > breaking
> > > > > > compatibility we could leave it as a
> > > > > > future improvement?
> > > > > >
> > > >
> > > > Thanks for the reply.
> > > > It makes sense to consider as a future optimization.
> > > >
> > > > On Fri, May 10, 2024 at 4:31 PM Piotr Nowojski  > > >
> > > > wrote:
> > > >
> > > > > > Hi!
> > > > > >
> > > > > > Thanks for your suggestions!
> > > > > >
> > > > > > > > > > I'd prefer a unified one interface
> > > > > >
> > > > > > I have updated the FLIP to take that into account. In this case, I
> > would
> > > > > > also propose to completely drop `DuplicatingFileSystem` in favour 
> > > > > > of a
> > > > > > basically renamed version of it `PathsCopyingFileSystem`.
> > > > > > `DuplicatingFileSystem` was not marked as 
> > > > > > PublicEvolving/Experimental
> > > > > > (probably by mistake), so technically we can do it. Even if not for
> > that
> > > > > > mistake, I would still vote to replace it to simplify the code, as 
> > > > > > any
> > > > > > migration would be very easy. At the same time to the best of my
> > knowledge,
> > > > > > no 

[jira] [Created] (FLINK-35391) Bump dependency of Paimon Pipeline connector to 0.8.0

2024-05-17 Thread LvYanquan (Jira)
LvYanquan created FLINK-35391:
-

 Summary: Bump dependency of Paimon Pipeline connector to 0.8.0
 Key: FLINK-35391
 URL: https://issues.apache.org/jira/browse/FLINK-35391
 Project: Flink
  Issue Type: Improvement
  Components: Flink CDC
Affects Versions: cdc-3.2.0
Reporter: LvYanquan
 Fix For: cdc-3.2.0


Apache Paimon has released 0.8 recently, We can update dependencies to use new 
features. 



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


Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread Yanquan Lv
Congratulations!
Thanks for all selfless contributors.


Best,
Yanquan Lv

Ahmed Hamdy  于2024年5月17日周五 18:49写道:

> Congratulations,
> Great Work!
> Best Regards
> Ahmed Hamdy
>
>
> On Fri, 17 May 2024 at 10:56, ConradJam  wrote:
>
> > Congratulations!
> >
> > Thanks for the great work.
> >
> > Hang Ruan  于2024年5月17日周五 17:48写道:
> >
> > > Congratulations!
> > >
> > > Thanks for the great work.
> > >
> > > Best,
> > > Hang
> > >
> > > Qingsheng Ren  于2024年5月17日周五 17:33写道:
> > >
> > > > The Apache Flink community is very happy to announce the release of
> > > > Apache Flink CDC 3.1.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
> > > > in a data pipeline.
> > > >
> > > > Please check out the release blog post for an overview of the
> release:
> > > >
> > > >
> > >
> >
> https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/
> > > >
> > > > The release is available for download at:
> > > > https://flink.apache.org/downloads.html
> > > >
> > > > Maven artifacts for Flink CDC can be found at:
> > > > https://search.maven.org/search?q=g:org.apache.flink%20cdc
> > > >
> > > > The full release notes are available in Jira:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387
> > > >
> > > > We would like to thank all contributors of the Apache Flink community
> > > > who made this release possible!
> > > >
> > > > Regards,
> > > > Qingsheng Ren
> > > >
> > >
> >
> >
> > --
> > Best
> >
> > ConradJam
> >
>


Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread Ahmed Hamdy
Congratulations,
Great Work!
Best Regards
Ahmed Hamdy


On Fri, 17 May 2024 at 10:56, ConradJam  wrote:

> Congratulations!
>
> Thanks for the great work.
>
> Hang Ruan  于2024年5月17日周五 17:48写道:
>
> > Congratulations!
> >
> > Thanks for the great work.
> >
> > Best,
> > Hang
> >
> > Qingsheng Ren  于2024年5月17日周五 17:33写道:
> >
> > > The Apache Flink community is very happy to announce the release of
> > > Apache Flink CDC 3.1.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
> > > in a data pipeline.
> > >
> > > Please check out the release blog post for an overview of the release:
> > >
> > >
> >
> https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/
> > >
> > > The release is available for download at:
> > > https://flink.apache.org/downloads.html
> > >
> > > Maven artifacts for Flink CDC can be found at:
> > > https://search.maven.org/search?q=g:org.apache.flink%20cdc
> > >
> > > The full release notes are available in Jira:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387
> > >
> > > We would like to thank all contributors of the Apache Flink community
> > > who made this release possible!
> > >
> > > Regards,
> > > Qingsheng Ren
> > >
> >
>
>
> --
> Best
>
> ConradJam
>


Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread ConradJam
Congratulations!

Thanks for the great work.

Hang Ruan  于2024年5月17日周五 17:48写道:

> Congratulations!
>
> Thanks for the great work.
>
> Best,
> Hang
>
> Qingsheng Ren  于2024年5月17日周五 17:33写道:
>
> > The Apache Flink community is very happy to announce the release of
> > Apache Flink CDC 3.1.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
> > in a data pipeline.
> >
> > Please check out the release blog post for an overview of the release:
> >
> >
> https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/
> >
> > The release is available for download at:
> > https://flink.apache.org/downloads.html
> >
> > Maven artifacts for Flink CDC can be found at:
> > https://search.maven.org/search?q=g:org.apache.flink%20cdc
> >
> > The full release notes are available in Jira:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387
> >
> > We would like to thank all contributors of the Apache Flink community
> > who made this release possible!
> >
> > Regards,
> > Qingsheng Ren
> >
>


-- 
Best

ConradJam


Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread Hang Ruan
Congratulations!

Thanks for the great work.

Best,
Hang

Qingsheng Ren  于2024年5月17日周五 17:33写道:

> The Apache Flink community is very happy to announce the release of
> Apache Flink CDC 3.1.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
> in a data pipeline.
>
> Please check out the release blog post for an overview of the release:
>
> https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/
>
> The release is available for download at:
> https://flink.apache.org/downloads.html
>
> Maven artifacts for Flink CDC can be found at:
> https://search.maven.org/search?q=g:org.apache.flink%20cdc
>
> The full release notes are available in Jira:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387
>
> We would like to thank all contributors of the Apache Flink community
> who made this release possible!
>
> Regards,
> Qingsheng Ren
>


Re: [VOTE] FLIP-453: Promote Unified Sink API V2 to Public and Deprecate SinkFunction

2024-05-17 Thread Leonard Xu
+1(binding)

Best,
Leonard

> 2024年5月17日 下午5:40,Hang Ruan  写道:
> 
> +1(non-binding)
> 
> Best,
> Hang
> 
> Yuepeng Pan  于2024年5月17日周五 16:15写道:
> 
>> +1(non-binding)
>> 
>> 
>> Best,
>> Yuepeng Pan
>> 
>> 
>> At 2024-05-15 21:09:04, "Jing Ge"  wrote:
>>> +1(binding) Thanks Martijn!
>>> 
>>> Best regards,
>>> Jing
>>> 
>>> On Wed, May 15, 2024 at 7:00 PM Muhammet Orazov
>>>  wrote:
>>> 
 Thanks Martijn driving this! +1 (non-binding)
 
 Best,
 Muhammet
 
 On 2024-05-14 06:43, Martijn Visser wrote:
> Hi everyone,
> 
> With no more discussions being open in the thread [1] I would like to
> start
> a vote on FLIP-453: Promote Unified Sink API V2 to Public and
>> Deprecate
> SinkFunction [2]
> 
> The vote will be open for at least 72 hours unless there is an
> objection or
> insufficient votes.
> 
> Best regards,
> 
> Martijn
> 
> [1] https://lists.apache.org/thread/hod6bg421bzwhbfv60lwsck7r81dvo59
> [2]
> 
 
>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-453%3A+Promote+Unified+Sink+API+V2+to+Public+and+Deprecate+SinkFunction
 
>> 



Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread Leonard Xu
Congratulations !

Thanks Qingsheng for the great work and all contributors involved !!

Best,
Leonard


> 2024年5月17日 下午5:32,Qingsheng Ren  写道:
> 
> The Apache Flink community is very happy to announce the release of
> Apache Flink CDC 3.1.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
> in a data pipeline.
> 
> Please check out the release blog post for an overview of the release:
> https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/
> 
> The release is available for download at:
> https://flink.apache.org/downloads.html
> 
> Maven artifacts for Flink CDC can be found at:
> https://search.maven.org/search?q=g:org.apache.flink%20cdc
> 
> The full release notes are available in Jira:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387
> 
> We would like to thank all contributors of the Apache Flink community
> who made this release possible!
> 
> Regards,
> Qingsheng Ren



Re: [VOTE] FLIP-453: Promote Unified Sink API V2 to Public and Deprecate SinkFunction

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

Best,
Hang

Yuepeng Pan  于2024年5月17日周五 16:15写道:

> +1(non-binding)
>
>
> Best,
> Yuepeng Pan
>
>
> At 2024-05-15 21:09:04, "Jing Ge"  wrote:
> >+1(binding) Thanks Martijn!
> >
> >Best regards,
> >Jing
> >
> >On Wed, May 15, 2024 at 7:00 PM Muhammet Orazov
> > wrote:
> >
> >> Thanks Martijn driving this! +1 (non-binding)
> >>
> >> Best,
> >> Muhammet
> >>
> >> On 2024-05-14 06:43, Martijn Visser wrote:
> >> > Hi everyone,
> >> >
> >> > With no more discussions being open in the thread [1] I would like to
> >> > start
> >> > a vote on FLIP-453: Promote Unified Sink API V2 to Public and
> Deprecate
> >> > SinkFunction [2]
> >> >
> >> > The vote will be open for at least 72 hours unless there is an
> >> > objection or
> >> > insufficient votes.
> >> >
> >> > Best regards,
> >> >
> >> > Martijn
> >> >
> >> > [1] https://lists.apache.org/thread/hod6bg421bzwhbfv60lwsck7r81dvo59
> >> > [2]
> >> >
> >>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-453%3A+Promote+Unified+Sink+API+V2+to+Public+and+Deprecate+SinkFunction
> >>
>


[ANNOUNCE] Apache Flink CDC 3.1.0 released

2024-05-17 Thread Qingsheng Ren
The Apache Flink community is very happy to announce the release of
Apache Flink CDC 3.1.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
in a data pipeline.

Please check out the release blog post for an overview of the release:
https://flink.apache.org/2024/05/17/apache-flink-cdc-3.1.0-release-announcement/

The release is available for download at:
https://flink.apache.org/downloads.html

Maven artifacts for Flink CDC can be found at:
https://search.maven.org/search?q=g:org.apache.flink%20cdc

The full release notes are available in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354387

We would like to thank all contributors of the Apache Flink community
who made this release possible!

Regards,
Qingsheng Ren


[jira] [Created] (FLINK-35390) Error reporting in SQL Server connection table structure table in Flink CDC-3.0 version

2024-05-17 Thread Jira
段志民 created FLINK-35390:
---

 Summary: Error reporting in SQL Server connection table structure 
table in Flink CDC-3.0 version
 Key: FLINK-35390
 URL: https://issues.apache.org/jira/browse/FLINK-35390
 Project: Flink
  Issue Type: Bug
  Components: Flink CDC
Affects Versions: 3.1.0
Reporter: 段志民


I am currently using SQL Server connector. I have upgraded from CDC2.2 version 
to 3.0 version. If there is a change in the table structure of SQL Server, the 
online task will report an error, while the old version will not



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


[jira] [Created] (FLINK-35389) Implement List Async State API for ForStStateBackend

2024-05-17 Thread Hangxiang Yu (Jira)
Hangxiang Yu created FLINK-35389:


 Summary: Implement List Async State API for ForStStateBackend
 Key: FLINK-35389
 URL: https://issues.apache.org/jira/browse/FLINK-35389
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / State Backends
Reporter: Hangxiang Yu






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


Re: [VOTE] FLIP-449: Reorganization of flink-connector-jdbc

2024-05-17 Thread Ahmed Hamdy
Hi all,
+1 (non-binding)
Best Regards
Ahmed Hamdy


On Fri, 17 May 2024 at 02:13, Jiabao Sun  wrote:

> Thanks for driving this proposal!
>
> +1 (binding)
>
> Best,
> Jiabao
>
>
> On 2024/05/10 22:18:04 Jeyhun Karimov wrote:
> > Thanks for driving this!
> >
> > +1 (non-binding)
> >
> > Regards,
> > Jeyhun
> >
> > On Fri, May 10, 2024 at 12:50 PM Muhammet Orazov
> >  wrote:
> >
> > > Thanks João for your efforts and driving this!
> > >
> > > +1 (non-binding)
> > >
> > > Best,
> > > Muhammet
> > >
> > > On 2024-05-09 12:01, Joao Boto wrote:
> > > > Hi everyone,
> > > >
> > > > Thanks for all the feedback, I'd like to start a vote on the
> FLIP-449:
> > > > Reorganization of flink-connector-jdbc [1].
> > > > The discussion thread is here [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/display/FLINK/FLIP-449%3A+Reorganization+of+flink-connector-jdbc
> > > > [2] https://lists.apache.org/thread/jc1yvvo35xwqzlxl5mj77qw3hq6f5sgr
> > > >
> > > > Best
> > > > Joao Boto
> > >
> >
>


Re: [VOTE] FLIP-453: Promote Unified Sink API V2 to Public and Deprecate SinkFunction

2024-05-17 Thread Yuepeng Pan
+1(non-binding)


Best,
Yuepeng Pan


At 2024-05-15 21:09:04, "Jing Ge"  wrote:
>+1(binding) Thanks Martijn!
>
>Best regards,
>Jing
>
>On Wed, May 15, 2024 at 7:00 PM Muhammet Orazov
> wrote:
>
>> Thanks Martijn driving this! +1 (non-binding)
>>
>> Best,
>> Muhammet
>>
>> On 2024-05-14 06:43, Martijn Visser wrote:
>> > Hi everyone,
>> >
>> > With no more discussions being open in the thread [1] I would like to
>> > start
>> > a vote on FLIP-453: Promote Unified Sink API V2 to Public and Deprecate
>> > SinkFunction [2]
>> >
>> > The vote will be open for at least 72 hours unless there is an
>> > objection or
>> > insufficient votes.
>> >
>> > Best regards,
>> >
>> > Martijn
>> >
>> > [1] https://lists.apache.org/thread/hod6bg421bzwhbfv60lwsck7r81dvo59
>> > [2]
>> >
>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-453%3A+Promote+Unified+Sink+API+V2+to+Public+and+Deprecate+SinkFunction
>>


[jira] [Created] (FLINK-35388) Flink 1.18.1 get stuck after creating highly available job result storage directory

2024-05-17 Thread Jira
Pedro Mázala created FLINK-35388:


 Summary: Flink 1.18.1 get stuck after creating highly available 
job result storage directory
 Key: FLINK-35388
 URL: https://issues.apache.org/jira/browse/FLINK-35388
 Project: Flink
  Issue Type: Bug
  Components: API / Core
Affects Versions: 1.18.1
Reporter: Pedro Mázala
 Attachments: output2.json

After upgrading to Flink 1.18.1 (from 1.17.2) some pipelines get stuck after 
creating highly available job result storage directory.

I use GCS for storage and I did not find anything unusual in the logs. 


The pod on k8s stays unhealthy until a manual restart (kill JM pod)



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