Re: [RESULT] [VOTE] Release 1.19.2, release candidate #1

Hi Alex Has Flink 1.19.2 released? If not, when will be the target date? Leonard Xu 于2025年2月12日周三 09:57写道： > Thanks Alex for driving this release, Good Job! > > minor：XXX should be replaced by votes number, i.e. there are 7 approving > votes, 4 of which are binding > > Best, > Leonard > > > 202

[jira] [Created] (FLINK-37322) surport eval groovy scripts udf for flink sql

tianyuan created FLINK-37322: Summary: surport eval groovy scripts udf for flink sql Key: FLINK-37322 URL: https://issues.apache.org/jira/browse/FLINK-37322 Project: Flink Issue Type: New Feature

Re: [DISCUSS] FLIP-491: BundledAggregateFunction for batched aggregation

Thanks for the comments Timo. 1. Consistency: Could we rename the `canXX` methods to `supportsXX` methods? > This might fit better to the existing methods such as > `FunctionDefinition.supportsConstantFoloding()` and other ability > interfaces that we use in connectors. Sounds good. I c

退订

退订

Re: [DISCUSS] Elasticsearch v3.1 release

Hi Ahmed, I recently working for adopting flink 2.0 for ES Connector. Before that, I need to release a version that supports 1.20. But I saw that you has already kicked off this Elasticsearch v3.1 release, so I was wondering where this is going? I can help you do the stuffs that requires committer

Re: Kafka connector releases

Hi, Devs. I am now working on the Kafka connector bump to Flink 2.0 in 4.0.0 version, and I have already opened a PR for this. Since there is a bug that fix in [FLINK-36568](Flink 2.0) in Flink 2.0-preview1 that would cause fail to run e2e case, so I comment out these e2e tests to pass CI. How

Re: Kafka connector releases

Hi Yanquan, thank you very much for taking care of this. I propose to merge your PR without E2E into 4.0-SNAPSHOT. Then we wait for Flink 2.0.0 with the fix, reenable E2E and lastly we can cut an official 4.0.0 release (we need to wait for 2.0.0 anyways for the release). We could release a 4.0.0-

[jira] [Created] (FLINK-37317) Checkpoint asyncOperationsThreadPool has only one thread running

Jufang He created FLINK-37317: - Summary: Checkpoint asyncOperationsThreadPool has only one thread running Key: FLINK-37317 URL: https://issues.apache.org/jira/browse/FLINK-37317 Project: Flink I

Re: [VOTE] FLIP-508: Add support for Smile format for Compiled plans

+1 (binding) Cheers, Fabian On Thu, Feb 13, 2025 at 12:07 PM David Radley wrote: > +1 (non-binding) > > Kind regards, David. > > From: Sergey Nuyanzin > Date: Thursday, 13 February 2025 at 10:52 > To: dev@flink.apache.org > Subject: [EXTERNAL] [VOTE] FLIP-508: Add support for Smile format for

Migrating CI to Github Actions

Hi all, I was hoping to sync up on the progress on moving from Azure CI to GitHub Actions for the main Flink repository. There was FLIP-396 [1] by Matthias Pohl detailing the plan to trial GitHub Actions and FLINK-27075 [2] which tracks the work. There are several workflows in the repo already

2025/02/13 CHI Eastern time zone workgroup meeting minutes

Hi, We have the 11th 30 minute working meeting of the Community Health Initiative (CHI) for Eastern time zone. In addition to triaging PRs we discussed: * 15 PRs came in this week. * We talked of moving the Flink / CI bot type activity to a G

Re: [DISCUSS] Pluggable Batching for Async Sink in Flink

Hello Ahmed, Thank you for your insights! In fact, FLIP-284 's proposal aligns so well with this approach, I have added it has the future scope. To answer your questions: I assume we wi

[jira] [Created] (FLINK-37318) RocksDBKeyedStateBackend disposed before task exit

Feifan Wang created FLINK-37318: --- Summary: RocksDBKeyedStateBackend disposed before task exit Key: FLINK-37318 URL: https://issues.apache.org/jira/browse/FLINK-37318 Project: Flink Issue Type:

Re: [VOTE] FLIP-508: Add support for Smile format for Compiled plans

+1 (binding) Thanks, Timo On 13.02.25 11:51, Sergey Nuyanzin wrote: Hi everyone, I'd like to start a vote on FLIP-508: Add support for Smile format for Compiled plans [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or

Re: [VOTE] FLIP-508: Add support for Smile format for Compiled plans

+1 (non-binding) Kind regards, David. From: Sergey Nuyanzin Date: Thursday, 13 February 2025 at 10:52 To: dev@flink.apache.org Subject: [EXTERNAL] [VOTE] FLIP-508: Add support for Smile format for Compiled plans Hi everyone, I'd like to start a vote on FLIP-508: Add support for Smile format f

