Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-06 Thread weijie guo
+1 (non-binding) Best regards, Weijie Mason Chen 于2023年2月7日周二 10:11写道: > +1 (non-binding) > > Best, > Mason > > > On Thu, Feb 2, 2023 at 6:03 PM Leonard Xu wrote: > > > +1 > > > > Best, > > Leonard > > > > > On Feb 3, 2023, at 9:49 AM, Dong Lin wrote: > > > > > > +1 > > > > > > On Thu, Feb

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-06 Thread Mason Chen
+1 (non-binding) Best, Mason On Thu, Feb 2, 2023 at 6:03 PM Leonard Xu wrote: > +1 > > Best, > Leonard > > > On Feb 3, 2023, at 9:49 AM, Dong Lin wrote: > > > > +1 > > > > On Thu, Feb 2, 2023 at 9:31 PM Hang Ruan wrote: > > > >> Hi all, > >> > >> Thanks for all the help about this FLIP. Now

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-02 Thread Leonard Xu
+1 Best, Leonard > On Feb 3, 2023, at 9:49 AM, Dong Lin wrote: > > +1 > > On Thu, Feb 2, 2023 at 9:31 PM Hang Ruan wrote: > >> Hi all, >> >> Thanks for all the help about this FLIP. Now let's start the vote again. >> Based on the discussion[1], we have come to a consensus, so I would like t

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-02 Thread Dong Lin
+1 On Thu, Feb 2, 2023 at 9:31 PM Hang Ruan wrote: > Hi all, > > Thanks for all the help about this FLIP. Now let's start the vote again. > Based on the discussion[1], we have come to a consensus, so I would like to > start a vote on FLIP-274: Introduce metric group for > OperatorCoordinator[2].

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-02 Thread Martijn Visser
+1 Op do 2 feb. 2023 om 16:22 schreef Chesnay Schepler : > > +1 > > On 02/02/2023 15:43, Jark Wu wrote: > > +1 > > > > Best, > > Jark > > > > On Thu, 2 Feb 2023 at 21:31, Hang Ruan wrote: > > > >> Hi all, > >> > >> Thanks for all the help about this FLIP. Now let's start the vote again. > >> Base

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-02 Thread Chesnay Schepler
+1 On 02/02/2023 15:43, Jark Wu wrote: +1 Best, Jark On Thu, 2 Feb 2023 at 21:31, Hang Ruan wrote: Hi all, Thanks for all the help about this FLIP. Now let's start the vote again. Based on the discussion[1], we have come to a consensus, so I would like to start a vote on FLIP-274: Introduc

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-02-02 Thread Jark Wu
+1 Best, Jark On Thu, 2 Feb 2023 at 21:31, Hang Ruan wrote: > Hi all, > > Thanks for all the help about this FLIP. Now let's start the vote again. > Based on the discussion[1], we have come to a consensus, so I would like to > start a vote on FLIP-274: Introduce metric group for > OperatorCoord

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-12 Thread Jark Wu
Hi Chesnay, Welcome back, and sorry for interrupting your vacation. Since there is a negative vote, I'm fine we can cancel the vote and continue the technical discussion back to the DISCUSS thread. I think we all have good intentions for the community. I hope the community collaboration can be mo

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Xintong Song
Hi all, AFAICS, there’s no consensus so far on how we should proceed discussions while some of the participants are unresponsive, in either the Bylaws[1] or any of the ML threads that I’m aware of. Without such consensus, it is understandable that contributors take actions based on their different

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Hang Ruan
Hi, all, Thanks for all discussions about this FLIP first. We all are trying to make Flink better. But not getting a reply quickly really discourages contributors. OperatorCoordinatorMetricGroup and SplitEnumeratorMetricGroup are important for many developers. And many metrics can not be reported

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Chesnay Schepler
You know, back when I wrote that line I actually felt a bit guilty about it and nearly dropped it, since it implicitly accused _someone_ of actually being capable/willing to push something through despite voiced concerns while no ones looking. Turns out things are a lot worse that I thought. Y

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Martijn Visser
Hi Jark, I disagree with your statement that someone doesn't care about the FLIP, especially since that person participated in the initial FLIP discussion and mentioned explicitly "Since I'm on holidays soon, just so no one tries to pull a fast one on me, if this were to go to a vote as-is I'd be

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Jark Wu
Hi Martijn, Thanks for helping us to find Chesnay. Could you clarify how "soon" will Chesnay participate? A day or a week? I agree with your improvement proposal and Hang exactly follows your points. The last-call-for-discussion for Chensay has been sent for more than 72 hours, even after the Chr

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Martijn Visser
Hi Jark and Dong, I fully understand your concerns in this case. I also think that this situation is an exception. This discussion started just before the holiday season in Europe started. The request to Chesnay if he had more comments was sent just a couple of days before Christmas. >From my per

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Dong Lin
Hi Martijn, A collaborative and active community is very important for any open-source project. Flink can succeed today because we have many experienced and passionate developers who collaborate together to develop Flink. It is important that developers can give constructive feedback and help each

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Jark Wu
Hi Martijn, I think we should have a reasonable time window to wait for the discussion response. Many proposals will halt if we have to wait for every reply indefinitely. Chesnay raised some concerns in the thread one month ago and no objections or feedback after that. Hang replied to all the ques

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-11 Thread Martijn Visser
-1 (binding) currently: I don't think this should have gone to a vote yet given that Chesnay deliberately mentioned that he would vote against it as-is. The discussion should have been settled first. On Tue, Jan 10, 2023 at 10:51 AM Zhu Zhu wrote: > +1 (binding) > > Thanks, > Zhu > > Jark Wu 于2

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-10 Thread Zhu Zhu
+1 (binding) Thanks, Zhu Jark Wu 于2023年1月10日周二 17:43写道: > > +1 (binding) > > Best, > Jark > > > 2023年1月10日 12:02,Qingsheng Ren 写道: > > > > Thanks for the FLIP! > > > > +1 (binding) > > > > Best, > > Qingsheng > > > > On Wed, Jan 4, 2023 at 10:08 AM Hang Ruan wrote: > > > >> Hi all, > >> > >> T

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-10 Thread Jark Wu
+1 (binding) Best, Jark > 2023年1月10日 12:02,Qingsheng Ren 写道: > > Thanks for the FLIP! > > +1 (binding) > > Best, > Qingsheng > > On Wed, Jan 4, 2023 at 10:08 AM Hang Ruan wrote: > >> Hi all, >> >> Thanks for all the feedback so far. >> Based on the discussion[1], we have come to a consens

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-09 Thread Qingsheng Ren
Thanks for the FLIP! +1 (binding) Best, Qingsheng On Wed, Jan 4, 2023 at 10:08 AM Hang Ruan wrote: > Hi all, > > Thanks for all the feedback so far. > Based on the discussion[1], we have come to a consensus, so I would like to > start a vote on FLIP-274: Introduce metric group for > OperatorCo

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-05 Thread Hang Ruan
Hi, Martijn, Thanks for your reply. Very glad for your help to review it. Let's make this vote last until Jan 10th. Best, Hang Leonard Xu 于2023年1月5日周四 16:16写道: > Thanks for driving this FLIP, Hang! > > +1 (binding) > > Best, > Leonard > > > On Jan 5, 2023, at 3:08 AM, Martijn Visser > wrote:

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-05 Thread Leonard Xu
Thanks for driving this FLIP, Hang! +1 (binding) Best, Leonard > On Jan 5, 2023, at 3:08 AM, Martijn Visser wrote: > > Hi Hang, > > I haven't had time to read the FLIP yet since this is still a holiday > period in Europe. I would like to read it in the next few days. Can you > keep the vote o

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-04 Thread Martijn Visser
Hi Hang, I haven't had time to read the FLIP yet since this is still a holiday period in Europe. I would like to read it in the next few days. Can you keep the vote open a little longer? Best regards, Martijn On Wed, Jan 4, 2023 at 2:01 PM Dong Lin wrote: > Thanks for proposing the FLIP! > >

Re: [VOTE] FLIP-274: Introduce metric group for OperatorCoordinator

2023-01-04 Thread Dong Lin
Thanks for proposing the FLIP! +1 (binding) Regards, Dong On Wed, Jan 4, 2023 at 10:08 AM Hang Ruan wrote: > Hi all, > > Thanks for all the feedback so far. > Based on the discussion[1], we have come to a consensus, so I would like to > start a vote on FLIP-274: Introduce metric group for > Op