[jira] [Created] (FLINK-35308) StarRocks sink maps TINYINT type to BOOLEAN incorrectly

2024-05-07 Thread yux (Jira)
yux created FLINK-35308: --- Summary: StarRocks sink maps TINYINT type to BOOLEAN incorrectly Key: FLINK-35308 URL: https://issues.apache.org/jira/browse/FLINK-35308 Project: Flink Issue Type: Bug

Re: [VOTE] Apache Flink CDC Release 3.1.0, release candidate #1

2024-05-07 Thread Qingsheng Ren
Thanks everyone for your verification! I'll investigate the issue and prepare another RC once it is resolved. Much appreciated to Jingsong! This release candidate is now canceled. Best, Qingsheng On Wed, May 8, 2024 at 2:20 PM Jingsong Li wrote: > -1 > > Thanks Qingsheng for preparing this RC

[DISCUSS] Flink CDC 3.2 Release Planning

2024-05-07 Thread Qingsheng Ren
Hi devs, As we are in the midst of the release voting process for Flink CDC 3.1.0, I think it's a good time to kick off the upcoming Flink CDC 3.2 release cycle. In this release cycle I would like to focus on the stability of Flink CDC, especially for the newly introduced YAML-based data integrat

Re: [VOTE] Apache Flink CDC Release 3.1.0, release candidate #1

2024-05-07 Thread Jingsong Li
-1 Thanks Qingsheng for preparing this RC. If you bundle third-party dependencies (non Flink dependencies) in your published jar, you need to write them in the NOTICE file. I recommend adding a test using flink-ci-tools to verify if the NOTICE file is correct. Of course, you cannot rely too much

[jira] [Created] (FLINK-35307) Add Compile CI check on jdk17

2024-05-07 Thread Zakelly Lan (Jira)
Zakelly Lan created FLINK-35307: --- Summary: Add Compile CI check on jdk17 Key: FLINK-35307 URL: https://issues.apache.org/jira/browse/FLINK-35307 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-35306) Flink cannot compile with jdk17

2024-05-07 Thread Rui Fan (Jira)
Rui Fan created FLINK-35306: --- Summary: Flink cannot compile with jdk17 Key: FLINK-35306 URL: https://issues.apache.org/jira/browse/FLINK-35306 Project: Flink Issue Type: Bug Affects Versions: 1

Re: [DISCUSS] FLIP-453: Promote Unified Sink API V2 to Public and Deprecate SinkFunction

2024-05-07 Thread Hongshun Wang
Hi Martijn, Thanks for the proposal +1 from me.Some sinks still use sinkfunction; it's time to take a step forward. Best, Hongshun On Mon, May 6, 2024 at 5:44 PM Leonard Xu wrote: > +1 from my side, thanks Martijn for the effort. > > Best, > Leonard > > > 2024年5月4日 下午7:41,Ahmed Hamdy 写道: > > >

[jira] [Created] (FLINK-35305) FLIP-438: Amazon SQS Sink Connector

2024-05-07 Thread Priya Dhingra (Jira)
Priya Dhingra created FLINK-35305: - Summary: FLIP-438: Amazon SQS Sink Connector Key: FLINK-35305 URL: https://issues.apache.org/jira/browse/FLINK-35305 Project: Flink Issue Type: New Feature

[VOTE] FLIP-452: Allow Skipping Invocation of Function Calls While Constant-folding

2024-05-07 Thread Alan Sheinberg
Hi everyone, I'd like to start a vote on FLIP-452 [1]. It covers adding a new method FunctionDefinition.supportsConstantFolding() as part of the Flink Table/SQL API to allow skipping invocation of functions while constant-folding. It has been discussed in this thread [2]. I would like to start a

Re: Issue in PrefetchCount

2024-05-07 Thread Talat Uyarer
Hi ajay, When you have 3 parallelisms you will have 3 independent clients. If you want to keep prefetch count 3 you need to set setRequestedChannelMax as 1 and setParallelism 3. So All 3 clients can have one connection. Talat On Tue, May 7, 2024 at 5:52 AM ajay pandey wrote: > Hi Flink Team, >

Re: [Vote] FLIP-438: Amazon SQS Sink Connector

2024-05-07 Thread Dhingra, Priya
Hi All, I'm happy to announce that FLIP-438: Amazon SQS Sink Connector[1] has been accepted with 9 approving votes (4 binding). I would like to thank everyone who took part in the discussion and/or voted. - Ahmed Hamdy (non-binding) - Samrat(non-binding) - Danny (binding) - Aleksandr (non-bindin

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