[jira] [Created] (FLINK-37316) Add StateManager#getStateOptional and StateManager#getState methods for DataStream V2

xuhuang created FLINK-37316: --- Summary: Add StateManager#getStateOptional and StateManager#getState methods for DataStream V2 Key: FLINK-37316 URL: https://issues.apache.org/jira/browse/FLINK-37316 Project:

[VOTE] FLIP-508: Add support for Smile format for Compiled plans

Hi everyone, I'd like to start a vote on FLIP-508: Add support for Smile format for Compiled plans [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1] https://cwiki.apache.org/confluence/display/FLINK

Re: [VOTE] FLIP-508: Add support for Smile format for Compiled plans

+1 (non binding) Bests, Samrat On Thu, 13 Feb 2025 at 5:01 PM, Fabian Hüske wrote: > +1 (binding) > > Cheers, Fabian > > On Thu, Feb 13, 2025 at 12:07 PM David Radley > wrote: > > > +1 (non-binding) > > > > Kind regards, David. > > > > From: Sergey Nuyanzin > > Date: Thursday, 13 February 2025

[jira] [Created] (FLINK-37319) Add retry in RocksDBStateUploader for fault tolerant

Zhenqiu Huang created FLINK-37319: - Summary: Add retry in RocksDBStateUploader for fault tolerant Key: FLINK-37319 URL: https://issues.apache.org/jira/browse/FLINK-37319 Project: Flink Issue

Re: [DISCUSS] Pluggable Batching for Async Sink in Flink

FYI: Created FLIP-509. Best Regards Ahmed Hamdy On Thu, 13 Feb 2025 at 16:30, Ahmed Hamdy wrote: > Hi Poorvank, > thanks for the feedback, I can see your point and I kinda agree, I would > say, if you don't need the flushing trigger interface in your use case > let's keep it out of the FLIP fo

Re: [DISCUSS] FLIP-491: BundledAggregateFunction for batched aggregation

Thank you for the update Alan. I just have some last minor comments, mostly around naming: 1. Consistency: Could we rename the `canXX` methods to `supportsXX` methods? This might fit better to the existing methods such as `FunctionDefinition.supportsConstantFoloding()` and other abili

Re: [DISCUSS] Pluggable Batching for Async Sink in Flink

Hi Poorvank, thanks for the feedback, I can see your point and I kinda agree, I would say, if you don't need the flushing trigger interface in your use case let's keep it out of the FLIP for now, Also let's wait for the feedback about that from other members. I will create a FLIP and assign it a nu

[jira] [Created] (FLINK-37320) FINISHED jobs incorrectly being set to RECONCILING

Luca Castelli created FLINK-37320: - Summary: FINISHED jobs incorrectly being set to RECONCILING Key: FLINK-37320 URL: https://issues.apache.org/jira/browse/FLINK-37320 Project: Flink Issue Ty

[jira] [Created] (FLINK-37321) Make window functions with wrong input fail during planning rather than runtime

Sergey Nuyanzin created FLINK-37321: --- Summary: Make window functions with wrong input fail during planning rather than runtime Key: FLINK-37321 URL: https://issues.apache.org/jira/browse/FLINK-37321

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

Hi, Xiangyu >>> I prefer to set the default value of this option as'false in the first place. Setting as true might introduce unexpected behavior for users when operating existing jobs. Maybe we should introduce this feature at first and discuss enabling this feature as default in a separated thr

[jira] [Created] (FLINK-37323) Checkpoint Growth & Akka FrameSize Exception when Migrating from FlinkKafkaProducer to KafkaSink

Zimehr Abbasi created FLINK-37323: - Summary: Checkpoint Growth & Akka FrameSize Exception when Migrating from FlinkKafkaProducer to KafkaSink Key: FLINK-37323 URL: https://issues.apache.org/jira/browse/FLINK-37323

Re: [DISCUSS] FLIP-506: Support Reuse Multiple Table Sinks in Planner

Hi Ron, After second thought, taking sink reuse as a long awaited feature with significant benefits for users, I agree to enable this in the first place. Similar features like `table.optimizer.reuse-sub-plan-enabled` and `table.optimizer.reuse-source-enabled` are also enabled by default. From thi

Re: Migrating CI to Github Actions

I wasn't able to continue with FLIP-396 [1] and didn't have the time to finish off FLINK-33901 [2]. Whoever wants to help out with that effort can pick up the subtasks in FLINK-33901 [2]. I tried to document all the things in the individual tickets. I'm happy to answer questions around that topic.