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,

退订

退订 | | 15901500...@163.com | | 邮箱：15901500...@163.com |

回复： 关于Apache Flink源码贡献流程

Hi, Shammon FY, 感谢你的帮助，我想我缺少了FLIP，我会补上再发起一次讨论 Best regards, tanjialiang. 回复的原邮件 | 发件人 | Shammon FY | | 发送日期 | 2023年4月25日 10:12 | | 收件人 | , | | 主题 | Re: 关于Apache Flink源码贡献流程 | Hi tanjialiang

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

Hi tanjialiang `EncodingFormat`和`DecodingFormat`是PublicEvolving接口，你可以在 https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals 创建一个FLIP，然后在dev邮件组发起FLIP讨论；完成讨论后发起FLIP投票，投票通过后可以在对应的issue上提交PR Best, Shammon FY On Mon, Apr 24, 2023 at 5:10 PM tanjialiang wrote: > Hi, Jing Ge

Re: [Discussion] - Release major Flink version to support JDK 17 (LTS)

Thanks Chesnay for working on this. Would you like to share more info about the JDK bug? Best regards, Jing On Mon, Apr 24, 2023 at 11:39 AM Chesnay Schepler wrote: > As it turns out Kryo isn't a blocker; we ran into a JDK bug. > > On 31/03/2023 08:57, Chesnay Schepler wrote: > > >

Flink-kubernetes-operator with Argocd

Hi, Can anyone who has implemented flink-kubernetes-operator with Argocd share an example code? Thank you, Sweta --

Re: State bootstrapping for Flink SQL / Table API jobs

Thank you, Shammon FY-- Sincerely,Ilya SoinOn 24 Apr 2023, at 15:19, Shammon FY wrote:Thanks Илья, there's already a FLIP [1] and discussion thread [2] about hybrid source. You can follow the progress and welcome to participate in the discussion.[1] 

Re: State bootstrapping for Flink SQL / Table API jobs

Thanks Илья, there's already a FLIP [1] and discussion thread [2] about hybrid source. You can follow the progress and welcome to participate in the discussion. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235836225 [2]

Re: [Flink operator] Flink Autoscale - Limit the max number of scale ups

Hi! Please opena JIRA ticket with the details of your log, config and operator version and we will take a look! Thanks Gyula On Mon, Apr 24, 2023 at 2:04 PM Sriram Ganesh wrote: > Hi, > > I am trying the autoscale provided by the operator. I found that Autoscale > keeps happening even after

[Flink operator] Flink Autoscale - Limit the max number of scale ups

Hi, I am trying the autoscale provided by the operator. I found that Autoscale keeps happening even after reaching max-parallelism. I have a question. How can we set the limit for the scale-up process? Because in my cluster it reached the max limit. So, there won't be any more resources

[ANNOUNCE] Apache flink-connector-aws 4.1.0 for Flink 1.17 released

The Apache Flink community is very happy to announce the release of Apache flink-connector-aws 4.1.0 for Apache Flink 1.17. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is

[ANNOUNCE] Apache flink-connector-mongodb 1.0.1 released

The Apache Flink community is very happy to announce the release of Apache flink-connector-mongodb 1.0.1 for Apache Flink 1.16 and 1.17. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The

Re: [Discussion] - Release major Flink version to support JDK 17 (LTS)

As it turns out Kryo isn't a blocker; we ran into a JDK bug. On 31/03/2023 08:57, Chesnay Schepler wrote: https://github.com/EsotericSoftware/kryo/wiki/Migration-to-v5#migration-guide Kroy themselves state that v5 likely can't read v2 data. However, both versions can be on the classpath

回复： 关于Apache Flink源码贡献流程

Hi, Jing Ge 感谢你的回复。 目前我已经发起了一个英文的邮件讨论（大约两周前），但是目前回复邮件的开发者只有一个，针对这种情况我应该如何去安排后续的代码贡献工作？ Best regrads, tanjialiang. 回复的原邮件 | 发件人 | Jing Ge | | 发送日期 | 2023年4月24日 16:30 | | 收件人 | | | 主题 | Re: 关于Apache Flink源码贡献流程 | Hi， 如果是增加public API变更的话，建议先发起一个英文的邮件讨论，然后看是否需要创建FLIP，然后在基于FLIP发起更具体的技术讨论

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:

关于Apache Flink源码贡献流程

Hello，everyone. 我想向apache flink贡献源码，由于修复这个issue需要新增一些API，按照流程需要发起邮件讨论，但这个topic只得到一名开发者关注，这样的情况下我应该如何进行后面的流程？期待有熟悉flink源码贡献的开发者可以提供帮助 issue: https://issues.apache.org/jira/browse/FLINK-31686 discuss邮件标题: EncodingFormat and DecondingFormat provide copy API Best regrads tanjialiang.

Re: State bootstrapping for Flink SQL / Table API jobs

Hi Shammon FY,I haven’t tried it because AFIK it’s only available in the DataStream API, while our job is in SQL. I’m thinking to write a custom HybridDynamicTableSource which will use HybridSource under the hood. This should allow to bootstrap any SQL / Table API job. Maybe it’s something worth