[jira] [Created] (FLINK-23488) Please unsubscribe/remove me from jira user emails

Bhagi created FLINK-23488: - Summary: Please unsubscribe/remove me from jira user emails Key: FLINK-23488 URL: https://issues.apache.org/jira/browse/FLINK-23488 Project: Flink Issue Type: Bug

Re: [VOTE] FLIP-182: Support watermark alignment of FLIP-27 Sources

+1 (binding) On Fri, Jul 23, 2021 at 8:21 AM Seth Wiesman wrote: > +1 (binding) > > Seth > > On Fri, Jul 23, 2021 at 7:31 AM Arvid Heise wrote: > > > +1 (binding) > > > > On Wed, Jul 21, 2021 at 1:55 PM Piotr Nowojski > > wrote: > > > > > Hi everyone, > > > > > > I would like to start a vote

Re: [DISCUSS] FLIP-177: Extend Sink API

Hi, Regarding the question whether to expose the MailboxExecutor or not: 1. We have plans on exposing it in the ProcessFunction (in short we want to make StreamOperator API private/internal only, and move all of it's extra functionality in one way or another to the ProcessFunction). I don't

Re: [VOTE] FLIP-182: Support watermark alignment of FLIP-27 Sources

+1 (binding) Seth On Fri, Jul 23, 2021 at 7:31 AM Arvid Heise wrote: > +1 (binding) > > On Wed, Jul 21, 2021 at 1:55 PM Piotr Nowojski > wrote: > > > Hi everyone, > > > > I would like to start a vote on the FLIP-182 [1] which was discussed in > > this > > thread [2]. > > The vote will be open

[VOTE] Release 1.13.2, release candidate #3

Hi everyone, Please review and vote on the release candidate #3 for the version 1.13.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1],

Re: [DISCUSS] FLIP-180: Adjust StreamStatus and Idleness definition

Hi everyone, I would be in favour of what Arvid said about not exposing the WatermarkStatus to the Sink. Unless there is a very strong argument that this is required I think that keeping this concept internal seems to me the better choice right now. Moreover, as Arvid said the downstream

Re: [VOTE] FLIP-182: Support watermark alignment of FLIP-27 Sources

+1 (binding) On Wed, Jul 21, 2021 at 1:55 PM Piotr Nowojski wrote: > Hi everyone, > > I would like to start a vote on the FLIP-182 [1] which was discussed in > this > thread [2]. > The vote will be open for at least 72 hours unless there is an objection > or not enough votes. > > Best, >

Re: Introduction email

Hello :) pon., 19 lip 2021 o 11:26 Márton Balassi napisał(a): > Hi Srini, > > Welcome to the community. Awesome to hear that LinkedIn decided to embrace > Flink, excited to see where this joint path leads us. > > On Mon, Jul 19, 2021 at 11:02 AM Timo Walther wrote: > > > Hi Srini, > > > >

Re: [DISCUSS] FLIP-180: Adjust StreamStatus and Idleness definition

Hi Eron, thank you very much for your feedback. Please mention that the "temporary status toggle" code will be removed. > This code is already removed but there is still some automation of going idle when temporary no splits are assigned. I will include it in the FLIP. I agree with adding the

[jira] [Created] (FLINK-23487) IRSA doesn't work with S3

Ingo Bürk created FLINK-23487: - Summary: IRSA doesn't work with S3 Key: FLINK-23487 URL: https://issues.apache.org/jira/browse/FLINK-23487 Project: Flink Issue Type: Bug Components:

Re: [DISCUSS] FLIP-179: Expose Standardized Operator Metrics

Hi Becket, I still can't follow your view on the metric being a global variable or your concern that it is confusing to users. Nevertheless, I like your proposal with having an additional collect method. I was thinking that > SourceOutput is going to have an additional method of collect(T

[jira] [Created] (FLINK-23486) Add monitoring/metrics for the ChangelogStateBackend

Roman Khachatryan created FLINK-23486: - Summary: Add monitoring/metrics for the ChangelogStateBackend Key: FLINK-23486 URL: https://issues.apache.org/jira/browse/FLINK-23486 Project: Flink

