[jira] [Created] (FLINK-32832) Row对象不兼容scala int

yong yang created FLINK-32832: - Summary: Row对象不兼容scala int Key: FLINK-32832 URL: https://issues.apache.org/jira/browse/FLINK-32832 Project: Flink Issue Type: Bug Components: Table SQL /

[jira] [Created] (FLINK-32831) RuntimeFilterProgram should aware join type when looking for the build side

Lijie Wang created FLINK-32831: -- Summary: RuntimeFilterProgram should aware join type when looking for the build side Key: FLINK-32831 URL: https://issues.apache.org/jira/browse/FLINK-32831 Project: Flin

Re: [DISCUSS] FLIP-330: Support specifying record timestamp requirement

Hi Xintong, Thanks for the detailed explanation of your concern. Let me chime in and provide my thoughts on this issue. Please see my comments for each point inline. Overall, it seems that the main concern with this FLIP is that the 2% throughput saving might not be worth the added implementatio

Re: [DISCUSS] FLIP-330: Support specifying record timestamp requirement

Hi Xintong, Thanks for your comments on this FLIP. I agree with it that most problems mentioned in your comments do exist for this FLIP, but the FLIP's benefit should still be large enough to cancel out these costs. 1. I agree with it that StreamElement should have the extensibility to include ot

[jira] [Created] (FLINK-32830) Support Histogram function

Hanyu Zheng created FLINK-32830: --- Summary: Support Histogram function Key: FLINK-32830 URL: https://issues.apache.org/jira/browse/FLINK-32830 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-32829) Allow setting different values for CPU requests and limits

Ivan Stoiev created FLINK-32829: --- Summary: Allow setting different values for CPU requests and limits Key: FLINK-32829 URL: https://issues.apache.org/jira/browse/FLINK-32829 Project: Flink Issu

Re: [DISCUSS] Connectors, Formats, and even User Code should also be pluggable.

Hi, zhiqiang Thanks for driving this proposal, it looks very interesting. As we all know, Flink has a very powerful connector ecosystem, and as Jing said, all the connectors are currently being externalized, and it would be very useful to design a pluggable mechanism for connectors, which could s

[jira] [Created] (FLINK-32828) Kafka-partition-aware watermark not handled correctly shortly after job start up

Grzegorz Liter created FLINK-32828: -- Summary: Kafka-partition-aware watermark not handled correctly shortly after job start up Key: FLINK-32828 URL: https://issues.apache.org/jira/browse/FLINK-32828

Re: [DISCUSS] FLIP-323: Support Attached Execution on Flink Application Completion for Batch Jobs

Hi Allison Thanks for driving this FLIP. It's a valuable feature for batch jobs. This helps keep "Drop Per-Job Mode [1]" going. +1 for this proposal. However, it seems that the change in this FLIP is not detailed enough. I have a few questions. 1. The config 'execution.attached' is not only use

Re: [DISCUSS] FLIP-330: Support specifying record timestamp requirement

Hi Yunfeng, Thanks for preparing this FLIP. I'm respectful for the efforts you already put into the PoC implementation and benchmarks. However, I have to say I'm quite concerned about this proposal. 1. The FLIP is based on the assumption that in non-timestamp scenarios StreamRecord is the only po

[VOTE] Apache Flink Kubernetes Operator Release 1.6.0, release candidate #2

Hi Everyone, Please review and vote on the release candidate #2 for the version 1.6.0 of Apache Flink Kubernetes Operator, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) **Release Overview** As an overview, the release consists of th

Re: [DISCUSS] FLIP-328: Allow source operators to determine isProcessingBacklog based on watermark lag

Thanks for preparing the FLIP, Xuannan. +1 in general. A quick question, could you explain why we are relying on the watermark for emitting the record attribute? Why not use timestamps in the records? I don't see any concern in using watermarks. Just wondering if there's any deep considerations b

Re: [VOTE] Release flink-connector-mongodb v1.0.2, release candidate 1

Thanks for driving the new release! +1 (binding) - Verified signature and checksum - Built from source locally - Reviewed release note and web PR Best, Qingsheng On Wed, Aug 9, 2023 at 7:45 PM Leonard Xu wrote: > Thanks Danny and Jiabao for driving the work! > > > +1 (binding) > > - built fro

[jira] [Created] (FLINK-32827) Operator fusion codegen may not take effect when enable runtime filter

Lijie Wang created FLINK-32827: -- Summary: Operator fusion codegen may not take effect when enable runtime filter Key: FLINK-32827 URL: https://issues.apache.org/jira/browse/FLINK-32827 Project: Flink

[RESULT][VOTE] FLIP-322 Cooldown period for adaptive scheduler

Hi, The vote has been closed. Thank you for your votes. Here is the result: Binding votes (3 in total): - Martijn Visser - Rui Fan - Maximilian Michels Non-binding votes (1 in total): - Prabhu Joseph According to the Flink Bylaws [1], consensus + three committer votes are required to accept

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Thanks Max! Etienne Le 09/08/2023 à 12:53, Maximilian Michels a écrit : +1 (binding) -Max On Tue, Aug 8, 2023 at 10:56 AM Etienne Chauchot wrote: Hi all, As part of Flink bylaws, binding votes for FLIP changes are active committer votes. Up to now, we have only 2 binding votes. Can one of

[jira] [Created] (FLINK-32826) Our job is stuck on requestMemorySegmentBlocking

Zhongyi Sun created FLINK-32826: --- Summary: Our job is stuck on requestMemorySegmentBlocking Key: FLINK-32826 URL: https://issues.apache.org/jira/browse/FLINK-32826 Project: Flink Issue Type: Bu