[jira] [Created] (FLINK-36858) [pipeline-kafka] JsonRowDataSerializationSchema compatibility bug

MOBIN created FLINK-36858: - Summary: [pipeline-kafka] JsonRowDataSerializationSchema compatibility bug Key: FLINK-36858 URL: https://issues.apache.org/jira/browse/FLINK-36858 Project: Flink Issue Ty

Re: [DISCUSS] FLIP-487: Show history of rescales in Web UI for AdaptiveScheduler

> I have a minor question for this: could we discuss 2 FLIPs together? Clarification: Organize related designs in different FLIP wikis and discuss them in different discussions. Together just means that two FLIPs can be carried out at the same time. After the design and discussion of both FLIPs a

Re: [DISCUSS] FLIP-487: Show history of rescales in Web UI for AdaptiveScheduler

Thanks Yuepeng for driving this proposal! It's definitely a great addition for Adaptive Scheduler. I see FLIP-487 has 2 docs, one is official wiki[1], one is google doc[2]. It's better to only use one doc to ensure the consistency, I prefer to only use FLIP-487 official wiki due to you have the wi

Re: Blue/Green Deployments support for Flink

Thanks everyone for your input and encouragement! Yes all of these are questions that have popped up one way or another, it won’t be easy to generalize this solution but hopefully we can devise a good initial/extensible architecture. I’ll get to work on the FLIP and make sure all these points

[jira] [Created] (FLINK-36857) Bump scala version to 2.12.20

Sergey Nuyanzin created FLINK-36857: --- Summary: Bump scala version to 2.12.20 Key: FLINK-36857 URL: https://issues.apache.org/jira/browse/FLINK-36857 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-36856) CollectSinkOperatorFactory is not respecting batch size and socket timeout configs

Gabor Somogyi created FLINK-36856: - Summary: CollectSinkOperatorFactory is not respecting batch size and socket timeout configs Key: FLINK-36856 URL: https://issues.apache.org/jira/browse/FLINK-36856

FW: Re: Flink technical debt. Chi meeting

Hello all, We had our 3rd Community Health Initiative meeting today. We triaged 30 PRs! https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=332499620 fyi When you see PR comments like “Reviewed by Chi on …” This means that the Community Health Initiate (Chi) has reviewed the PR and ha

[jira] [Created] (FLINK-36855) Implement Source API in Kudu connector

Ferenc Csaky created FLINK-36855: Summary: Implement Source API in Kudu connector Key: FLINK-36855 URL: https://issues.apache.org/jira/browse/FLINK-36855 Project: Flink Issue Type: New Featur

Re: Blue/Green Deployments support for Flink

Hi Sergio, Thank you for starting the discussion. Blue/Green deployment support would indeed be a great feature. +1 on initiating the FLIP. In addition to David's points about data consistency, I think it is also important to mention in the FLIP that this deployment procedure will probably not be

Re: [DISCUSS] FLIP-488: Expose Async State Processing and New State APIs in Datastream(V1) APIs

Hi Zakelly, Thank for the proposal! I noticed that it says users can invoke `enableAsyncState` after sum or process, thus will this FLIP add `enableAsyncState` to `SingleOutputStreamOperator` as well? Best, Yunfeng > 2024年12月4日 20:32，Zakelly Lan 写道： > > Hi everyone, > > I'd like to start

Re: [DISCUSS] FLIP-488: Expose Async State Processing and New State APIs in Datastream(V1) APIs

Hi Yunfeng, will this FLIP add `enableAsyncState` to `SingleOutputStreamOperator` as > well? Yes. Thanks for the reminder. Best, Zakelly On Thu, Dec 5, 2024 at 7:21 PM Yunfeng Zhou wrote: > Hi Zakelly, > > Thank for the proposal! > > I noticed that it says users can invoke `enableAsyncState

[jira] [Created] (FLINK-36854) Column comments and default expressions gone after being transformed

yux created FLINK-36854: --- Summary: Column comments and default expressions gone after being transformed Key: FLINK-36854 URL: https://issues.apache.org/jira/browse/FLINK-36854 Project: Flink Issue Typ

Re: [DISCUSS] FLIP-488: Expose Async State Processing and New State APIs in Datastream(V1) APIs

Hi Gyula, Thanks for your quick response! 1. Instead of having to implement a method in the interface could we >instead use an empty marker interface such as "WithAsyncStateAccess" > Well it's a good suggestion, I changed the FLIP accordingly. >2. If a function is marked async can t