[jira] [Created] (FLINK-37550) Add 2.0 to PreviousDocs list

Weijie Guo created FLINK-37550: -- Summary: Add 2.0 to PreviousDocs list Key: FLINK-37550 URL: https://issues.apache.org/jira/browse/FLINK-37550 Project: Flink Issue Type: Sub-task Compo

Re: [DISCUSS] FLIP-XXX: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

Hi Rui, Great question, yes, that’s been taken into account. During the transition we check whether the resources are ready and give it a timeout, we also monitor the Kubernetes events and keep track of anything abnormal. If the transition times out, it’s aborted, status is patched and we rai

Re: [DISCUSS] FLIP-XXX: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

Thanks Sergio for the feedback, and Ryan for the valuable input! > During the transition we check whether the resources are ready and give it a timeout, we also monitor the Kubernetes events and keep track of anything abnormal. Would you mind elaborating on it? What's the default timeout? And how

Re: [DISCUSS] FLIP-515: Dynamic Kafka Sink

Hi Arvin, Thank you for taking time to look at this proposal. The concept of KafkaMetadataService is not new, it has been introduced with Dynamic Kafka Source already: https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/datastream/dynamic-kafka/#kafka-metadata-service This is an

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Thanks for driving this & Congrats! Best Yuan On Mon, Mar 24, 2025 at 5:38 PM Leonard Xu wrote: > Congratulations! > > Thanks Xintong, Jark, Jiangjie and Martijn for the release management and > all evolved. > > Best, > Leonard > > > > > 2025年3月24日 16:24，Xintong Song 写道： > > > > The Apache Fli

[jira] [Created] (FLINK-37549) Some scala and markdown syntax errors in tableApi page

cuiyanxiang created FLINK-37549: --- Summary: Some scala and markdown syntax errors in tableApi page Key: FLINK-37549 URL: https://issues.apache.org/jira/browse/FLINK-37549 Project: Flink Issue Ty

Re: [VOTE] FLIP-503: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

+1 (non-binding) Alexander Fedulov ezt írta (időpont: 2025. márc. 24., H, 10:28): > +1 (binding) > > On Mon, 24 Mar 2025 at 01:34, Thomas Weise wrote: > > > > +1 (binding) > > > > > > On Fri, Mar 21, 2025 at 10:02 AM Ferenc Csaky > > > wrote: > > > > > +1 (binding) > > > > > > Thanks, > > > Fe

Re: [DISCUSS] FLIP-517: Better Handling of Dynamic Table Primitives with PTFs