2024-05-07 Thread Alexey Leonov-Vendrovskiy
Hey Paul, Yes, no interchangeability. Just a wire-through for more uniformity. Thanks, Alexey On Tue, May 7, 2024 at 2:10 AM Paul Lam wrote: > Hi Alexey, > > Thanks a lot for bringing up the discussion. I’m big +1 for the FLIP. > > I suppose the goal doesn’t involve the interchangeability of j

[RabbitMQ Connector]: missing support for per consumer QoS (needed for quorum queues)

2024-05-07 Thread charlie vuillemez
Hello devs, Seems RabbitMQ Connector support only global QoS (Prefetch), which is not compatible with RabbitMQ quorum queues.Cf https://www.rabbitmq.com/docs/quorum-queues#feature-matrix Quorum queues is the only option for HA, cause mirrored classic queues are deprecated since RabbitMQ v3.9.Quo

Issue in PrefetchCount

2024-05-07 Thread ajay pandey
Hi Flink Team, I am currently reading streaming data from RabbitMQ and using the RMQConnectionConfig for establishing the connection. Here's how I'm setting up the connection: and we use flink version 1.16.2 and RabbitMQ version 3.10.7 RMQConnectionConfig connectionConfig = new RMQConnectionCon

Re: [DISCUSS] FLIP-448: Introduce Pluggable Workflow Scheduler Interface for Materialized Table

2024-05-07 Thread Ron Liu
Hi, dev Following the recent PoC[1], and drawing on the excellent code design within Flink, I have made the following optimizations to the Public Interfaces section of FLIP: 1. I have renamed WorkflowOperation to RefreshWorkflow. This change better conveys its purpose. RefreshWorkflow is used to

Re: [DISCUSSION] FLIP-449: Reorganization of flink-connector-jdbc

2024-05-07 Thread lorenzo . affetti
Thanks joao for your replies! I also saw the latest PR that allows properties to be specified. Thank for adding the pain points as well, that clarifies a lot. On May 7, 2024 at 09:50 +0200, Muhammet Orazov , wrote: > Thanks João for pointing it out. I didn't know about the PR, I am going > to ch

[jira] [Created] (FLINK-35304) Mongo ITCase fails due to duplicate records after resuming

2024-05-07 Thread yux (Jira)
yux created FLINK-35304: --- Summary: Mongo ITCase fails due to duplicate records after resuming Key: FLINK-35304 URL: https://issues.apache.org/jira/browse/FLINK-35304 Project: Flink Issue Type: Bug

Re: [DISCUSSION] FLIP-456: CompiledPlan support for Batch Execution Mode

2024-05-07 Thread Paul Lam
Hi Alexey, Thanks a lot for bringing up the discussion. I’m big +1 for the FLIP. I suppose the goal doesn’t involve the interchangeability of json plans between batch mode and streaming mode, right? In other words, a json plan compiled in a batch program can’t be run in streaming mode without a

[SUMMARY] Flink 1.20 Release Sync 05/07/2024

2024-05-07 Thread Rui Fan
Dear devs, Today is the third meeting for Flink 1.20 release cycle. I'd like to share the information synced in the meeting. - Feature Freeze As we discussed before, the feature freeze time is June 15, 2024, 00:00 CEST(UTC+2). It is worth noting that there are only 6 weeks left until the f

[jira] [Created] (FLINK-35303) Support logical deletion of datax

2024-05-07 Thread melin (Jira)
melin created FLINK-35303: - Summary: Support logical deletion of datax Key: FLINK-35303 URL: https://issues.apache.org/jira/browse/FLINK-35303 Project: Flink Issue Type: New Feature Compon

Re: [Vote] FLIP-438: Amazon SQS Sink Connector

2024-05-07 Thread Hong Liang
Hi Priya, Great to see the FLIP has passed the vote. It would be good to report the final result of the vote at the end of the thread, listing the binding / non-binding votes in an email. See example here [1] [2] Regards, Hong [1] https://lists.apache.org/thread/3sj88kk0104vzj4hklfgbn3rpdnjxj8v

Re: [DISCUSSION] FLIP-449: Reorganization of flink-connector-jdbc

2024-05-07 Thread Muhammet Orazov
Thanks João for pointing it out. I didn't know about the PR, I am going to check it. Best, Muhammet On 2024-05-06 14:45, João Boto wrote: Hi Muhammet, Have you had a chance to review the recently merged pull request [1]? We've introduced a new feature allowing users to include ad hoc config

Re: [DISCUSS] FLIP-443: Interruptible watermark processing

2024-05-07 Thread Rui Fan
Hi Piotr, Overall this FLIP is fine for me. I have a minor concern: IIUC, the code path will become more complex after this FLIP due to the addition of shouldIntterupt() checks, right? If so, it's better to add a benchmark to check whether the job performance regresses when one job has a lot of t