Re: [ANNOUNCE] Apache Flink 1.18.1 released

Hi folks, The bug has been fixed and PR at docker-library/official-images has been merged. The official images are available now. Best regards, Jing On Mon, Jan 22, 2024 at 11:39 AM Jing Ge wrote: > Hi folks, > > I am still working on the official images because of the issu

Re: [ANNOUNCE] Apache Flink 1.18.1 released

Hi folks, I am still working on the official images because of the issue https://issues.apache.org/jira/browse/FLINK-34165. Images under apache/flink are available. Best regards, Jing On Sun, Jan 21, 2024 at 11:06 PM Jing Ge wrote: > Thanks Leonard for the feedback! Also thanks @Jark

Re: [ANNOUNCE] Apache Flink 1.18.1 released

Thanks Leonard for the feedback! Also thanks @Jark Wu @Chesnay Schepler and each and everyone who worked closely with me for this release. We made it together! Best regards, Jing On Sun, Jan 21, 2024 at 9:25 AM Leonard Xu wrote: > Thanks Jing for driving the release, nice work! > &g

[ANNOUNCE] Apache Flink 1.18.1 released

/browse/FLINK-33824 Feel free to reach out to the release managers (or respond to this thread) with feedback on the release process. Our goal is to constantly improve the release process. Feedback on what could be improved or things that didn't go so well are appreciated. Regards, Jing

[ANNOUNCE] Apache Flink 1.18.0 released

notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352885 We would like to thank all contributors of the Apache Flink community who made this release possible! Best regards, Konstantin, Qingsheng, Sergey, and Jing

Re: 请问1.18什么时候可以发布呢，想体验1.17jdk

快了，已经开始voting了 :-)) On Sun, Oct 15, 2023 at 5:55 AM kcz <573693...@qq.com.invalid> wrote: >

Fwd: [Discussion] Slack Channel

Hi devs, Thanks Giannis for your suggestion. It seems that the last email wasn't sent to the dev ML. It is also an interesting topic for devs and user-zh. Best regards, Jing -- Forwarded message - From: Giannis Polyzos Date: Tue, Aug 22, 2023 at 11:11 AM Subject: [Discussion

Re: [ANNOUNCE] Apache Flink 1.16.2 released

regards, Jing On Mon, May 29, 2023 at 6:27 AM weijie guo wrote: > Hi Jing, > > Thank you for caring about the releasing process. It has to be said that > the entire process went smoothly. We have very comprehensive > documentation[1] to guide my work, thanks to the contribut

Re: [ANNOUNCE] Apache Flink 1.16.2 released

Hi Weijie, Thanks again for your effort. I was wondering if there were any obstacles you had to overcome while releasing 1.16.2 and 1.17.1 that could lead us to any improvement wrt the release process and management? Best regards, Jing On Fri, May 26, 2023 at 4:41 PM Martijn Visser wrote

Re: [ANNOUNCE] Apache Flink 1.17.1 released

Hi Weijie, That is earlier than I expected! Thank you so much for your effort! Best regards, Jing On Fri, May 26, 2023 at 4:44 PM Martijn Visser wrote: > Same here as with Flink 1.16.2, thank you Weijie and those who helped with > testing! > > On Fri, May 26, 2023 at 1:08 P

Re: 关于Apache Flink源码贡献流程

Hi tanjianliang, 你说的英文讨论邮件是这个吧[1]? 建议以后讨论涉及到邮件引用时都带上链接，方便大家理解上下文。 结合邮件以及Jira里面的回复，你可以写好FLIP[2]之后再来发起新的讨论。 Best regards, Jing [1] https://lists.apache.org/thread/3yzvo6mynj637v2z10s895t7hhmv4rjd [2] https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals On Mon, Apr 24

Re: 关于Apache Flink源码贡献流程

Hi， 如果是增加public API变更的话，建议先发起一个英文的邮件讨论，然后看是否需要创建FLIP，然后在基于FLIP发起更具体的技术讨论 On Mon, Apr 24, 2023 at 10:06 AM tanjialiang wrote: > Hello，everyone. > 我想向apache > flink贡献源码，由于修复这个issue需要新增一些API，按照流程需要发起邮件讨论，但这个topic只得到一名开发者关注，这样的情况下我应该如何进行后面的流程？期待有熟悉flink源码贡献的开发者可以提供帮助 > > > issue:

Re: [ANNOUNCE] Flink Table Store Joins Apache Incubator as Apache Paimon(incubating)

Congrats! Best regards, Jing On Mon, Mar 27, 2023 at 2:32 PM Leonard Xu wrote: > Congratulations! > > > Best, > Leonard > > On Mar 27, 2023, at 5:23 PM, Yu Li wrote: > > Dear Flinkers, > > > > As you may have noticed, we are pleased to announce that Fli