[jira] [Created] (FLINK-23485) Add a benchmark for the Changelog DFS writer

Roman Khachatryan created FLINK-23485: - Summary: Add a benchmark for the Changelog DFS writer Key: FLINK-23485 URL: https://issues.apache.org/jira/browse/FLINK-23485 Project: Flink Issue

[jira] [Created] (FLINK-23484) Add a benchmark for the ChangelogStateBackend

Roman Khachatryan created FLINK-23484: - Summary: Add a benchmark for the ChangelogStateBackend Key: FLINK-23484 URL: https://issues.apache.org/jira/browse/FLINK-23484 Project: Flink

Re: [DISCUSS] FLIP-177: Extend Sink API

Hi, Arvid >>>The main question here is what do you think is the harm of exposing Mailbox? Is it the complexity or the maintenance overhead? I think that exposing the internal threading model might be risky. In case the threading model changes, it will affect the user's api and bring the burden

Re: [DISCUSS] FLIP-179: Expose Standardized Operator Metrics

Regarding the generic type v.s. class/subclasses of Metadata. I think generic types usually make sense if the framework/abstract class itself does not look into the instances, but just pass them from one user logic to another. Otherwise, interfaces or class/subclasses would be preferred. In our

Re: [DISCUSS] FLIP-179: Expose Standardized Operator Metrics

Hi Arvid, > I'm not sure if I follow the global variable argument, could you elaborate? Are you referring specifically to the SettableGauge? How is that different from a Counter or Meter? What I meant is that the fetch lag computing logic can either get the information required from method

Still receiving these emails.. please unsubscribe me

Hi Team, Please unsubscribe me from all these emails On Fri, 23 Jul 2021 at 2:19 PM, LINZ, Arnaud wrote: > Hello, > > It’s hard to say what caused the timeout to trigger – I agree with you > that it should not have stopped the heartbeat thread, but it did. The easy > fix was to increase it

RE: [DISCUSS] FLIP-185: Shorter heartbeat timeout and interval default values

Hello, It’s hard to say what caused the timeout to trigger – I agree with you that it should not have stopped the heartbeat thread, but it did. The easy fix was to increase it until we no longer see our app self-killed. The task was using a CPU-intensive computation (with a few threads created

[jira] [Created] (FLINK-23483) Add document to describe how to submit job to different executor for sql client

godfrey he created FLINK-23483: -- Summary: Add document to describe how to submit job to different executor for sql client Key: FLINK-23483 URL: https://issues.apache.org/jira/browse/FLINK-23483

[jira] [Created] (FLINK-23482) Simplify BlinkExecutorFactory stack

Timo Walther created FLINK-23482: Summary: Simplify BlinkExecutorFactory stack Key: FLINK-23482 URL: https://issues.apache.org/jira/browse/FLINK-23482 Project: Flink Issue Type: Sub-task

Re: [RESULT][VOTE] FLIP-147: Support Checkpoint After Tasks Finished

I'd be fine to continue w/o a vote as long as the FLIP will contain all the clarifications we talked about in this thread and in FLINK-21080. Cheers, Till On Fri, Jul 23, 2021 at 8:34 AM Dawid Wysakowicz wrote: > How do you feel about proceeding without an additional vote? > > I agree, we

[jira] [Created] (FLINK-23481) KubernetesSharedInformerITCase is unstable

Chesnay Schepler created FLINK-23481: Summary: KubernetesSharedInformerITCase is unstable Key: FLINK-23481 URL: https://issues.apache.org/jira/browse/FLINK-23481 Project: Flink Issue

[jira] [Created] (FLINK-23480) about proxy-user problem

ighack created FLINK-23480: -- Summary: about proxy-user problem Key: FLINK-23480 URL: https://issues.apache.org/jira/browse/FLINK-23480 Project: Flink Issue Type: Improvement Components:

Re: [RESULT][VOTE] FLIP-147: Support Checkpoint After Tasks Finished

How do you feel about proceeding without an additional vote? I agree, we added quite a bit in there, but none of the added content changes what has been voted so far. A big part of the added content can be considered as clarifying the implementation. I'd be inclined to proceed without a vote.