Thanks Timo for the FLIP! This is a great improvement to the FLINK sql syntax around tables. I have two clarification questions: 1. For SEARCH_KEY ``` SELECT * FROM t_other, LATERAL SEARCH_KEY( input => t, on_key => DESCRIPTOR(k), lookup => t_other.name, options => MAP[ '

Re: [DISCUSS] FLIP-XXX: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

Hi Sergio, With relation to the Kubernetes events. It would be great to tackle the integration of ResourceQuota (s) into the Kubernetes operator as part of this initiative. Then we would know we have enough resources to double the resour

[jira] [Created] (FLINK-37548) FLIP-507 : Add Model DDL methods in TABLE API

Yash Anand created FLINK-37548: -- Summary: FLIP-507 : Add Model DDL methods in TABLE API Key: FLINK-37548 URL: https://issues.apache.org/jira/browse/FLINK-37548 Project: Flink Issue Type: New Fea

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! Best, Jingsong On Tue, Mar 25, 2025 at 10:40 AM Yuan Mei wrote: > > Thanks for driving this & Congrats! > > Best > Yuan > > On Mon, Mar 24, 2025 at 5:38 PM Leonard Xu wrote: >> >> Congratulations! >> >> Thanks Xintong, Jark, Jiangjie and Martijn for the release management and

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! And thanks to all who made this release possible! Best, Jark On Tue, 25 Mar 2025 at 14:46, Jingsong Li wrote: > Congratulations! > > Best, > Jingsong > > On Tue, Mar 25, 2025 at 10:40 AM Yuan Mei wrote: > > > > Thanks for driving this & Congrats! > > > > Best > > Yuan > > > >

Re: [DISCUSS] FLIP-511: Support transaction id pooling in Kafka connector

Hi heise, Thanks for pushing this job. Currently, kafka sinks in transactions are not productive, which will influence the whole kafka cluster. As we discussed before, I have three problems when using Kafka exactly-once sink : 1. Too much transaction id https://issues.apache.org/jira/browse/FLINK-

Re: [DISCUSS] FLIP-XXX: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

Yes thanks both Rui and Ryan, points noted! Rui, for now we’re keeping it simple and yes the cluster needs double the resources during the transition time to have both Blue and Green jobs running. Now in order to not be blocked when we’re out of room for a 2n job, we could add something like an

[jira] [Created] (FLINK-37543) Support sink reuse in batch mode

xiangyu feng created FLINK-37543: Summary: Support sink reuse in batch mode Key: FLINK-37543 URL: https://issues.apache.org/jira/browse/FLINK-37543 Project: Flink Issue Type: Sub-task

[ANNOUNCE] Apache Flink 2.0.0 released

The Apache Flink community is very happy to announce the release of Apache Flink 2.0.0, which is the first formal release for the Apache Flink 2.x series. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming app

[jira] [Created] (FLINK-37540) Introduce SupportsTargetColumnWriting sink ability

xiangyu feng created FLINK-37540: Summary: Introduce SupportsTargetColumnWriting sink ability Key: FLINK-37540 URL: https://issues.apache.org/jira/browse/FLINK-37540 Project: Flink Issue Type

[jira] [Created] (FLINK-37542) Support sink reuse in streaming mode

xiangyu feng created FLINK-37542: Summary: Support sink reuse in streaming mode Key: FLINK-37542 URL: https://issues.apache.org/jira/browse/FLINK-37542 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-37544) Replace Timer with single thread scheduled executor for BlobServer

Jiaan Geng created FLINK-37544: -- Summary: Replace Timer with single thread scheduled executor for BlobServer Key: FLINK-37544 URL: https://issues.apache.org/jira/browse/FLINK-37544 Project: Flink

[jira] [Created] (FLINK-37545) StackOverflowError when using MetricGroup in custom WatermarkStrategy

Grzegorz Liter created FLINK-37545: -- Summary: StackOverflowError when using MetricGroup in custom WatermarkStrategy Key: FLINK-37545 URL: https://issues.apache.org/jira/browse/FLINK-37545 Project: Fl

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Awesome! Thanks for all the release managers running this release and all the contributors to contribute to it! Luke On Mon, Mar 24, 2025 at 4:41 PM Zakelly Lan wrote: > Congratulations! Thanks Xintong, Jark, Jiangjie and Martijn for driving the > 2.0. > Thanks everyone for the great work!

[jira] [Created] (FLINK-37546) KryoSerializer breaks without Twitter Chill library

Maximilian Michels created FLINK-37546: -- Summary: KryoSerializer breaks without Twitter Chill library Key: FLINK-37546 URL: https://issues.apache.org/jira/browse/FLINK-37546 Project: Flink

Re: [VOTE] FLIP-503: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

+1 (binding) On Mon, 24 Mar 2025 at 01:34, Thomas Weise wrote: > > +1 (binding) > > > On Fri, Mar 21, 2025 at 10:02 AM Ferenc Csaky > wrote: > > > +1 (binding) > > > > Thanks, > > Ferenc > > > > > > > > > > On Friday, March 21st, 2025 at 14:48, Őrhidi Mátyás < > > matyas.orh...@gmail.com> wrote:

[jira] [Created] (FLINK-37547) Add initial document for PTFs

Timo Walther created FLINK-37547: Summary: Add initial document for PTFs Key: FLINK-37547 URL: https://issues.apache.org/jira/browse/FLINK-37547 Project: Flink Issue Type: Sub-task

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! Thanks Xintong, Jark, Jiangjie and Martijn for the release management and all evolved. Best, Leonard > 2025年3月24日 16:24，Xintong Song 写道： > > The Apache Flink community is very happy to announce the release of Apache > Flink 2.0.0, which is the first formal release for the

[jira] [Created] (FLINK-37539) performance optimization in Paimon Sink to reduce end-to-end checkpoint time

Yanquan Lv created FLINK-37539: -- Summary: performance optimization in Paimon Sink to reduce end-to-end checkpoint time Key: FLINK-37539 URL: https://issues.apache.org/jira/browse/FLINK-37539 Project: Fli

[jira] [Created] (FLINK-37541) Deprecate getTargetColumns in DynamicTableSink.Context

xiangyu feng created FLINK-37541: Summary: Deprecate getTargetColumns in DynamicTableSink.Context Key: FLINK-37541 URL: https://issues.apache.org/jira/browse/FLINK-37541 Project: Flink Issue

[DISCUSS] Planning Flink 2.1

Hi everyone, With the release announcement of Flink 2.0, it's a good time to kick off discussion of the next release 2.1. - Release Managers I'd like to volunteer as one of the release managers this time. It has been good practice to have a team of release managers from different backgrounds, so

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! Thanks Xintong, Jark, Jiangjie and Martijn for driving the 2.0. Thanks everyone for the great work! Best, Zakelly On Mon, Mar 24, 2025 at 4:24 PM Xintong Song wrote: > The Apache Flink community is very happy to announce the release of Apache > Flink 2.0.0, which is the first

[jira] [Created] (FLINK-37537) Duplicate key when job failover in SchemaOperator

linqigeng created FLINK-37537: - Summary: Duplicate key when job failover in SchemaOperator Key: FLINK-37537 URL: https://issues.apache.org/jira/browse/FLINK-37537 Project: Flink Issue Type: Bug

Re: [DISCUSS] FLIP-495: Support AdaptiveScheduler record and query the rescale history

Hi, Community, There haven’t been any further responses to this email over the past few days. I'd like to initiate a vote on the current proposal[1] in the next few days. Please rest assured that I’m proceeding cautiously and not rushing the process. If there are any concerns about this FLIP-495[1

Re: [DISCUSS] FLIP-XXX: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

To answer here a question by Pedro Mázala, > When we say > >> >> - Records/data will be duplicated for as long as both pipelines are >> running concurrently >> >> > Do we mean the source record will be forwarded to both pipelines? I'm > asking this just as a concern because, depending on t