[jira] [Created] (FLINK-23419) CheckpointBarrierTrackerTest.testNextFirstCheckpointBarrierOvertakesCancellationBarrier fails on Azure

Dawid Wysakowicz created FLINK-23419: Summary: CheckpointBarrierTrackerTest.testNextFirstCheckpointBarrierOvertakesCancellationBarrier fails on Azure Key: FLINK-23419 URL:

[jira] [Created] (FLINK-23418) 'Run kubernetes application HA test' fail on Azure

Dawid Wysakowicz created FLINK-23418: Summary: 'Run kubernetes application HA test' fail on Azure Key: FLINK-23418 URL: https://issues.apache.org/jira/browse/FLINK-23418 Project: Flink

[jira] [Created] (FLINK-23417) MiniClusterITCase.testHandleBatchJobsWhenNotEnoughSlot fails on Azure

Dawid Wysakowicz created FLINK-23417: Summary: MiniClusterITCase.testHandleBatchJobsWhenNotEnoughSlot fails on Azure Key: FLINK-23417 URL: https://issues.apache.org/jira/browse/FLINK-23417

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

I think we're all really close to the same solution. I second Yun's thoughts that MAX_WATERMARK works well for time based buffering, but it does not solve flushing other operations such as e.g. count windows or batching requests in Sinks. I'd prefer to treat the finish() as a message for Operator

Re: [DISCUSS] FLIP-171: Async Sink

Hi, I'm very sorry to participate in this discussion so late. But I have a little question. I understand the goal of this FLIP is to make `Writer` support asynchronous. But my question is: why not let `Committer` support asynchronization? If only `Writer` supports asynchronization, ExactlyOnce is

[jira] [Created] (FLINK-23421) Unify the space handling in RowData CSV parser

Dian Fu created FLINK-23421: --- Summary: Unify the space handling in RowData CSV parser Key: FLINK-23421 URL: https://issues.apache.org/jira/browse/FLINK-23421 Project: Flink Issue Type: Bug

Re: [VOTE] Release 1.12.5, release candidate #2

+1 (binding) - verified checksums & signatures - built from sources - run example jobs with standalone and native k8s deployments Thank you~ Xintong Song On Thu, Jul 15, 2021 at 6:53 PM Jingsong Li wrote: > Hi everyone, > > Please review and vote on the release candidate #2 for the version

Re: [IGNORE] [RESULT] [VOTE] FLIP-150: Introduce Hybrid Source

Hi Becket, Thanks for taking a look at the FLIP page. I just updated it to include the classes that are user facing, i.e. those that a user would interact with when using the HybridSource. I also updated the examples in the HybridSource code block to show both of the scenarios, fixed start

Re: [VOTE] FLIP-184: Refine ShuffleMaster lifecycle management for pluggable shuffle service framework

+1 (non-binding) Best, Jin Guowei Ma 于2021年7月19日周一 上午9:41写道： > +1(binding) > > Best, > Guowei > > > On Fri, Jul 16, 2021 at 5:36 PM Yingjie Cao > wrote: > > > Hi all, > > > > I'd like to start a vote on FLIP-184 [1] which was > > discussed in [2] [3]. The vote will be open for at least 72

[jira] [Created] (FLINK-23420) sql stream mode lag function java.lang.NullPointerException

xiechenling created FLINK-23420: --- Summary: sql stream mode lag function java.lang.NullPointerException Key: FLINK-23420 URL: https://issues.apache.org/jira/browse/FLINK-23420 Project: Flink

Re: [VOTE] FLIP-184: Refine ShuffleMaster lifecycle management for pluggable shuffle service framework

+1(binding) Best, Guowei On Fri, Jul 16, 2021 at 5:36 PM Yingjie Cao wrote: > Hi all, > > I'd like to start a vote on FLIP-184 [1] which was > discussed in [2] [3]. The vote will be open for at least 72 hours > until 7.21 unless there is an objection. > > [1] > >

Re: [VOTE] Release 1.13.2, release candidate #2

+1 (binding) - verified checksums & signatures - built from sources - run example jobs with standalone and native k8s deployments Thank you~ Xintong Song On Wed, Jul 14, 2021 at 4:49 PM Yun Tang wrote: > Hi everyone, > Please review and vote on the release candidate #2 for the version