Re: [ANNOUNCE] Apache Flink 1.17.0 released

Excellent work! Congratulations! Appreciate the hard work and contributions of everyone in the Apache Flink community who helped make this release possible. Looking forward to those new features. Cheers! Best regards, Jing On Thu, Mar 23, 2023 at 10:24 AM Leonard Xu wrote: > The Apache Fl

Re: [ANNOUNCE] FRocksDB 6.20.3-ververica-2.0 released

Hi Yanfei, Thanks for your effort. Looking forward to checking it. Best regards, Jing On Mon, Jan 30, 2023 at 1:42 PM Yanfei Lei wrote: > It is very happy to announce the release of FRocksDB 6.20.3-ververica-2.0. > > Compiled files for Linux x86, Linux arm, Linux ppc64le, MacOS x86

Re: [ANNOUNCE] Apache Flink 1.16.0 released

Congrats! On Fri, Oct 28, 2022 at 1:22 PM 任庆盛 wrote: > Congratulations and a big thanks to Chesnay, Martijn, Godfrey and Xingbo > for the awesome work for 1.16! > > Best regards, > Qingsheng Ren > > > On Oct 28, 2022, at 14:46, Xingbo Huang wrote: > > > > The Apache Flink community is very

Re: Re: 关于flink table store的疑问

我理解，目前大的目标是为了流批一体，设计上实际上是对存储进行了抽象，从某种角度上来看可以理解为存储虚拟化，未来的想象空间要大很多。Iceberg，Hudi这些可以作为底层对接的一种具体实现。 On Fri, Sep 9, 2022 at 2:44 PM Xuyang wrote: > Hi，我理解Flink table store主要有以下几个优势： > 1、减少架构复杂性，不需要额外引入多余的组件 > 2、支持Flink计算中直接使用Flink table store的存储 > 3、毫秒级流式查询和olap能力 > > > > > -- > > Best！ >

Re: [ANNOUNCE] Apache Flink 1.15.2 released

Thanks Danny for your effort! Best regards, Jing On Wed, Aug 24, 2022 at 11:43 PM Danny Cranmer wrote: > The Apache Flink community is very happy to announce the release of Apache > Flink 1.15.2, which is the second bugfix release for the Apache Flink 1.15 > series. > &g

Re: [ANNOUNCE] Apache Flink Kubernetes Operator 1.1.0 released

Congrats! Thank you all! Best regards, Jing On Mon, Jul 25, 2022 at 7:51 AM Px New <15701181132mr@gmail.com> wrote: >  > > Yang Wang 于2022年7月25日周一 10:55写道： > > > Congrats! Thanks Gyula for driving this release, and thanks to all > > contributors! > >

Re: 怀疑源码中的一个方法是never reached code

Hi, 友情提醒：开ticket以及以后在dev里讨论，记得用英语哈。 祝好 Jing On Tue, Jun 14, 2022 at 3:23 PM Yun Tang wrote: > Hi，育锋 > > 我觉得你的分析应该是没问题的。可以创建一个ticket来修复该问题。另外，关于代码实现的具体讨论，建议在dev邮件列表讨论。 > > 祝好 > 唐云 > > From: 朱育锋 > Sent: Tuesday, June 1

Re: [ANNOUNCE] Apache Flink Kubernetes Operator 1.0.0 released

Amazing! Thanks Yang for driving this! Thanks all for your effort! Best regards, Jing On Sun, Jun 5, 2022 at 11:30 AM tison wrote: > Congrats! Thank you all for making this release happen. > > Best, > tison. > > > rui fan <1996fan...@gmail.com> 于2022年6月5日周

Re: [ANNOUNCE] Welcome to join the Apache Flink community on Slack

Thanks everyone for your effort! Best regards, Jing On Thu, Jun 2, 2022 at 4:17 PM Martijn Visser wrote: > Thanks everyone for joining! It's good to see so many have joined in such > a short time already. I've just refreshed the link which you can always > find on the project w

Re: GlobalCommitter in Flink's two-phase commit

, which is recommended to replace the usage of GlobalCommitter, is used to take care of the post commit topology. Best regards, Jing On Tue, May 24, 2022 at 9:11 AM di wu <676366...@qq.com> wrote: > Hello > Regarding the GlobalCommitter in Flink's two-phase commit, > I see it

如何给flink的输出削峰填谷？

Hi Flink中文社区， 我碰到一个这样的问题，我的数据库有write throttle, 我的flink app是一个10分钟窗口的聚合操作，这样导致，每10分钟有个非常大量的写请求。导致数据库的sink有时候会destroy. 有什么办法把这些写请求均匀分布到10分钟吗？ 谢谢， Jing

