Re: [Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

Thanks to @Martijn @Leonard for raising this question This is also something I have been worried about, that is, the issue of code copyright ownership and cooperation. That's why I mark FLIP-202 [1] as draft. I have sent a private email inviting the author to participate. If there is more news, I

Re: [DISCUSS] FLIP-356: Support Nested Fields Filter Pushdown

Hi Venkatakrishnan, The reason why I thought it's abandoned because the Jira ticket is part of the umbrella ticket for FLIP-95. Let's move the Jira ticket to its own dedicated task instead of nested to a FLIP-95 ticket. Thanks, Martijn On Wed, Sep 20, 2023 at 4:34 PM Becket Qin wrote: > > Hi M

Re: [DISCUSS] FLIP-365: Introduce flush interval to adjust the interval of emitting results with idempotent semantics

Hi Yunfeng and Dong, Thanks for this FLIP. I have reviewed it briefly and have a few questions: 1. Is this FLIP proposing to buffer the output in the state backend? If so, what is the data format of this buffer (what type of state does it use and what is the value)? Additionally, how does the ope

Re: [DISCUSS] FLIP-368 Reorganize the exceptions thrown in state interfaces

Fair enough! Thanks Zakelly for the information. Afaic, even users can do nothing with Flink, they still can do something in their territory, at least doing some logging and metrics stuff, or triggering some other services in their ecosystem. After all, the Flink jobs they build are part of their s

Re: Close orphaned/stale PRs

Hi all, I really believe that the problem of the number of open PRs is just that there aren't enough reviewers/resources available to review them. > Stale PRs can clutter the repository, and closing them helps keep it > organized and ensures that only relevant and up-to-date PRs are present. Su

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

Hi all, Jark and I discussed this FLIP offline and I will summarize our discussion below. It would be great if you could provide your opinion of the proposed options. Regarding the target use-cases: - We both agreed that MySQL CDC should have backlog=true when watermarkLag is large during the bin

Re: [VOTE] FLIP-312: Prometheus Sink Connector

Thank you , +1 (non binding) Bests, Samrat On Thu, Sep 21, 2023 at 9:43 AM Leonard Xu wrote: > Thanks Lorenzo for driving this. > > +1(binding) > > Best, > Leonard > > > On Sep 21, 2023, at 11:47 AM, Yun Tang wrote: > > > > +1 (binding) > > > > Thanks for driving this, Lorenzo. > > > > Best >

Re: [VOTE] FLIP-307: Flink Connector Redshift

Thank you , closing the vote. I will share the result in a separate thread. Bests, Samrat On Wed, Sep 20, 2023 at 7:22 PM Leonard Xu wrote: > +1 (binding) > > > Best, > Leonard > > > On Sep 18, 2023, at 11:53 PM, Ahmed Hamdy wrote: > > > > +1 (non-binding) > > Best Regards > > Ahmed Hamdy > >

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Hi Junrui, +1 for following the standard. Thanks for your effort! Best regards, Jing On Thu, Sep 21, 2023 at 5:09 AM Junrui Lee wrote: > Hi Jane, > > Thank you for your valuable feedback and suggestions. > I agree with your point about differentiating between "flink-config.yaml" > and "flink-c

Re: [DISCUSS] FLIP-356: Support Nested Fields Filter Pushdown

Got it, Martijn. Unfortunately, I don't have edit access to the already created JIRA - FLINK-20767 . If you can remove the task from the EPIC FLINK-16987 FLIP-95: Add new table source and sink interfaces

[RESULT][VOTE] FLIP-307: Flink Connector Redshift

Hi Everyone, The proposal, FLIP-307: Flink Connector Redshift, has been accepted with 5 votes (4 binding) . +1 votes: - Danny Cranmer (binding) - Jing Ge (binding) - Ahmed Hamdy (non-binding) - Martijn Visser (binding) - Leonard Xu (binding) Bests, Samrat

Re: [DISCUSS] FLIP-365: Introduce flush interval to adjust the interval of emitting results with idempotent semantics

Hi Zakelly, Thanks for your comments on this FLIP. Please let me attempt to clarify these points. 1. Yes, this FLIP proposes to buffer the outputs in the state backend. As only the latest one of each type of StreamElement is about to be buffered, a ValueState in keyed context or a ListState in no

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

+1 Support for standard YAML format facilitates specification Jing Ge 于2023年9月22日周五 02:23写道： > Hi Junrui, > > +1 for following the standard. Thanks for your effort! > > Best regards, > Jing > > On Thu, Sep 21, 2023 at 5:09 AM Junrui Lee wrote: > > > Hi Jane, > > > > Thank you for your valuable

Re: [VOTE] FLIP-312: Prometheus Sink Connector

+1 (non binding) Samrat Deb 于2023年9月21日周四 23:31写道： > Thank you , > > +1 (non binding) > > Bests, > Samrat > > On Thu, Sep 21, 2023 at 9:43 AM Leonard Xu wrote: > > > Thanks Lorenzo for driving this. > > > > +1(binding) > > > > Best, > > Leonard > > > > > On Sep 21, 2023, at 11:47 AM, Yun Tang

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Hi Junrui, +1 for this proposal, thanks for driving. Best, Lijie ConradJam 于2023年9月22日周五 10:07写道： > +1 Support for standard YAML format facilitates specification > > Jing Ge 于2023年9月22日周五 02:23写道： > > > Hi Junrui, > > > > +1 for following the standard. Thanks for your effort! > > > > Best reg

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Thanks for driving this, +1 for the proposal. Best, Yangze Guo On Fri, Sep 22, 2023 at 11:59 AM Lijie Wang wrote: > > Hi Junrui, > > +1 for this proposal, thanks for driving. > > Best, > Lijie > > ConradJam 于2023年9月22日周五 10:07写道： > > > +1 Support for standard YAML format facilitates specificat

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

+1 for the proposal, thanks for driving. Bet, Shammon FY On Fri, Sep 22, 2023 at 12:41 PM Yangze Guo wrote: > Thanks for driving this, +1 for the proposal. > > Best, > Yangze Guo > > > On Fri, Sep 22, 2023 at 11:59 AM Lijie Wang > wrote: > > > > Hi Junrui, > > > > +1 for this proposal, thanks

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Hello Junrui, +1 for the proposal. Bests, Samrat On Fri, Sep 22, 2023 at 10:18 AM Shammon FY wrote: > +1 for the proposal, thanks for driving. > > Bet, > Shammon FY > > On Fri, Sep 22, 2023 at 12:41 PM Yangze Guo wrote: > > > Thanks for driving this, +1 for the proposal. > > > > Best, > > Ya

[VOTE] FLIP-327: Support switching from batch to stream mode to improve throughput when processing backlog data

Hi all, We would like to start the vote for FLIP-327: Support switching from batch to stream mode to improve throughput when processing backlog data [1]. This FLIP was discussed in this thread [2]. The vote will be open until at least Sep 27th (at least 72 hours), following the consensus voting p

回复: [DISCUSS] FLIP-367: Support Setting Parallelism for Table/SQL Sources

Hi Jane, Thanks for the suggestions and totally agree with them. I've updated the FLIP with the following two changes: 1. ​Rename WrapperTransformation to SourceTransformationWrapper that wraps a SourceTransformation only. Note that we do not plan to support the legacy LegacySourceTransformati

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

Hi, Junrui +1 for the proposal. Thanks for your effort. Best, Yuxin Samrat Deb 于2023年9月22日周五 13:23写道： > Hello Junrui, > > +1 for the proposal. > > > Bests, > Samrat > > On Fri, Sep 22, 2023 at 10:18 AM Shammon FY wrote: > > > +1 for the proposal, thanks for driving. > > > > Bet, > > Shammon