[jira] [Created] (FLINK-37415) [Release-2.0] Prepare RC1 release

Xintong Song created FLINK-37415: Summary: [Release-2.0] Prepare RC1 release Key: FLINK-37415 URL: https://issues.apache.org/jira/browse/FLINK-37415 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-37414) Java heap space OOM in test_cron_azure core

Weijie Guo created FLINK-37414: -- Summary: Java heap space OOM in test_cron_azure core Key: FLINK-37414 URL: https://issues.apache.org/jira/browse/FLINK-37414 Project: Flink Issue Type: Bug

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

Hey devs, Thank you all for participating in the discussion! I've updated this doc based on feedback. Please feel free to share any further thoughts. If there are no additional suggestions, I plan to initiate a vote within the next few days. On Wed, Feb 26, 2025 at 9:00 PM Poorvank Bhatia wrote

Re: [DISCUSS] FLIP-505: Flink History Server Scability Improvements, Remote Data Store Fetch and Per Job Fetch

Hi Yanquan, I've updated the FLIP to contain the default values, thanks for your help! Sincerely - Allison On Thu, Jan 30, 2025 at 3:21 AM Yanquan Lv wrote: > Thank you for your explanation. I have basically solved the previous > questions. > > Regarding the second point, I would like to sugge

Re: [DISCUSS] FLIP-505: Flink History Server Scability Improvements, Remote Data Store Fetch and Per Job Fetch

Hi Venkat, To reply to your questions: 1. Correct, only if remote fetch is enabled as a configuration, will the remote storage and local cache limits be decoupled. Otherwise, the system will behave as previously. 2. I've clarified the description in the FLIP. Regarding decoupling the two features

[jira] [Created] (FLINK-37413) Introduce append-only RowTimeDeduplicateFunction with Async State API

Piotr Nowojski created FLINK-37413: -- Summary: Introduce append-only RowTimeDeduplicateFunction with Async State API Key: FLINK-37413 URL: https://issues.apache.org/jira/browse/FLINK-37413 Project: Fl

[RESULT] [VOTE] Apache Flink Kubernetes Operator Release 1.11.0, release candidate #1

I'm happy to announce that we have unanimously approved this release. There are 4 approving votes, 3 of which are binding: * Rui Fan (binding) * Gyula Fora (binding) * Max Michels (binding) * Tom Cooper (non-binding) There are no disapproving votes. Thanks everyone! Gyula

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.11.0, release candidate #1

Thank you all! Closing the vote Gyula On Fri, Feb 28, 2025 at 12:34 PM Maximilian Michels wrote: > +1 (binding) > > 1. Verified the archives, checksums, and signatures > 2. Extracted and inspected the source code for binaries > 3. Compiled and tested the source code via mvn verify > 4. Verifie

[jira] [Created] (FLINK-37412) Add slot allocation strategy to for selecting TMs first that have already slots assigned

Matthias Pohl created FLINK-37412: - Summary: Add slot allocation strategy to for selecting TMs first that have already slots assigned Key: FLINK-37412 URL: https://issues.apache.org/jira/browse/FLINK-37412

[jira] [Created] (FLINK-37411) Introduce the rollback mechanism for Autoscaler

Rui Fan created FLINK-37411: --- Summary: Introduce the rollback mechanism for Autoscaler Key: FLINK-37411 URL: https://issues.apache.org/jira/browse/FLINK-37411 Project: Flink Issue Type: New Featur

Re: [DISCUSS] Split-level Watermark Metrics

Hi Efrat, Thanks for the proposal and +1 from my side for this FLIP. Flink currently has a huge observability gap when it comes to the state of the per-split watermarks, which makes it very difficult for users to understand why any given job generated any particular operator-level watermark. Prov