Re: flinksql的await

陈卓宇 你好， 在默认情况下，所有提交后的DML都是异步执行的，详见TableEnvironment.executeSql(String statement)的注释。使用.await()和不使用.await()的区别是使用await()后会等待异步查询返回第一行结果（题外话：请注意INSERT和SELECT的区别），详见TableResult.await()注解，具体代码见TableResultImpl.awaitInternal(long timeout, TimeUnit unit), 由于此时入参timeout为-1，导致future.get()被调用,

Re: 退订

...@flink.apache.org For more information, please go to [1]. [1] https://flink.apache.org/community.html#mailing-lists Best, JING ZHANG maozhaolin 于2021年9月26日周日 下午3:28写道： > 退订

Re: [ANNOUNCE] Flink mailing lists archive service has migrated to Apache Archive service

Thanks Leonard for driving this. The information is helpful. Best, JING ZHANG Jark Wu 于2021年9月6日周一 下午4:59写道： > Thanks Leonard, > > I have seen many users complaining that the Flink mailing list doesn't > work (they were using Nabble). > I think this information would be very he

Flink1.12的RocksDB占用的内存大于Flink1.9

请教个问题，同样的业务逻辑，同样的资源配置，作业在Flink1.9和Flink1.12的内存使用相差很大，使用jemalloc分析 发现主要是rocksdb的UncompressBlockContentsForCompressionType方法占用的内存较多 ，运行相同的时间，该方法在Flink1.9 占用内存200MB，在Flink1.12占用内存约4G，大家有遇到过这个现象么？

相同的作业配置 ，Flink1.12 版本的作业checkpoint耗时增加以及制作失败，Flink1.9的作业运行正常

【现象】相同配置的作业（checkpoint interval ：3分钟，作业逻辑：regular join），flink1.9运行正常，flink1.12运行一段时间后，checkpoint制作耗时增大，最后checkpoint制作失败。 【分析】了解到flink1.10后对于checkpoint机制进行调整，接收端在barrier对齐时不会缓存单个barrier到达后的数据，意味着发送方必须在barrier对齐后等待credit feedback来传输数据，因此发送方会产生一定的冷启动，影响到延迟和网络吞吐量，因此调整checkpoint

Re: Flink 1.12.0 隔几个小时Checkpoint就会失败

你好，问题定位到了吗？ 我也遇到了相同的问题，感觉和checkpoint interval有关 我有两个相同的作业（checkpoint interval 设置的是3分钟），一个运行在flink1.9，一个运行在flink1.12，1.9的作业稳定运行，1.12的运行5小时就会checkpoint 制作失败，抛异常 org.apache.flink.util.FlinkRuntimeException: Exceeded checkpoint tolerable failure threshold. 当我把checkpoint

Re: 【PyFlink】对于数据以Csv()格式写入kafka报错，以及使用python udf时无法启动udf

1. 重新安装之后并没有解决。 本地提交和远程提交都有问题。用 python demo.py 的方式是正常的。 2. 作业是已经提交了。 有在提示 Job has been submitted with JobID 05fcaebfec3aca731df408418ebea80c 然后立马会出现下面的错误： 即：Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.beam.sdk.options.PipelineOptionsFactory Traceback (most

Re: 【PyFlink】对于数据以Csv()格式写入kafka报错，以及使用python udf时无法启动udf

Hi, xingbo. 在检查之后，并没有发现什么 beam 的其他版本，flink-python 版本是 2.11-1.11.1。不管是 pip install apache-beam==2.19.0 还是没有，都是一样的问题。 用 udf 的示例代码也不通过。本地 python demo.py 是可以正常的。 只有是 flink run -m localhost:8081 -py demo.py 是一直在出现这种问题。 pyflink-shell.sh remote localhost 8081 也试过了。一样的结果。 示例代码如下： import logging import

Re: 【PyFlink】对于数据以Csv()格式写入kafka报错，以及使用python udf时无法启动udf

Hi, jincheng. 最近也遇到了类似问题，请问有什么思路吗？ flink-python 的 jar 都是有的，且版本是对的。 版本是 1.11.1，这个主要是在引入了 udf 时出现的，之前是正常的。 尝试过 virtualenv 打包 python 环境也没有效果。 具体报错如下： Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.beam.sdk.options.PipelineOptionsFactory at

Re: 【PyFlink】对于数据以Csv()格式写入kafka报错，以及使用python udf时无法启动udf

Hi, jincheng. 目前也遇到了类似问题，请问有什么思路吗？ flink-python 的 jar 都是有的，且版本是对的。 版本是 1.11.1，这个主要是在引入了 udf 时出现的，之前是正常的。 具体报错如下： Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.beam.sdk.options.PipelineOptionsFactory at