[jira] [Created] (FLINK-26210) PulsarSourceUnorderedE2ECase failed on azure due to multiple causes

[Yun Gao (Jira)]

Yun Gao created FLINK-26210:
---

 Summary: PulsarSourceUnorderedE2ECase failed on azure due to 
multiple causes
 Key: FLINK-26210
 URL: https://issues.apache.org/jira/browse/FLINK-26210
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.0
Reporter: Yun Gao



{code:java}
Feb 17 04:58:33 [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time 
elapsed: 85.664 s <<< FAILURE! - in 
org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase
Feb 17 04:58:33 [ERROR] 
org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase.testOneSplitWithMultipleConsumers(TestEnvironment,
 DataStreamSourceExternalContext)[1]  Time elapsed: 0.571 s  <<< ERROR!
Feb 17 04:58:33 
org.apache.pulsar.client.admin.PulsarAdminException$GettingAuthenticationDataException:
 
Feb 17 04:58:33 java.util.concurrent.ExecutionException: 
org.apache.pulsar.client.admin.PulsarAdminException$GettingAuthenticationDataException:
 A MultiException has 2 exceptions.  They are:
Feb 17 04:58:33 1. java.lang.NoClassDefFoundError: 
javax/xml/bind/annotation/XmlElement
Feb 17 04:58:33 2. java.lang.IllegalStateException: Unable to perform 
operation: create on 
org.apache.pulsar.shade.org.glassfish.jersey.jackson.internal.DefaultJacksonJaxbJsonProvider
Feb 17 04:58:33 
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.BaseResource.request(BaseResource.java:70)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.BaseResource.asyncPutRequest(BaseResource.java:120)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.TopicsImpl.createPartitionedTopicAsync(TopicsImpl.java:430)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.TopicsImpl.createPartitionedTopicAsync(TopicsImpl.java:421)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.TopicsImpl.createPartitionedTopic(TopicsImpl.java:373)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.testutils.runtime.PulsarRuntimeOperator.lambda$createPartitionedTopic$11(PulsarRuntimeOperator.java:504)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneaky(PulsarExceptionUtils.java:60)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneakyAdmin(PulsarExceptionUtils.java:50)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.testutils.runtime.PulsarRuntimeOperator.createPartitionedTopic(PulsarRuntimeOperator.java:504)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.testutils.runtime.PulsarRuntimeOperator.createTopic(PulsarRuntimeOperator.java:184)
Feb 17 04:58:33 at 
org.apache.flink.tests.util.pulsar.cases.KeySharedSubscriptionContext.createSourceSplitDataWriter(KeySharedSubscriptionContext.java:111)
Feb 17 04:58:33 at 
org.apache.flink.tests.util.pulsar.common.UnorderedSourceTestSuiteBase.testOneSplitWithMultipleConsumers(UnorderedSourceTestSuiteBase.java:73)
Feb 17 04:58:33 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Feb 17 04:58:33 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Feb 17 04:58:33 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Feb 17 04:58:33 at 
java.base/java.lang.reflect.Method.invoke(Method.java:566)
Feb 17 04:58:33 at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
{code}

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31702&view=logs&j=6e8542d7-de38-5a33-4aca-458d6c87066d&t=5846934b-7a4f-545b-e5b0-eb4d8bda32e1&l=15537



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26211) PulsarSourceUnorderedE2ECase failed on azure due to multiple causes

[Yun Gao (Jira)]

Yun Gao created FLINK-26211:
---

 Summary: PulsarSourceUnorderedE2ECase failed on azure due to 
multiple causes
 Key: FLINK-26211
 URL: https://issues.apache.org/jira/browse/FLINK-26211
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.0
Reporter: Yun Gao



{code:java}
Feb 17 04:58:33 [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time 
elapsed: 85.664 s <<< FAILURE! - in 
org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase
Feb 17 04:58:33 [ERROR] 
org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase.testOneSplitWithMultipleConsumers(TestEnvironment,
 DataStreamSourceExternalContext)[1]  Time elapsed: 0.571 s  <<< ERROR!
Feb 17 04:58:33 
org.apache.pulsar.client.admin.PulsarAdminException$GettingAuthenticationDataException:
 
Feb 17 04:58:33 java.util.concurrent.ExecutionException: 
org.apache.pulsar.client.admin.PulsarAdminException$GettingAuthenticationDataException:
 A MultiException has 2 exceptions.  They are:
Feb 17 04:58:33 1. java.lang.NoClassDefFoundError: 
javax/xml/bind/annotation/XmlElement
Feb 17 04:58:33 2. java.lang.IllegalStateException: Unable to perform 
operation: create on 
org.apache.pulsar.shade.org.glassfish.jersey.jackson.internal.DefaultJacksonJaxbJsonProvider
Feb 17 04:58:33 
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.BaseResource.request(BaseResource.java:70)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.BaseResource.asyncPutRequest(BaseResource.java:120)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.TopicsImpl.createPartitionedTopicAsync(TopicsImpl.java:430)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.TopicsImpl.createPartitionedTopicAsync(TopicsImpl.java:421)
Feb 17 04:58:33 at 
org.apache.pulsar.client.admin.internal.TopicsImpl.createPartitionedTopic(TopicsImpl.java:373)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.testutils.runtime.PulsarRuntimeOperator.lambda$createPartitionedTopic$11(PulsarRuntimeOperator.java:504)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneaky(PulsarExceptionUtils.java:60)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneakyAdmin(PulsarExceptionUtils.java:50)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.testutils.runtime.PulsarRuntimeOperator.createPartitionedTopic(PulsarRuntimeOperator.java:504)
Feb 17 04:58:33 at 
org.apache.flink.connector.pulsar.testutils.runtime.PulsarRuntimeOperator.createTopic(PulsarRuntimeOperator.java:184)
Feb 17 04:58:33 at 
org.apache.flink.tests.util.pulsar.cases.KeySharedSubscriptionContext.createSourceSplitDataWriter(KeySharedSubscriptionContext.java:111)
Feb 17 04:58:33 at 
org.apache.flink.tests.util.pulsar.common.UnorderedSourceTestSuiteBase.testOneSplitWithMultipleConsumers(UnorderedSourceTestSuiteBase.java:73)
Feb 17 04:58:33 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Feb 17 04:58:33 at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Feb 17 04:58:33 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Feb 17 04:58:33 at 
java.base/java.lang.reflect.Method.invoke(Method.java:566)
Feb 17 04:58:33 at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
Feb 17 04:58:33 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
{code}

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31702&view=logs&j=6e8542d7-de38-5a33-4aca-458d6c87066d&t=5846934b-7a4f-545b-e5b0-eb4d8bda32e1&l=15537



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26212) UnalignedCheckpointRescaleITCase.shouldRescaleUnalignedCheckpoint failed due to java.nio.file.NoSuchFileException

[Yun Gao (Jira)]

Yun Gao created FLINK-26212:
---

 Summary: 
UnalignedCheckpointRescaleITCase.shouldRescaleUnalignedCheckpoint failed due to 
java.nio.file.NoSuchFileException
 Key: FLINK-26212
 URL: https://issues.apache.org/jira/browse/FLINK-26212
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Checkpointing
Affects Versions: 1.14.3
Reporter: Yun Gao



{code:java}
Feb 17 01:59:30 [ERROR] Tests run: 36, Failures: 0, Errors: 1, Skipped: 0, Time 
elapsed: 203.954 s <<< FAILURE! - in 
org.apache.flink.test.checkpointing.UnalignedCheckpointRescaleITCase
Feb 17 01:59:30 [ERROR] shouldRescaleUnalignedCheckpoint[downscale multi_input 
from 2 to 
1](org.apache.flink.test.checkpointing.UnalignedCheckpointRescaleITCase)  Time 
elapsed: 1.154 s  <<< ERROR!
Feb 17 01:59:30 java.io.UncheckedIOException: 
java.nio.file.NoSuchFileException: 
/tmp/junit9158163965206615901/junit1958406566349108348/eec2fe5565487e3ce4c95764a842f712/chk-6/7ab2b240-a313-4d38-9806-8a97334abbc8
Feb 17 01:59:30 at 
java.base/java.nio.file.FileTreeIterator.fetchNextIfNeeded(FileTreeIterator.java:87)
Feb 17 01:59:30 at 
java.base/java.nio.file.FileTreeIterator.hasNext(FileTreeIterator.java:103)
Feb 17 01:59:30 at 
java.base/java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
Feb 17 01:59:30 at 
java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
Feb 17 01:59:30 at 
java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
Feb 17 01:59:30 at 
java.base/java.util.stream.ReferencePipeline.findAny(ReferencePipeline.java:548)
Feb 17 01:59:30 at 
org.apache.flink.test.checkpointing.UnalignedCheckpointTestBase.hasMetadata(UnalignedCheckpointTestBase.java:189)
Feb 17 01:59:30 at 
org.apache.flink.test.checkpointing.UnalignedCheckpointTestBase.isCompletedCheckpoint(UnalignedCheckpointTestBase.java:179)
Feb 17 01:59:30 at 
java.base/java.nio.file.Files.lambda$find$2(Files.java:3948)
Feb 17 01:59:30 at 
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:176)
Feb 17 01:59:30 at 
java.base/java.util.Iterator.forEachRemaining(Iterator.java:133)
Feb 17 01:59:30 at 
java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
Feb 17 01:59:30 at 
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
Feb 17 01:59:30 at 
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
Feb 17 01:59:30 at 
java.base/java.util.stream.ReferencePipeline.reduce(ReferencePipeline.java:558)
Feb 17 01:59:30 at 
java.base/java.util.stream.ReferencePipeline.max(ReferencePipeline.java:594)
Feb 17 01:59:30 at 
org.apache.flink.test.checkpointing.UnalignedCheckpointTestBase.execute(UnalignedCheckpointTestBase.java:169)
Feb 17 01:59:30 at 
org.apache.flink.test.checkpointing.UnalignedCheckpointRescaleITCase.shouldRescaleUnalignedCheckpoint(UnalignedCheckpointRescaleITCase.java:515)
Feb 17 01:59:30 at 
jdk.internal.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
Feb 17 01:59:30 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Feb 17 01:59:30 at 
java.base/java.lang.reflect.Method.invoke(Method.java:566)
Feb 17 01:59:30 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
Feb 17 01:59:30 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
Feb 17 01:59:30 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
Feb 17 01:59:30 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
Feb 17 01:59:30 at org.junit.rules.Verifier$1.evaluate(Verifier.java:35)
Feb 17 01:59:30 at 
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
Feb 17 01:59:30 at 
org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
Feb 17 01:59:30 at 
org.junit.rules.TestWatcher$1.evaluate(TestWatc

[jira] [Created] (FLINK-26213) Translate "Deduplication" page into Chinese

[Edmond Wang (Jira)]

Edmond Wang created FLINK-26213:
---

 Summary: Translate "Deduplication" page into Chinese
 Key: FLINK-26213
 URL: https://issues.apache.org/jira/browse/FLINK-26213
 Project: Flink
  Issue Type: Improvement
  Components: chinese-translation, Documentation
Affects Versions: 1.14.4
Reporter: Edmond Wang


The page url is 
https://nightlies.apache.org/flink/flink-docs-release-1.14/zh/docs/dev/table/sql/queries/deduplication/

The markdown file is located in 
*docs/content.zh/docs/dev/table/sql/queries/deduplication.md*



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Aitozi]

Congratulations!

Best,
Aitozi

Guowei Ma  于2022年2月17日周四 15:52写道：

> Congratulations to Feng and Zhipeng!
> Best,
> Guowei
>
>
> On Thu, Feb 17, 2022 at 3:30 PM Yang Wang  wrote:
>
> > Congratulations!
> >
> > Best,
> > Yang
> >
> > Lijie Wang  于2022年2月17日周四 14:21写道：
> >
> > > Congratulations to all of you!
> > >
> > > Best,
> > > Lijie
> > >
> > > Zakelly Lan  于2022年2月17日周四 12:21写道：
> > >
> > > > Congratulations :-D
> > > >
> > > > On Thu, Feb 17, 2022 at 12:15 PM Leonard Xu 
> wrote:
> > > >
> > > > > Congratulations !
> > > > >
> > > > >
> > > > > Best,
> > > > > Leonard
> > > > >
> > > > > > 2022年2月17日 上午11:17，Paul Lam  写道：
> > > > > >
> > > > > > Congrats! Well deserved!
> > > > > >
> > > > > > Best,
> > > > > > Paul Lam
> > > > > >
> > > > > >> 2022年2月16日 21:30，Robert Metzger  写道：
> > > > > >>
> > > > > >> Hi everyone,
> > > > > >>
> > > > > >> On behalf of the PMC, I'm very happy to announce two new Flink
> > > > > >> committers: Feng Wang and Zhipeng Zhang!
> > > > > >>
> > > > > >> Feng is one of the most active Flink evangelists in China, with
> > > plenty
> > > > > of
> > > > > >> public talks, blog posts and other evangelization activities.
> The
> > > PMC
> > > > > wants
> > > > > >> to recognize and value these efforts by making Feng a committer!
> > > > > >>
> > > > > >> Zhipeng Zhang has made significant contributions to flink-ml,
> like
> > > > most
> > > > > of
> > > > > >> the FLIPs for our ML efforts.
> > > > > >>
> > > > > >> Please join me in welcoming them as committers!
> > > > > >>
> > > > > >>
> > > > > >> Best,
> > > > > >> Robert
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Aitozi]

Congratulations!

Best,
Aitozi


Guowei Ma  于2022年2月17日周四 15:53写道：

> Congratulations
>
> Best,
> Guowei
>
>
> On Thu, Feb 17, 2022 at 3:29 PM Yang Wang  wrote:
>
> > Congratulations to all of you!
> >
> > Best,
> > Yang
> >
> > Lijie Wang  于2022年2月17日周四 14:20写道：
> >
> > > Congratulations to all of you!
> > >
> > > Best,
> > > Lijie
> > >
> > > Leonard Xu  于2022年2月17日周四 12:13写道：
> > >
> > > > Congratulations !
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > > > 2022年2月17日 上午11:09，Yun Tang  写道：
> > > > >
> > > > > Congratulations to all of you!
> > > > >
> > > > > Best,
> > > > > Yun Tang
> > > > > 
> > > > > From: Yangze Guo 
> > > > > Sent: Thursday, February 17, 2022 10:44
> > > > > To: dev 
> > > > > Cc: ro...@apache.org 
> > > > > Subject: Re: [ANNOUNCE] New Flink PMC members: Igal Shilman,
> > Konstantin
> > > > Knauf and Yun Gao
> > > > >
> > > > > Congratulations! Well deserved.
> > > > >
> > > > > Best,
> > > > > Yangze Guo
> > > > >
> > > > > On Thu, Feb 17, 2022 at 10:15 AM Paul Lam 
> > > wrote:
> > > > >>
> > > > >> Congrats to all of you!
> > > > >>
> > > > >> Best,
> > > > >> Paul Lam
> > > > >>
> > > > >>> 2022年2月17日 01:24，Roman Khachatryan  写道：
> > > > >>>
> > > > >>> Congratulations!
> > > > >>>
> > > > >>> Regards,
> > > > >>> Roman
> > > > >>>
> > > > >>> On Wed, Feb 16, 2022 at 5:22 PM Matthias Pohl <
> > > matth...@ververica.com>
> > > > wrote:
> > > > 
> > > >  Congratulations to all of you :)
> > > > 
> > > >  On Wed, Feb 16, 2022 at 4:04 PM Till Rohrmann <
> > trohrm...@apache.org
> > > >
> > > > wrote:
> > > > 
> > > > > Congratulations! Well deserved!
> > > > >
> > > > > Cheers,
> > > > > Till
> > > > >
> > > > > On Wed, Feb 16, 2022 at 2:51 PM Martijn Visser <
> > > > mart...@ververica.com>
> > > > > wrote:
> > > > >
> > > > >> Congratulations to all of you!
> > > > >>
> > > > >> Best regards,
> > > > >>
> > > > >> Martijn Visser
> > > > >> https://twitter.com/MartijnVisser82
> > > > >>
> > > > >>
> > > > >> On Wed, 16 Feb 2022 at 14:29, Fabian Paul 
> > > wrote:
> > > > >>
> > > > >>> Congrats to all three of you, well deserved.
> > > > >>>
> > > > >>> Best,
> > > > >>> Fabian
> > > > >>>
> > > > >>> On Wed, Feb 16, 2022 at 2:23 PM Robert Metzger <
> > > > rmetz...@apache.org>
> > > > >>> wrote:
> > > > 
> > > >  Hi all,
> > > > 
> > > >  I would like to formally announce a few new Flink PMC
> members
> > on
> > > > the
> > > > >> dev@
> > > >  list. The PMC has not done a good job of always announcing
> new
> > > PMC
> > > > >>> members
> > > >  (and committers) recently. I'll try to keep an eye on this
> in
> > > the
> > > > >> future
> > > > >>> to
> > > >  improve the situation.
> > > > 
> > > >  Nevertheless, I'm very happy to announce some very active
> > > > community
> > > > >>> members
> > > >  as new PMC members:
> > > > 
> > > >  - Igal Shilman, added to the PMC in October 2021
> > > >  - Konstantin Knauf, added to the PMC in January 2022
> > > >  - Yun Gao, added to the PMC in February 2022
> > > > 
> > > >  Please join me in welcoming them to the Flink PMC!
> > > > 
> > > >  Best,
> > > >  Robert
> > > > >>>
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Yuan Mei]

Congratulations!

Best Regards,
Yuan

On Thu, Feb 17, 2022 at 5:15 PM Aitozi  wrote:

> Congratulations!
>
> Best,
> Aitozi
>
> Guowei Ma  于2022年2月17日周四 15:52写道：
>
> > Congratulations to Feng and Zhipeng!
> > Best,
> > Guowei
> >
> >
> > On Thu, Feb 17, 2022 at 3:30 PM Yang Wang  wrote:
> >
> > > Congratulations!
> > >
> > > Best,
> > > Yang
> > >
> > > Lijie Wang  于2022年2月17日周四 14:21写道：
> > >
> > > > Congratulations to all of you!
> > > >
> > > > Best,
> > > > Lijie
> > > >
> > > > Zakelly Lan  于2022年2月17日周四 12:21写道：
> > > >
> > > > > Congratulations :-D
> > > > >
> > > > > On Thu, Feb 17, 2022 at 12:15 PM Leonard Xu 
> > wrote:
> > > > >
> > > > > > Congratulations !
> > > > > >
> > > > > >
> > > > > > Best,
> > > > > > Leonard
> > > > > >
> > > > > > > 2022年2月17日 上午11:17，Paul Lam  写道：
> > > > > > >
> > > > > > > Congrats! Well deserved!
> > > > > > >
> > > > > > > Best,
> > > > > > > Paul Lam
> > > > > > >
> > > > > > >> 2022年2月16日 21:30，Robert Metzger  写道：
> > > > > > >>
> > > > > > >> Hi everyone,
> > > > > > >>
> > > > > > >> On behalf of the PMC, I'm very happy to announce two new Flink
> > > > > > >> committers: Feng Wang and Zhipeng Zhang!
> > > > > > >>
> > > > > > >> Feng is one of the most active Flink evangelists in China,
> with
> > > > plenty
> > > > > > of
> > > > > > >> public talks, blog posts and other evangelization activities.
> > The
> > > > PMC
> > > > > > wants
> > > > > > >> to recognize and value these efforts by making Feng a
> committer!
> > > > > > >>
> > > > > > >> Zhipeng Zhang has made significant contributions to flink-ml,
> > like
> > > > > most
> > > > > > of
> > > > > > >> the FLIPs for our ML efforts.
> > > > > > >>
> > > > > > >> Please join me in welcoming them as committers!
> > > > > > >>
> > > > > > >>
> > > > > > >> Best,
> > > > > > >> Robert
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Yuan Mei]

Congratulations!

Best Regards,
Yuan

On Thu, Feb 17, 2022 at 5:17 PM Aitozi  wrote:

> Congratulations!
>
> Best,
> Aitozi
>
>
> Guowei Ma  于2022年2月17日周四 15:53写道：
>
> > Congratulations
> >
> > Best,
> > Guowei
> >
> >
> > On Thu, Feb 17, 2022 at 3:29 PM Yang Wang  wrote:
> >
> > > Congratulations to all of you!
> > >
> > > Best,
> > > Yang
> > >
> > > Lijie Wang  于2022年2月17日周四 14:20写道：
> > >
> > > > Congratulations to all of you!
> > > >
> > > > Best,
> > > > Lijie
> > > >
> > > > Leonard Xu  于2022年2月17日周四 12:13写道：
> > > >
> > > > > Congratulations !
> > > > >
> > > > > Best,
> > > > > Leonard
> > > > >
> > > > > > 2022年2月17日 上午11:09，Yun Tang  写道：
> > > > > >
> > > > > > Congratulations to all of you!
> > > > > >
> > > > > > Best,
> > > > > > Yun Tang
> > > > > > 
> > > > > > From: Yangze Guo 
> > > > > > Sent: Thursday, February 17, 2022 10:44
> > > > > > To: dev 
> > > > > > Cc: ro...@apache.org 
> > > > > > Subject: Re: [ANNOUNCE] New Flink PMC members: Igal Shilman,
> > > Konstantin
> > > > > Knauf and Yun Gao
> > > > > >
> > > > > > Congratulations! Well deserved.
> > > > > >
> > > > > > Best,
> > > > > > Yangze Guo
> > > > > >
> > > > > > On Thu, Feb 17, 2022 at 10:15 AM Paul Lam  >
> > > > wrote:
> > > > > >>
> > > > > >> Congrats to all of you!
> > > > > >>
> > > > > >> Best,
> > > > > >> Paul Lam
> > > > > >>
> > > > > >>> 2022年2月17日 01:24，Roman Khachatryan  写道：
> > > > > >>>
> > > > > >>> Congratulations!
> > > > > >>>
> > > > > >>> Regards,
> > > > > >>> Roman
> > > > > >>>
> > > > > >>> On Wed, Feb 16, 2022 at 5:22 PM Matthias Pohl <
> > > > matth...@ververica.com>
> > > > > wrote:
> > > > > 
> > > > >  Congratulations to all of you :)
> > > > > 
> > > > >  On Wed, Feb 16, 2022 at 4:04 PM Till Rohrmann <
> > > trohrm...@apache.org
> > > > >
> > > > > wrote:
> > > > > 
> > > > > > Congratulations! Well deserved!
> > > > > >
> > > > > > Cheers,
> > > > > > Till
> > > > > >
> > > > > > On Wed, Feb 16, 2022 at 2:51 PM Martijn Visser <
> > > > > mart...@ververica.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Congratulations to all of you!
> > > > > >>
> > > > > >> Best regards,
> > > > > >>
> > > > > >> Martijn Visser
> > > > > >> https://twitter.com/MartijnVisser82
> > > > > >>
> > > > > >>
> > > > > >> On Wed, 16 Feb 2022 at 14:29, Fabian Paul  >
> > > > wrote:
> > > > > >>
> > > > > >>> Congrats to all three of you, well deserved.
> > > > > >>>
> > > > > >>> Best,
> > > > > >>> Fabian
> > > > > >>>
> > > > > >>> On Wed, Feb 16, 2022 at 2:23 PM Robert Metzger <
> > > > > rmetz...@apache.org>
> > > > > >>> wrote:
> > > > > 
> > > > >  Hi all,
> > > > > 
> > > > >  I would like to formally announce a few new Flink PMC
> > members
> > > on
> > > > > the
> > > > > >> dev@
> > > > >  list. The PMC has not done a good job of always announcing
> > new
> > > > PMC
> > > > > >>> members
> > > > >  (and committers) recently. I'll try to keep an eye on this
> > in
> > > > the
> > > > > >> future
> > > > > >>> to
> > > > >  improve the situation.
> > > > > 
> > > > >  Nevertheless, I'm very happy to announce some very active
> > > > > community
> > > > > >>> members
> > > > >  as new PMC members:
> > > > > 
> > > > >  - Igal Shilman, added to the PMC in October 2021
> > > > >  - Konstantin Knauf, added to the PMC in January 2022
> > > > >  - Yun Gao, added to the PMC in February 2022
> > > > > 
> > > > >  Please join me in welcoming them to the Flink PMC!
> > > > > 
> > > > >  Best,
> > > > >  Robert
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Created] (FLINK-26214) Publish Kubernetes operator to container registry

[Zili Chen (Jira)]

Zili Chen created FLINK-26214:
-

 Summary: Publish Kubernetes operator to container registry
 Key: FLINK-26214
 URL: https://issues.apache.org/jira/browse/FLINK-26214
 Project: Flink
  Issue Type: Sub-task
Reporter: Zili Chen


Created from 
https://github.com/apache/flink-kubernetes-operator/pull/4#issuecomment-1042717476.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Johannes Moser]

👏

> On 17.02.2022, at 10:19, Yuan Mei  wrote:
> 
> Congratulations!
> 
> Best Regards,
> Yuan
> 
> On Thu, Feb 17, 2022 at 5:17 PM Aitozi  wrote:
> 
>> Congratulations!
>> 
>> Best,
>> Aitozi
>> 
>> 
>> Guowei Ma  于2022年2月17日周四 15:53写道：
>> 
>>> Congratulations
>>> 
>>> Best,
>>> Guowei
>>> 
>>> 
>>> On Thu, Feb 17, 2022 at 3:29 PM Yang Wang  wrote:
>>> 
 Congratulations to all of you!
 
 Best,
 Yang
 
 Lijie Wang  于2022年2月17日周四 14:20写道：
 
> Congratulations to all of you!
> 
> Best,
> Lijie
> 
> Leonard Xu  于2022年2月17日周四 12:13写道：
> 
>> Congratulations !
>> 
>> Best,
>> Leonard
>> 
>>> 2022年2月17日 上午11:09，Yun Tang  写道：
>>> 
>>> Congratulations to all of you!
>>> 
>>> Best,
>>> Yun Tang
>>> 
>>> From: Yangze Guo 
>>> Sent: Thursday, February 17, 2022 10:44
>>> To: dev 
>>> Cc: ro...@apache.org 
>>> Subject: Re: [ANNOUNCE] New Flink PMC members: Igal Shilman,
 Konstantin
>> Knauf and Yun Gao
>>> 
>>> Congratulations! Well deserved.
>>> 
>>> Best,
>>> Yangze Guo
>>> 
>>> On Thu, Feb 17, 2022 at 10:15 AM Paul Lam >> 
> wrote:
 
 Congrats to all of you!
 
 Best,
 Paul Lam
 
> 2022年2月17日 01:24，Roman Khachatryan  写道：
> 
> Congratulations!
> 
> Regards,
> Roman
> 
> On Wed, Feb 16, 2022 at 5:22 PM Matthias Pohl <
> matth...@ververica.com>
>> wrote:
>> 
>> Congratulations to all of you :)
>> 
>> On Wed, Feb 16, 2022 at 4:04 PM Till Rohrmann <
 trohrm...@apache.org
>> 
>> wrote:
>> 
>>> Congratulations! Well deserved!
>>> 
>>> Cheers,
>>> Till
>>> 
>>> On Wed, Feb 16, 2022 at 2:51 PM Martijn Visser <
>> mart...@ververica.com>
>>> wrote:
>>> 
 Congratulations to all of you!
 
 Best regards,
 
 Martijn Visser
 https://twitter.com/MartijnVisser82
 
 
 On Wed, 16 Feb 2022 at 14:29, Fabian Paul >> 
> wrote:
 
> Congrats to all three of you, well deserved.
> 
> Best,
> Fabian
> 
> On Wed, Feb 16, 2022 at 2:23 PM Robert Metzger <
>> rmetz...@apache.org>
> wrote:
>> 
>> Hi all,
>> 
>> I would like to formally announce a few new Flink PMC
>>> members
 on
>> the
 dev@
>> list. The PMC has not done a good job of always announcing
>>> new
> PMC
> members
>> (and committers) recently. I'll try to keep an eye on this
>>> in
> the
 future
> to
>> improve the situation.
>> 
>> Nevertheless, I'm very happy to announce some very active
>> community
> members
>> as new PMC members:
>> 
>> - Igal Shilman, added to the PMC in October 2021
>> - Konstantin Knauf, added to the PMC in January 2022
>> - Yun Gao, added to the PMC in February 2022
>> 
>> Please join me in welcoming them to the Flink PMC!
>> 
>> Best,
>> Robert
> 
 
 
>> 
>> 
> 
 
>>> 
>> 

Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Dian Fu]

Congratulations!

Regards,
Dian

On Thu, Feb 17, 2022 at 5:18 PM Yuan Mei  wrote:

> Congratulations!
>
> Best Regards,
> Yuan
>
> On Thu, Feb 17, 2022 at 5:15 PM Aitozi  wrote:
>
> > Congratulations!
> >
> > Best,
> > Aitozi
> >
> > Guowei Ma  于2022年2月17日周四 15:52写道：
> >
> > > Congratulations to Feng and Zhipeng!
> > > Best,
> > > Guowei
> > >
> > >
> > > On Thu, Feb 17, 2022 at 3:30 PM Yang Wang 
> wrote:
> > >
> > > > Congratulations!
> > > >
> > > > Best,
> > > > Yang
> > > >
> > > > Lijie Wang  于2022年2月17日周四 14:21写道：
> > > >
> > > > > Congratulations to all of you!
> > > > >
> > > > > Best,
> > > > > Lijie
> > > > >
> > > > > Zakelly Lan  于2022年2月17日周四 12:21写道：
> > > > >
> > > > > > Congratulations :-D
> > > > > >
> > > > > > On Thu, Feb 17, 2022 at 12:15 PM Leonard Xu 
> > > wrote:
> > > > > >
> > > > > > > Congratulations !
> > > > > > >
> > > > > > >
> > > > > > > Best,
> > > > > > > Leonard
> > > > > > >
> > > > > > > > 2022年2月17日 上午11:17，Paul Lam  写道：
> > > > > > > >
> > > > > > > > Congrats! Well deserved!
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Paul Lam
> > > > > > > >
> > > > > > > >> 2022年2月16日 21:30，Robert Metzger  写道：
> > > > > > > >>
> > > > > > > >> Hi everyone,
> > > > > > > >>
> > > > > > > >> On behalf of the PMC, I'm very happy to announce two new
> Flink
> > > > > > > >> committers: Feng Wang and Zhipeng Zhang!
> > > > > > > >>
> > > > > > > >> Feng is one of the most active Flink evangelists in China,
> > with
> > > > > plenty
> > > > > > > of
> > > > > > > >> public talks, blog posts and other evangelization
> activities.
> > > The
> > > > > PMC
> > > > > > > wants
> > > > > > > >> to recognize and value these efforts by making Feng a
> > committer!
> > > > > > > >>
> > > > > > > >> Zhipeng Zhang has made significant contributions to
> flink-ml,
> > > like
> > > > > > most
> > > > > > > of
> > > > > > > >> the FLIPs for our ML efforts.
> > > > > > > >>
> > > > > > > >> Please join me in welcoming them as committers!
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> Best,
> > > > > > > >> Robert
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Dian Fu]

Congratulations!

Regards,
Dian

On Thu, Feb 17, 2022 at 6:54 PM Johannes Moser  wrote:

> 👏
>
> > On 17.02.2022, at 10:19, Yuan Mei  wrote:
> >
> > Congratulations!
> >
> > Best Regards,
> > Yuan
> >
> > On Thu, Feb 17, 2022 at 5:17 PM Aitozi  wrote:
> >
> >> Congratulations!
> >>
> >> Best,
> >> Aitozi
> >>
> >>
> >> Guowei Ma  于2022年2月17日周四 15:53写道：
> >>
> >>> Congratulations
> >>>
> >>> Best,
> >>> Guowei
> >>>
> >>>
> >>> On Thu, Feb 17, 2022 at 3:29 PM Yang Wang 
> wrote:
> >>>
>  Congratulations to all of you!
> 
>  Best,
>  Yang
> 
>  Lijie Wang  于2022年2月17日周四 14:20写道：
> 
> > Congratulations to all of you!
> >
> > Best,
> > Lijie
> >
> > Leonard Xu  于2022年2月17日周四 12:13写道：
> >
> >> Congratulations !
> >>
> >> Best,
> >> Leonard
> >>
> >>> 2022年2月17日 上午11:09，Yun Tang  写道：
> >>>
> >>> Congratulations to all of you!
> >>>
> >>> Best,
> >>> Yun Tang
> >>> 
> >>> From: Yangze Guo 
> >>> Sent: Thursday, February 17, 2022 10:44
> >>> To: dev 
> >>> Cc: ro...@apache.org 
> >>> Subject: Re: [ANNOUNCE] New Flink PMC members: Igal Shilman,
>  Konstantin
> >> Knauf and Yun Gao
> >>>
> >>> Congratulations! Well deserved.
> >>>
> >>> Best,
> >>> Yangze Guo
> >>>
> >>> On Thu, Feb 17, 2022 at 10:15 AM Paul Lam  >>>
> > wrote:
> 
>  Congrats to all of you!
> 
>  Best,
>  Paul Lam
> 
> > 2022年2月17日 01:24，Roman Khachatryan  写道：
> >
> > Congratulations!
> >
> > Regards,
> > Roman
> >
> > On Wed, Feb 16, 2022 at 5:22 PM Matthias Pohl <
> > matth...@ververica.com>
> >> wrote:
> >>
> >> Congratulations to all of you :)
> >>
> >> On Wed, Feb 16, 2022 at 4:04 PM Till Rohrmann <
>  trohrm...@apache.org
> >>
> >> wrote:
> >>
> >>> Congratulations! Well deserved!
> >>>
> >>> Cheers,
> >>> Till
> >>>
> >>> On Wed, Feb 16, 2022 at 2:51 PM Martijn Visser <
> >> mart...@ververica.com>
> >>> wrote:
> >>>
>  Congratulations to all of you!
> 
>  Best regards,
> 
>  Martijn Visser
>  https://twitter.com/MartijnVisser82
> 
> 
>  On Wed, 16 Feb 2022 at 14:29, Fabian Paul  >>>
> > wrote:
> 
> > Congrats to all three of you, well deserved.
> >
> > Best,
> > Fabian
> >
> > On Wed, Feb 16, 2022 at 2:23 PM Robert Metzger <
> >> rmetz...@apache.org>
> > wrote:
> >>
> >> Hi all,
> >>
> >> I would like to formally announce a few new Flink PMC
> >>> members
>  on
> >> the
>  dev@
> >> list. The PMC has not done a good job of always announcing
> >>> new
> > PMC
> > members
> >> (and committers) recently. I'll try to keep an eye on this
> >>> in
> > the
>  future
> > to
> >> improve the situation.
> >>
> >> Nevertheless, I'm very happy to announce some very active
> >> community
> > members
> >> as new PMC members:
> >>
> >> - Igal Shilman, added to the PMC in October 2021
> >> - Konstantin Knauf, added to the PMC in January 2022
> >> - Yun Gao, added to the PMC in February 2022
> >>
> >> Please join me in welcoming them to the Flink PMC!
> >>
> >> Best,
> >> Robert
> >
> 
> 
> >>
> >>
> >
> 
> >>>
> >>
>
>

[jira] [Created] (FLINK-26215) [JUnit5 Migration] Module: flink-metrics-statsd

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26215:


 Summary: [JUnit5 Migration] Module: flink-metrics-statsd
 Key: FLINK-26215
 URL: https://issues.apache.org/jira/browse/FLINK-26215
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26216) Make 'replicas' work in JobManager Spec

[Biao Geng (Jira)]

Biao Geng created FLINK-26216:
-

 Summary: Make 'replicas' work in JobManager Spec
 Key: FLINK-26216
 URL: https://issues.apache.org/jira/browse/FLINK-26216
 Project: Flink
  Issue Type: Bug
  Components: Kubernetes Operator
Reporter: Biao Geng


In our flink kubernetes operator's cr, we allow users to set the replica of 
JobManager. 
But in our {{FlinkUtils#getEffectiveConfig}} method, we currently not set this 
value from the yaml file and as a result, the {{replicas}} will not work and 
the default value(i.e. 1) will be applied. 
Though we believe one JM with KubernetesHaService should be enough for most HA 
cases, the {{replicas}} field of JM also makes sense since more than one JM can 
reduce down time and make recovery of JM failure faster. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26217) Introduce manifest.merge-min-count in commit

[Jingsong Lee (Jira)]

Jingsong Lee created FLINK-26217:


 Summary: Introduce manifest.merge-min-count in commit
 Key: FLINK-26217
 URL: https://issues.apache.org/jira/browse/FLINK-26217
 Project: Flink
  Issue Type: Sub-task
  Components: Table Store
Reporter: Jingsong Lee
 Fix For: table-store-0.1.0


To avoid frequent manifest merges, this parameter is introduced to control the 
number of merges.

- manifest.merge-min-count: default value can be 30



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26218) Enable JUnit 5 Automatic Extension Detection

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26218:


 Summary: Enable JUnit 5 Automatic Extension Detection
 Key: FLINK-26218
 URL: https://issues.apache.org/jira/browse/FLINK-26218
 Project: Flink
  Issue Type: Improvement
  Components: Tests
Affects Versions: 1.15.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0


This allows us to declare the TestLoggerExtension for all tests in a module via 
the service entry.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26219) [JUnit5 Migration] Module: flink-metrics-slf4j

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26219:


 Summary: [JUnit5 Migration] Module: flink-metrics-slf4j
 Key: FLINK-26219
 URL: https://issues.apache.org/jira/browse/FLINK-26219
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Jinzhong Li]

Congratulations!


Best,

Jinzhong

Robert Metzger  于2022年2月16日周三 21:32写道：

> Hi everyone,
>
> On behalf of the PMC, I'm very happy to announce two new Flink
> committers: Feng Wang and Zhipeng Zhang!
>
> Feng is one of the most active Flink evangelists in China, with plenty of
> public talks, blog posts and other evangelization activities. The PMC wants
> to recognize and value these efforts by making Feng a committer!
>
> Zhipeng Zhang has made significant contributions to flink-ml, like most of
> the FLIPs for our ML efforts.
>
> Please join me in welcoming them as committers!
>
>
> Best,
> Robert
>

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Jinzhong Li]

Congratulations!


Best,

Jinzhong

On Wed, Feb 16, 2022 at 9:23 PM Robert Metzger  wrote:

> Hi all,
>
> I would like to formally announce a few new Flink PMC members on the dev@
> list. The PMC has not done a good job of always announcing new PMC members
> (and committers) recently. I'll try to keep an eye on this in the future to
> improve the situation.
>
> Nevertheless, I'm very happy to announce some very active community members
> as new PMC members:
>
> - Igal Shilman, added to the PMC in October 2021
> - Konstantin Knauf, added to the PMC in January 2022
> - Yun Gao, added to the PMC in February 2022
>
> Please join me in welcoming them to the Flink PMC!
>
> Best,
> Robert
>

[DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

[Robert Metzger]

Hi all,

Some time ago, we added this "Automated Checks / Review Progress" [1] bot
to the Flink PRs. I'm not aware of anybody using it, and I'm also not sure
if it still works properly.

Therefore, I propose to disable this bot. Please let me know if you
disagree, otherwise, I'll soon disable it.


Best,
Robert


[1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516

[jira] [Created] (FLINK-26220) KafkaSourceITCase$KafkaSpecificTests.testTimestamp fails on Azure Pipelines

[Alexander Preuss (Jira)]

Alexander Preuss created FLINK-26220:


 Summary: KafkaSourceITCase$KafkaSpecificTests.testTimestamp fails 
on Azure Pipelines
 Key: FLINK-26220
 URL: https://issues.apache.org/jira/browse/FLINK-26220
 Project: Flink
  Issue Type: Technical Debt
  Components: Connectors / Kafka
Affects Versions: 1.15.0
Reporter: Alexander Preuss


{code:java}
Feb 16 18:10:37 [ERROR] Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time 
elapsed: 60.963 s <<< FAILURE! - in 
org.apache.flink.connector.kafka.source.KafkaSourceITCase$KafkaSpecificTests
Feb 16 18:10:37 [ERROR] 
org.apache.flink.connector.kafka.source.KafkaSourceITCase$KafkaSpecificTests.testTimestamp(boolean)[1]
  Time elapsed: 11.21 s  <<< FAILURE!
Feb 16 18:10:37 java.lang.AssertionError: Create test topic : 
testTimestamp-3028462271882246016 failed, The topic metadata failed to 
propagate to Kafka broker.
Feb 16 18:10:37 at org.junit.Assert.fail(Assert.java:89)
Feb 16 18:10:37 at 
org.apache.flink.streaming.connectors.kafka.KafkaTestEnvironmentImpl.createTestTopic(KafkaTestEnvironmentImpl.java:223)
Feb 16 18:10:37 at 
org.apache.flink.streaming.connectors.kafka.KafkaTestEnvironment.createTestTopic(KafkaTestEnvironment.java:98)
Feb 16 18:10:37 at 
org.apache.flink.streaming.connectors.kafka.KafkaTestBase.createTestTopic(KafkaTestBase.java:216)
Feb 16 18:10:37 at 
org.apache.flink.connector.kafka.source.KafkaSourceITCase$KafkaSpecificTests.testTimestamp(KafkaSourceITCase.java:108)
Feb 16 18:10:37 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
Feb 16 18:10:37 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Feb 16 18:10:37 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Feb 16 18:10:37 at java.lang.reflect.Method.invoke(Method.java:498)
 {code}
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31686&view=logs&j=c5f0071e-1851-543e-9a45-9ac140befc32&t=15a22db7-8faa-5b34-3920-d33c9f0ca23c&l=35870



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26221) [JUnit5 Migration] Module: flink-metrics-prometheus

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26221:


 Summary: [JUnit5 Migration] Module: flink-metrics-prometheus
 Key: FLINK-26221
 URL: https://issues.apache.org/jira/browse/FLINK-26221
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

[Konstantin Knauf]

+1

On Thu, Feb 17, 2022 at 1:11 PM Robert Metzger  wrote:

> Hi all,
>
> Some time ago, we added this "Automated Checks / Review Progress" [1] bot
> to the Flink PRs. I'm not aware of anybody using it, and I'm also not sure
> if it still works properly.
>
> Therefore, I propose to disable this bot. Please let me know if you
> disagree, otherwise, I'll soon disable it.
>
>
> Best,
> Robert
>
>
> [1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516
>


-- 

Konstantin Knauf

https://twitter.com/snntrable

https://github.com/knaufk

Re: [DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

[Chesnay Schepler]

+1 to remove it.

On 17/02/2022 13:31, Konstantin Knauf wrote:

+1

On Thu, Feb 17, 2022 at 1:11 PM Robert Metzger  wrote:


Hi all,

Some time ago, we added this "Automated Checks / Review Progress" [1] bot
to the Flink PRs. I'm not aware of anybody using it, and I'm also not sure
if it still works properly.

Therefore, I propose to disable this bot. Please let me know if you
disagree, otherwise, I'll soon disable it.


Best,
Robert


[1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516

Re: [DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

[Martijn Visser]

+1 to remove it

On Thu, 17 Feb 2022 at 13:34, Chesnay Schepler  wrote:

> +1 to remove it.
>
> On 17/02/2022 13:31, Konstantin Knauf wrote:
> > +1
> >
> > On Thu, Feb 17, 2022 at 1:11 PM Robert Metzger 
> wrote:
> >
> >> Hi all,
> >>
> >> Some time ago, we added this "Automated Checks / Review Progress" [1]
> bot
> >> to the Flink PRs. I'm not aware of anybody using it, and I'm also not
> sure
> >> if it still works properly.
> >>
> >> Therefore, I propose to disable this bot. Please let me know if you
> >> disagree, otherwise, I'll soon disable it.
> >>
> >>
> >> Best,
> >> Robert
> >>
> >>
> >> [1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516
> >>
> >
>
>

Re: [DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

[Till Rohrmann]

+1 to remove it.

Cheers,
Till

On Thu, Feb 17, 2022 at 1:42 PM Martijn Visser 
wrote:

> +1 to remove it
>
> On Thu, 17 Feb 2022 at 13:34, Chesnay Schepler  wrote:
>
> > +1 to remove it.
> >
> > On 17/02/2022 13:31, Konstantin Knauf wrote:
> > > +1
> > >
> > > On Thu, Feb 17, 2022 at 1:11 PM Robert Metzger 
> > wrote:
> > >
> > >> Hi all,
> > >>
> > >> Some time ago, we added this "Automated Checks / Review Progress" [1]
> > bot
> > >> to the Flink PRs. I'm not aware of anybody using it, and I'm also not
> > sure
> > >> if it still works properly.
> > >>
> > >> Therefore, I propose to disable this bot. Please let me know if you
> > >> disagree, otherwise, I'll soon disable it.
> > >>
> > >>
> > >> Best,
> > >> Robert
> > >>
> > >>
> > >> [1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516
> > >>
> > >
> >
> >
>

[jira] [Created] (FLINK-26222) Delete outdated documents in "InfluxDB" part of "Metric Reporters" page

[Chengkai Yang (Jira)]

Chengkai Yang created FLINK-26222:
-

 Summary: Delete outdated documents in "InfluxDB" part of "Metric 
Reporters" page
 Key: FLINK-26222
 URL: https://issues.apache.org/jira/browse/FLINK-26222
 Project: Flink
  Issue Type: Improvement
Reporter: Chengkai Yang


In this 
[part|[https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/metric_reporters/#influxdb]|https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/metric_reporters/#influxdb],we]

we should remove this line:"In order to use this reporter you must copy 
{{/opt/flink-metrics-influxdb-1.14.3.jar}} into the {{plugins/influxdb}} folder 
of your Flink distribution." since the jar is  already under 
plugins/metrics-influx/ folder.

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26223) Making ZK-related logs available in tests

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-26223:
-

 Summary: Making ZK-related logs available in tests
 Key: FLINK-26223
 URL: https://issues.apache.org/jira/browse/FLINK-26223
 Project: Flink
  Issue Type: Improvement
  Components: Runtime / Coordination
Affects Versions: 1.15.0, 1.16.0
Reporter: Matthias Pohl


Recently, we had a few incidents where it appears that ZooKeeper wasn't 
behaving as expected. It might help to have to the ZooKeeper logs available in 
these cases.

We have multiple options:
 * Introduce an extension to change the ZK log level for specific tests
 * Lower the ZK log level again and make the logs being written to the standard 
log files
 * Lower the ZK log level again and move the ZK logs into a dedicated file to 
avoid spoiling the Flink logs



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] Flink 1.15 Feature Freeze

[wenlong.lwl]

Hi,all, I want to merge a pr (https://github.com/apache/flink/pull/18363)
belonging to FLIP-190, which was approved yesterday, but not merged before
code freeze because of CI queueing and failed by other changes.
WDYT?

Best,
Wenlong

On Thu, 17 Feb 2022 at 02:08, Till Rohrmann  wrote:

> Hi everyone,
>
> The deadline for merging new features for Flink 1.15 has passed.
>
> * From now on, only bug-fixes and documentation fixes / improvements are
> allowed to be merged into the master branch.
>
> * New features merged after this point can be reverted. If you need an
> exception to this rule, please open a discussion on dev@ list and reach
> out
> to us.
>
> We plan to wait for the master branch to get a bit more stabilized before
> cutting the "release-1.15" branch, in order to reduce the overhead of
> having to manage two branches. That also means potentially delaying merging
> new features for Flink 1.16 into the master branch. If you are blocked on
> this, please let us know and we can come up with a compromise for the
> branch cutting time.
>
> What you can do to help with the release testing phase:
>
> * The first release testing sync will be on *February 22, 9am CET*.
> Everyone is welcome to join. The link can be found on the release wiki page
> [1].
>
> * Please prepare for the release testing by creating Jira tickets for
> documentation and testing tasks for the new features. Tickets should be
> opened with Priority Blocker, FixVersion 1.15.0 and Label release-testing
> (testing tasks only).
>
> * There are currently 92 test-stability issues affecting the 1.15.0 release
> [2]. It is greatly appreciated if you can help address some of them.
>
> Cheers,
> Joe, Yun & Till
>
> [1] https://cwiki.apache.org/confluence/display/FLINK/1.15+Release
> [2] https://issues.apache.org/jira/issues/?filter=12351363
>

[jira] [Created] (FLINK-26224) HAJobRunOnHadoopS3FileSystemITCase fails with UnsupportedFileSystemSchemeException

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-26224:
-

 Summary: HAJobRunOnHadoopS3FileSystemITCase fails with 
UnsupportedFileSystemSchemeException
 Key: FLINK-26224
 URL: https://issues.apache.org/jira/browse/FLINK-26224
 Project: Flink
  Issue Type: Improvement
  Components: Connectors / FileSystem
Affects Versions: 1.15.0
Reporter: Matthias Pohl


We're observing occassional errors in a Flink fork based on {{master}} in 
{{HAJobRunOnHadoopS3FileSystemITCase}} where the Hadoop S3 FileSystem wasn't 
loaded properly causing the {{UnsupportedFileSystemSchemeException}}:
{code}
Feb 16 19:02:52 [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time 
elapsed: 7.391 s <<< FAILURE! - in 
org.apache.flink.fs.s3hadoop.HAJobRunOnHadoopS3FileSystemITCase
Feb 16 19:02:52 [ERROR] 
org.apache.flink.fs.s3hadoop.HAJobRunOnHadoopS3FileSystemITCase.testJobExecutionInHaMode
  Time elapsed: 1.89 s  <<< ERROR!
Feb 16 19:02:52 java.io.IOException: Could not create FileSystem for highly 
available storage path (s3://bucket-cqycdk/test-cluster/default)
Feb 16 19:02:52 at 
org.apache.flink.runtime.blob.BlobUtils.createFileSystemBlobStore(BlobUtils.java:102)
Feb 16 19:02:52 at 
org.apache.flink.runtime.blob.BlobUtils.createBlobStoreFromConfig(BlobUtils.java:86)
Feb 16 19:02:52 at 
org.apache.flink.runtime.highavailability.HighAvailabilityServicesUtils.createZooKeeperHaServices(HighAvailabilityServicesUtils.java:87)
Feb 16 19:02:52 at 
org.apache.flink.runtime.highavailability.HighAvailabilityServicesUtils.createAvailableOrEmbeddedServices(HighAvailabilityServicesUtils.java:70)
Feb 16 19:02:52 at 
org.apache.flink.runtime.minicluster.MiniCluster.createHighAvailabilityServices(MiniCluster.java:549)
Feb 16 19:02:52 at 
org.apache.flink.runtime.minicluster.MiniCluster.start(MiniCluster.java:397)
Feb 16 19:02:52 at 
org.apache.flink.runtime.testutils.MiniClusterResource.startMiniCluster(MiniClusterResource.java:245)
Feb 16 19:02:52 at 
org.apache.flink.runtime.testutils.MiniClusterResource.before(MiniClusterResource.java:105)
Feb 16 19:02:52 at 
org.apache.flink.runtime.testutils.MiniClusterExtension.before(MiniClusterExtension.java:56)
Feb 16 19:02:52 at 
org.apache.flink.core.testutils.EachCallbackWrapper.beforeEach(EachCallbackWrapper.java:45)
Feb 16 19:02:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeEachCallbacks$2(TestMethodTestDescriptor.java:163)
Feb 16 19:02:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$6(TestMethodTestDescriptor.java:199)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
Feb 16 19:02:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:199)
Feb 16 19:02:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeEachCallbacks(TestMethodTestDescriptor.java:162)
Feb 16 19:02:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:129)
Feb 16 19:02:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:66)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
Feb 16 19:02:52 at java.util.ArrayList.forEach(ArrayList.java:1259)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:41)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:155)
Feb 16 19:02:52 at 
org.junit.platform.engine.support.hie

Re: Re: [DISCUSS] Future of Per-Job Mode

[Jark Wu]

Hi Yang,

It would be better to have an interface to submitting application mode
jobs. It's a little tricky for SQL CLI/Gateway process to invoke a shell
script to submit jobs.

Best,
Jark

On Thu, 17 Feb 2022 at 15:20, Yang Wang  wrote:

> I am not sure whether the sql script could also be submitted like python.
> We will need a sql-runner jar, which plays as the user jar and has the sql
> script as the argument.
>
> ./bin/flink run-application \  --target kubernetes-application \
>-Dkubernetes.cluster-id= \
> -Dkubernetes.container.image= \  --sqlFiles
> /opt/flink/examples/sql/word_count.sql
>
> Best,
> Yang
>
> Jark Wu  于2022年2月16日周三 20:00写道：
>
> > I think this mode is still limited and maybe not easy to extend.
> > Could the application mode provide an interface to execute?
> > So that clients can implement the interface and pass arbitrary parameters
> > (e.g. SQL scripts) ?
> >
> > Best,
> > Jark
> >
> > On Wed, 16 Feb 2022 at 18:54, Konstantin Knauf 
> wrote:
> >
> > > Hi Jark,
> > >
> > > I think you are raising a very good point. I think we need an
> application
> > > mode for SQL that would work along the lines of executing a SQL script
> > > (incl. init scripts) located in a particular directory in the Docker
> > Image.
> > > Details to be discussed.
> > >
> > > Do you think Zeppelin/SQL CLI could work with such a mode for
> > > non-interactive queries (interactive queries would use a session
> > cluster)?
> > >
> > > Best,
> > >
> > > Konstantin
> > >
> > >
> > > On Sat, Feb 12, 2022 at 4:31 AM Jark Wu  wrote:
> > >
> > > > Hi David,
> > > >
> > > > Zeppelin and SQL CLI also support submitting long-running streaming
> SQL
> > > > jobs. So the session cluster is not a fit mode.
> > > >
> > > > Best,
> > > > Jark
> > > >
> > > > On Fri, 11 Feb 2022 at 22:42, David Morávek  wrote:
> > > >
> > > > > Hi Jark, can you please elaborate about the current need of the
> > per-job
> > > > > mode for interactive clients (eg. Zeppelin that you've mentioned)?
> > > Aren't
> > > > > these a natural fit for the session cluster?
> > > > >
> > > > > D.
> > > > >
> > > > > On Fri, Feb 11, 2022 at 3:25 PM Jark Wu  wrote:
> > > > >
> > > > > > Hi Konstantin,
> > > > > >
> > > > > > I'm not very familiar with the implementation of per-job mode and
> > > > > > application mode.
> > > > > > But is there any instruction for users abou how to migrate
> > > > platforms/jobs
> > > > > > to application mode?
> > > > > > IIUC, the biggest difference between the two modes is where the
> > > main()
> > > > > > method is executed.
> > > > > > However, SQL jobs are not jar applications and don't have the
> > main()
> > > > > > method.
> > > > > > For example, SQL CLI submits SQL jobs by invoking
> > > > > > `StreamExecutionEnvironment#executeAsync(StreamGraph)`.
> > > > > > How SQL Client and SQL platforms (e.g. Zeppelin) support
> > application
> > > > > mode?
> > > > > >
> > > > > > Best,
> > > > > > Jark
> > > > > >
> > > > > >
> > > > > > On Fri, 28 Jan 2022 at 23:33, Konstantin Knauf <
> kna...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > Thank you for sharing your perspectives. I was not aware of
> > > > > > > these limitations of per-job mode on YARN. It seems that there
> > is a
> > > > > > general
> > > > > > > agreement to deprecate per-job mode and to drop it once the
> > > > limitations
> > > > > > > around YARN are resolved. I've started a corresponding vote in
> > [1].
> > > > > > >
> > > > > > > Thanks again,
> > > > > > >
> > > > > > > Konstantin
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/v6oz92dfp95qcox45l0f8393089oyjv4
> > > > > > >
> > > > > > > On Fri, Jan 28, 2022 at 1:53 PM Ferenc Csaky
> > > > >  > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Yang,
> > > > > > > >
> > > > > > > > Thank you for the clarification. In general I think we will
> > have
> > > > time
> > > > > > to
> > > > > > > > experiment with this until it will be removed totally and
> > migrate
> > > > our
> > > > > > > > solution to use application mode.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > F
> > > > > > > >
> > > > > > > > On 2022/01/26 02:42:24 Yang Wang wrote:
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > I remember the application mode was initially named
> "cluster
> > > > mode".
> > > > > > As
> > > > > > > a
> > > > > > > > > contrast, the per-job mode is the "client mode".
> > > > > > > > > So I believe application mode should cover all the
> > > > functionalities
> > > > > of
> > > > > > > > > per-job except where we are running the user main code.
> > > > > > > > > In the containerized or the Kubernetes world, the
> application
> > > > mode
> > > > > is
> > > > > > > > more
> > > > > > > > > native and easy to use since all the Flink and user
> > > > > > > > > jars are bundled in the image. I am also in favor of
> > > deprecating
> > > > > and
> > > > > > > > > removing the

[jira] [Created] (FLINK-26225) [JUnit5 Migration] Module: flink-metrics-jmx

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26225:


 Summary: [JUnit5 Migration] Module: flink-metrics-jmx
 Key: FLINK-26225
 URL: https://issues.apache.org/jira/browse/FLINK-26225
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26226) [JUnit5 Migration] Module: flink-metrics-influxdb

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26226:


 Summary: [JUnit5 Migration] Module: flink-metrics-influxdb
 Key: FLINK-26226
 URL: https://issues.apache.org/jira/browse/FLINK-26226
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26227) [JUnit5 Migration] Module: flink-metrics-graphite

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26227:


 Summary: [JUnit5 Migration] Module: flink-metrics-graphite
 Key: FLINK-26227
 URL: https://issues.apache.org/jira/browse/FLINK-26227
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26228) [JUnit5 Migration] Module: flink-metrics-dropwizard

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26228:


 Summary: [JUnit5 Migration] Module: flink-metrics-dropwizard
 Key: FLINK-26228
 URL: https://issues.apache.org/jira/browse/FLINK-26228
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26229) [JUnit5 Migration] Module: flink-metrics-datadog

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26229:


 Summary: [JUnit5 Migration] Module: flink-metrics-datadog
 Key: FLINK-26229
 URL: https://issues.apache.org/jira/browse/FLINK-26229
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26230) [JUnit5 Migration] Module: flink-metrics-core

[Chesnay Schepler (Jira)]

Chesnay Schepler created FLINK-26230:


 Summary: [JUnit5 Migration] Module: flink-metrics-core
 Key: FLINK-26230
 URL: https://issues.apache.org/jira/browse/FLINK-26230
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Metrics, Tests
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26231) [Changelog] Incorrect MaterializationID passed to ChangelogStateBackendHandleImpl

[Roman Khachatryan (Jira)]

Roman Khachatryan created FLINK-26231:
-

 Summary: [Changelog] Incorrect MaterializationID passed to 
ChangelogStateBackendHandleImpl
 Key: FLINK-26231
 URL: https://issues.apache.org/jira/browse/FLINK-26231
 Project: Flink
  Issue Type: Bug
  Components: Runtime / State Backends
Affects Versions: 1.15.0
Reporter: Roman Khachatryan
Assignee: Roman Khachatryan
 Fix For: 1.15.0


In ChangelogStateBackendHandleImpl constructor, materializationID and 
persistedSizeOfThisCheckpoint are mixed up.

 

cc: [~yunta]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26232) [JUnit5 Migration] Module: flink-avro

[Ryan Skraba (Jira)]

Ryan Skraba created FLINK-26232:
---

 Summary: [JUnit5 Migration] Module: flink-avro
 Key: FLINK-26232
 URL: https://issues.apache.org/jira/browse/FLINK-26232
 Project: Flink
  Issue Type: Sub-task
Reporter: Ryan Skraba






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: question about StatefunContext in golang Statefun SDK

[Galen Warren]

Thanks for the quick reply!

What I'm trying to do is put some things into the context so that they're
available in downstream calls, perhaps in methods with pointer receivers to
the function struct (MyFunc) but also perhaps in methods that are further
downstream that don't have access to MyFunc. If I'm understanding
correctly, your proposal would work for the former but not the latter.

An example would be to put a configured Logger into the context via a
WithLogger method (logging package - knative.dev/pkg/logging - pkg.go.dev
) and then pull it
out downstream via FromContext (logging package - knative.dev/pkg/logging -
pkg.go.dev ).




On Wed, Feb 16, 2022 at 5:50 PM Seth Wiesman  wrote:

> Hi Galen,
>
> No, that is not currently supported, the current idiomatic way would be to
> pass those values to the struct implementing the Statefun interface.
>
>
> type MyFunc struct { someRuntimeInfo string } func (m *MyFunc) Invoke(ctx
> statefun.Context, message statefun.Message) error { } func main() { builder
> := statefun.StatefulFunctionsBuilder()
> f := MyFunc { someRuntimeInfo: "runtime-provided" } builder.WithSpec
> (statefun.StatefulFunctionSpec{ FunctionType: statefun.TypeNameFrom(
> "example/my-func"), Function: f })
> http.Handle("/statefun", builder.AsHandler())
> _ = http.ListenAndServe(":8000", nil) }
>
> Would this work for you? Or what is the context (pun intended) you are
> looking for?
>
> Seth
>
> On Wed, Feb 16, 2022 at 4:35 PM Galen Warren 
> wrote:
>
> > When stateful functions are invoked, they are passed an instance of
> > statefun.Context, which wraps the context.Context received by the HTTP
> > request. Is there any way to customize that context.Context to, say, hold
> > custom values, using ctx.WithValue()? I don't see a way but I wanted to
> > ask.
> >
> > If not, would you be interested in a PR to add this functionality? A
> simple
> > way might be to add a property to StatefulFunctionSpec, say:
> >
> > TransformContext func(ctx context.Context) context.Context
> >
> > ... that, if supplied, would be called to create a customized context
> that
> > would be used downstream?
> >
> > Thanks.
> >
>

[jira] [Created] (FLINK-26233) FileSinkCompactionSwitchITCase.testSwitchingCompaction() fails

[Alexander Fedulov (Jira)]

Alexander Fedulov created FLINK-26233:
-

 Summary: FileSinkCompactionSwitchITCase.testSwitchingCompaction() 
fails
 Key: FLINK-26233
 URL: https://issues.apache.org/jira/browse/FLINK-26233
 Project: Flink
  Issue Type: Improvement
  Components: Connectors / FileSystem
Affects Versions: 1.15.0
Reporter: Alexander Fedulov


{code:java}
2022-02-17T20:13:20.2895110Z Feb 17 20:13:20 [INFO] Running 
org.apache.flink.connector.file.sink.writer.FileSinkMigrationITCase
2022-02-17T20:13:40.2160260Z Feb 17 20:13:40 [INFO] Tests run: 2, Failures: 0, 
Errors: 0, Skipped: 0, Time elapsed: 19.905 s - in 
org.apache.flink.connector.file.sink.writer.FileSinkMigrationITCase
2022-02-17T20:13:58.8860609Z Feb 17 20:13:58 [ERROR] Tests run: 2, Failures: 0, 
Errors: 1, Skipped: 0, Time elapsed: 102.488 s <<< FAILURE! - in 
org.apache.flink.connector.file.sink.FileSinkCompactionSwitchITCase
2022-02-17T20:13:58.8864562Z Feb 17 20:13:58 [ERROR] 
FileSinkCompactionSwitchITCase.testSwitchingCompaction  Time elapsed: 37.28 s  
<<< ERROR!
2022-02-17T20:13:58.8865526Z Feb 17 20:13:58 
org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
2022-02-17T20:13:58.8866319Z Feb 17 20:13:58     at 
org.apache.flink.runtime.jobmaster.JobResult.toJobExecutionResult(JobResult.java:144)
2022-02-17T20:13:58.8867102Z Feb 17 20:13:58     at 
org.apache.flink.runtime.minicluster.MiniCluster.executeJobBlocking(MiniCluster.java:934)
2022-02-17T20:13:58.8867985Z Feb 17 20:13:58     at 
org.apache.flink.connector.file.sink.FileSinkCompactionSwitchITCase.testSwitchingCompaction(FileSinkCompactionSwitchITCase.java:175)
[...]
2022-02-17T20:13:58.8919634Z Feb 17 20:13:58 Caused by: 
org.apache.flink.runtime.JobException: Recovery is suppressed by 
NoRestartBackoffTimeStrategy
[...]
2022-02-17T20:13:58.8939468Z Feb 17 20:13:58 Caused by: 
org.apache.flink.util.FlinkRuntimeException: Exceeded checkpoint tolerable 
failure threshold.
2022-02-17T20:13:58.8940119Z Feb 17 20:13:58     at 
org.apache.flink.runtime.checkpoint.CheckpointFailureManager.checkFailureAgainstCounter(CheckpointFailureManager.java:160)
2022-02-17T20:13:58.8940863Z Feb 17 20:13:58     at 
org.apache.flink.runtime.checkpoint.CheckpointFailureManager.handleTaskLevelCheckpointException(CheckpointFailureManager.java:145)
2022-02-17T20:13:58.8941613Z Feb 17 20:13:58     at 
org.apache.flink.runtime.checkpoint.CheckpointFailureManager.handleCheckpointException(CheckpointFailureManager.java:97)
2022-02-17T20:13:58.8942321Z Feb 17 20:13:58     at 
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.abortPendingCheckpoint(CheckpointCoordinator.java:2046)
2022-02-17T20:13:58.8943011Z Feb 17 20:13:58     at 
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.receiveDeclineMessage(CheckpointCoordinator.java:1040)
2022-02-17T20:13:58.8943830Z Feb 17 20:13:58     at 
org.apache.flink.runtime.scheduler.ExecutionGraphHandler.lambda$declineCheckpoint$2(ExecutionGraphHandler.java:103)
2022-02-17T20:13:58.8944567Z Feb 17 20:13:58     at 
org.apache.flink.runtime.scheduler.ExecutionGraphHandler.lambda$processCheckpointCoordinatorMessage$3(ExecutionGraphHandler.java:119)
2022-02-17T20:13:58.8945240Z Feb 17 20:13:58     at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2022-02-17T20:13:58.8945794Z Feb 17 20:13:58     at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2022-02-17T20:13:58.8946276Z Feb 17 20:13:58     at 
java.lang.Thread.run(Thread.java:748)  {code}
https://dev.azure.com/alexanderfedulov/Flink/_build/results?buildId=37&view=logs&j=dafbab6d-4616-5d7b-ee37-3c54e4828fd7&t=e204f081-e6cd-5c04-4f4c-919639b63be9&l=2



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: question about StatefunContext in golang Statefun SDK

[Galen Warren]

Also, a potentially simpler way to support this would be to add a
SetContext method to the statefun.Context interface, and have it assign the
wrapped context. This would not require changes to the function spec, or
anything else, and would be more flexible.

On Thu, Feb 17, 2022 at 1:05 PM Galen Warren 
wrote:

> Thanks for the quick reply!
>
> What I'm trying to do is put some things into the context so that they're
> available in downstream calls, perhaps in methods with pointer receivers to
> the function struct (MyFunc) but also perhaps in methods that are further
> downstream that don't have access to MyFunc. If I'm understanding
> correctly, your proposal would work for the former but not the latter.
>
> An example would be to put a configured Logger into the context via a
> WithLogger method (logging package - knative.dev/pkg/logging - pkg.go.dev
> ) and then pull it
> out downstream via FromContext (logging package - knative.dev/pkg/logging
> - pkg.go.dev ).
>
>
>
>
> On Wed, Feb 16, 2022 at 5:50 PM Seth Wiesman  wrote:
>
>> Hi Galen,
>>
>> No, that is not currently supported, the current idiomatic way would be to
>> pass those values to the struct implementing the Statefun interface.
>>
>>
>> type MyFunc struct { someRuntimeInfo string } func (m *MyFunc) Invoke(ctx
>> statefun.Context, message statefun.Message) error { } func main() {
>> builder
>> := statefun.StatefulFunctionsBuilder()
>> f := MyFunc { someRuntimeInfo: "runtime-provided" } builder.WithSpec
>> (statefun.StatefulFunctionSpec{ FunctionType: statefun.TypeNameFrom(
>> "example/my-func"), Function: f })
>> http.Handle("/statefun", builder.AsHandler())
>> _ = http.ListenAndServe(":8000", nil) }
>>
>> Would this work for you? Or what is the context (pun intended) you are
>> looking for?
>>
>> Seth
>>
>> On Wed, Feb 16, 2022 at 4:35 PM Galen Warren 
>> wrote:
>>
>> > When stateful functions are invoked, they are passed an instance of
>> > statefun.Context, which wraps the context.Context received by the HTTP
>> > request. Is there any way to customize that context.Context to, say,
>> hold
>> > custom values, using ctx.WithValue()? I don't see a way but I wanted to
>> > ask.
>> >
>> > If not, would you be interested in a PR to add this functionality? A
>> simple
>> > way might be to add a property to StatefulFunctionSpec, say:
>> >
>> > TransformContext func(ctx context.Context) context.Context
>> >
>> > ... that, if supplied, would be called to create a customized context
>> that
>> > would be used downstream?
>> >
>> > Thanks.
>> >
>>
>

Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Zhipeng Zhang]

Thank you everyone for the warm welcome!

Best,
Zhipeng

Jinzhong Li  于2022年2月17日周四 19:58写道：

> Congratulations!
>
>
> Best,
>
> Jinzhong
>
> Robert Metzger  于2022年2月16日周三 21:32写道：
>
> > Hi everyone,
> >
> > On behalf of the PMC, I'm very happy to announce two new Flink
> > committers: Feng Wang and Zhipeng Zhang!
> >
> > Feng is one of the most active Flink evangelists in China, with plenty of
> > public talks, blog posts and other evangelization activities. The PMC
> wants
> > to recognize and value these efforts by making Feng a committer!
> >
> > Zhipeng Zhang has made significant contributions to flink-ml, like most
> of
> > the FLIPs for our ML efforts.
> >
> > Please join me in welcoming them as committers!
> >
> >
> > Best,
> > Robert
> >
>


-- 
best,
Zhipeng

[jira] [Created] (FLINK-26234) Start minikube manually to replace external github actions

[Yang Wang (Jira)]

Yang Wang created FLINK-26234:
-

 Summary: Start minikube manually to replace external github actions
 Key: FLINK-26234
 URL: https://issues.apache.org/jira/browse/FLINK-26234
 Project: Flink
  Issue Type: Bug
  Components: Kubernetes Operator
Reporter: Yang Wang


External github actions are not allowed to used in the workflow. So we need to 
start minikube manually instead of relying on the existing actions.
{code:java}
Error: .github#L1medyagh/setup-minikube@master and 
medyagh/setup-minikube@master are not allowed to be used in 
apache/flink-kubernetes-operator. Actions in this workflow must be: within a 
repository owned by apache, created by GitHub, verified in the GitHub 
Marketplace or match the following: 
*/*@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+, 
AdoptOpenJDK/install-jdk@*, 
JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92, 
TobKed/label-when-approved-action@*, actions-cool/issues-helper@*, 
actions-rs/*, al-cheb/configure-pagefile-action@*, 
amannn/action-semantic-pull-request@*, apache/*, 
burrunan/gradle-cache-action@*, bytedeco/javacpp-presets/.github/actions/*, 
chromaui/action@*, codecov/codecov-action@*, conda-incubator/setup-miniconda@*, 
container-tools/kind-action@*, container-tools/microshift-action@*, 
dawidd6/action-download-artifact@*, delaguardo/setup-graalvm@*, 
docker://jekyll/jekyll:*, docker://pandoc/core:2.9, 
eps1lon/actions-label-merge-conflict@*, gau... {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Re: [DISCUSS] Future of Per-Job Mode

[Yang Wang]

Do you mean a new interface just like *ApplicationDeployer* for
flink-jar-application submission?

The *ApplicationDeployer*[1] interface has already been used in the
flink-kubernetes-operator project.

[1].
https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/service/FlinkService.java#L65

Best,
Yang

Jark Wu  于2022年2月17日周四 22:18写道：

> Hi Yang,
>
> It would be better to have an interface to submitting application mode
> jobs. It's a little tricky for SQL CLI/Gateway process to invoke a shell
> script to submit jobs.
>
> Best,
> Jark
>
> On Thu, 17 Feb 2022 at 15:20, Yang Wang  wrote:
>
> > I am not sure whether the sql script could also be submitted like python.
> > We will need a sql-runner jar, which plays as the user jar and has the
> sql
> > script as the argument.
> >
> > ./bin/flink run-application \  --target kubernetes-application \
> >-Dkubernetes.cluster-id= \
> > -Dkubernetes.container.image= \  --sqlFiles
> > /opt/flink/examples/sql/word_count.sql
> >
> > Best,
> > Yang
> >
> > Jark Wu  于2022年2月16日周三 20:00写道：
> >
> > > I think this mode is still limited and maybe not easy to extend.
> > > Could the application mode provide an interface to execute?
> > > So that clients can implement the interface and pass arbitrary
> parameters
> > > (e.g. SQL scripts) ?
> > >
> > > Best,
> > > Jark
> > >
> > > On Wed, 16 Feb 2022 at 18:54, Konstantin Knauf 
> > wrote:
> > >
> > > > Hi Jark,
> > > >
> > > > I think you are raising a very good point. I think we need an
> > application
> > > > mode for SQL that would work along the lines of executing a SQL
> script
> > > > (incl. init scripts) located in a particular directory in the Docker
> > > Image.
> > > > Details to be discussed.
> > > >
> > > > Do you think Zeppelin/SQL CLI could work with such a mode for
> > > > non-interactive queries (interactive queries would use a session
> > > cluster)?
> > > >
> > > > Best,
> > > >
> > > > Konstantin
> > > >
> > > >
> > > > On Sat, Feb 12, 2022 at 4:31 AM Jark Wu  wrote:
> > > >
> > > > > Hi David,
> > > > >
> > > > > Zeppelin and SQL CLI also support submitting long-running streaming
> > SQL
> > > > > jobs. So the session cluster is not a fit mode.
> > > > >
> > > > > Best,
> > > > > Jark
> > > > >
> > > > > On Fri, 11 Feb 2022 at 22:42, David Morávek 
> wrote:
> > > > >
> > > > > > Hi Jark, can you please elaborate about the current need of the
> > > per-job
> > > > > > mode for interactive clients (eg. Zeppelin that you've
> mentioned)?
> > > > Aren't
> > > > > > these a natural fit for the session cluster?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Fri, Feb 11, 2022 at 3:25 PM Jark Wu 
> wrote:
> > > > > >
> > > > > > > Hi Konstantin,
> > > > > > >
> > > > > > > I'm not very familiar with the implementation of per-job mode
> and
> > > > > > > application mode.
> > > > > > > But is there any instruction for users abou how to migrate
> > > > > platforms/jobs
> > > > > > > to application mode?
> > > > > > > IIUC, the biggest difference between the two modes is where the
> > > > main()
> > > > > > > method is executed.
> > > > > > > However, SQL jobs are not jar applications and don't have the
> > > main()
> > > > > > > method.
> > > > > > > For example, SQL CLI submits SQL jobs by invoking
> > > > > > > `StreamExecutionEnvironment#executeAsync(StreamGraph)`.
> > > > > > > How SQL Client and SQL platforms (e.g. Zeppelin) support
> > > application
> > > > > > mode?
> > > > > > >
> > > > > > > Best,
> > > > > > > Jark
> > > > > > >
> > > > > > >
> > > > > > > On Fri, 28 Jan 2022 at 23:33, Konstantin Knauf <
> > kna...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > Thank you for sharing your perspectives. I was not aware of
> > > > > > > > these limitations of per-job mode on YARN. It seems that
> there
> > > is a
> > > > > > > general
> > > > > > > > agreement to deprecate per-job mode and to drop it once the
> > > > > limitations
> > > > > > > > around YARN are resolved. I've started a corresponding vote
> in
> > > [1].
> > > > > > > >
> > > > > > > > Thanks again,
> > > > > > > >
> > > > > > > > Konstantin
> > > > > > > >
> > > > > > > >
> > > > > > > > [1]
> > > > https://lists.apache.org/thread/v6oz92dfp95qcox45l0f8393089oyjv4
> > > > > > > >
> > > > > > > > On Fri, Jan 28, 2022 at 1:53 PM Ferenc Csaky
> > > > > >  > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Yang,
> > > > > > > > >
> > > > > > > > > Thank you for the clarification. In general I think we will
> > > have
> > > > > time
> > > > > > > to
> > > > > > > > > experiment with this until it will be removed totally and
> > > migrate
> > > > > our
> > > > > > > > > solution to use application mode.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > F
> > > > > > > > >
> > > > > > > > > On 2022/01/26 02:42:24 Yang Wang wrote:
> > > > > > > > > > Hi all,

[jira] [Created] (FLINK-26235) CompactingFileWriter and PendingFileRecoverable should not be exposed to users.

[Gen Luo (Jira)]

Gen Luo created FLINK-26235:
---

 Summary: CompactingFileWriter and PendingFileRecoverable should 
not be exposed to users.
 Key: FLINK-26235
 URL: https://issues.apache.org/jira/browse/FLINK-26235
 Project: Flink
  Issue Type: Bug
  Components: Connectors / FileSystem
Reporter: Gen Luo






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

[Jingsong Li]

+1 to remove it.

Thanks for driving.

Best,
Jingsong

On Thu, Feb 17, 2022 at 8:44 PM Till Rohrmann  wrote:
>
> +1 to remove it.
>
> Cheers,
> Till
>
> On Thu, Feb 17, 2022 at 1:42 PM Martijn Visser 
> wrote:
>
> > +1 to remove it
> >
> > On Thu, 17 Feb 2022 at 13:34, Chesnay Schepler  wrote:
> >
> > > +1 to remove it.
> > >
> > > On 17/02/2022 13:31, Konstantin Knauf wrote:
> > > > +1
> > > >
> > > > On Thu, Feb 17, 2022 at 1:11 PM Robert Metzger 
> > > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> Some time ago, we added this "Automated Checks / Review Progress" [1]
> > > bot
> > > >> to the Flink PRs. I'm not aware of anybody using it, and I'm also not
> > > sure
> > > >> if it still works properly.
> > > >>
> > > >> Therefore, I propose to disable this bot. Please let me know if you
> > > >> disagree, otherwise, I'll soon disable it.
> > > >>
> > > >>
> > > >> Best,
> > > >> Robert
> > > >>
> > > >>
> > > >> [1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516
> > > >>
> > > >
> > >
> > >
> >

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Jingsong Li]

Congratulations!

Best,
Jingsong

On Thu, Feb 17, 2022 at 8:08 PM Jinzhong Li  wrote:
>
> Congratulations!
>
>
> Best,
>
> Jinzhong
>
> On Wed, Feb 16, 2022 at 9:23 PM Robert Metzger  wrote:
>
> > Hi all,
> >
> > I would like to formally announce a few new Flink PMC members on the dev@
> > list. The PMC has not done a good job of always announcing new PMC members
> > (and committers) recently. I'll try to keep an eye on this in the future to
> > improve the situation.
> >
> > Nevertheless, I'm very happy to announce some very active community members
> > as new PMC members:
> >
> > - Igal Shilman, added to the PMC in October 2021
> > - Konstantin Knauf, added to the PMC in January 2022
> > - Yun Gao, added to the PMC in February 2022
> >
> > Please join me in welcoming them to the Flink PMC!
> >
> > Best,
> > Robert
> >

Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Jingsong Li]

Congratulations!

Best,
Jingsong

On Fri, Feb 18, 2022 at 9:47 AM Zhipeng Zhang  wrote:
>
> Thank you everyone for the warm welcome!
>
> Best,
> Zhipeng
>
> Jinzhong Li  于2022年2月17日周四 19:58写道：
>
> > Congratulations!
> >
> >
> > Best,
> >
> > Jinzhong
> >
> > Robert Metzger  于2022年2月16日周三 21:32写道：
> >
> > > Hi everyone,
> > >
> > > On behalf of the PMC, I'm very happy to announce two new Flink
> > > committers: Feng Wang and Zhipeng Zhang!
> > >
> > > Feng is one of the most active Flink evangelists in China, with plenty of
> > > public talks, blog posts and other evangelization activities. The PMC
> > wants
> > > to recognize and value these efforts by making Feng a committer!
> > >
> > > Zhipeng Zhang has made significant contributions to flink-ml, like most
> > of
> > > the FLIPs for our ML efforts.
> > >
> > > Please join me in welcoming them as committers!
> > >
> > >
> > > Best,
> > > Robert
> > >
> >
>
>
> --
> best,
> Zhipeng

Re:Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Yuepeng Pan]

Congratulations!


Best,
Yuepeng Pan














在 2022-02-18 12:41:18，"Jingsong Li"  写道：
>Congratulations!
>
>Best,
>Jingsong
>
>On Fri, Feb 18, 2022 at 9:47 AM Zhipeng Zhang  wrote:
>>
>> Thank you everyone for the warm welcome!
>>
>> Best,
>> Zhipeng
>>
>> Jinzhong Li  于2022年2月17日周四 19:58写道：
>>
>> > Congratulations!
>> >
>> >
>> > Best,
>> >
>> > Jinzhong
>> >
>> > Robert Metzger  于2022年2月16日周三 21:32写道：
>> >
>> > > Hi everyone,
>> > >
>> > > On behalf of the PMC, I'm very happy to announce two new Flink
>> > > committers: Feng Wang and Zhipeng Zhang!
>> > >
>> > > Feng is one of the most active Flink evangelists in China, with plenty of
>> > > public talks, blog posts and other evangelization activities. The PMC
>> > wants
>> > > to recognize and value these efforts by making Feng a committer!
>> > >
>> > > Zhipeng Zhang has made significant contributions to flink-ml, like most
>> > of
>> > > the FLIPs for our ML efforts.
>> > >
>> > > Please join me in welcoming them as committers!
>> > >
>> > >
>> > > Best,
>> > > Robert
>> > >
>> >
>>
>>
>> --
>> best,
>> Zhipeng

[jira] [Created] (FLINK-26236) Track and cap retries in ReconciliationStatus

[Gyula Fora (Jira)]

Gyula Fora created FLINK-26236:
--

 Summary: Track and cap retries in ReconciliationStatus
 Key: FLINK-26236
 URL: https://issues.apache.org/jira/browse/FLINK-26236
 Project: Flink
  Issue Type: Sub-task
  Components: Kubernetes Operator
Reporter: Gyula Fora


At the moment we retry errors again and again indefinitely. As suggested by 
[~t...@apache.org] we should cap the number of retries (or the time spent 
retrying).

For this we can include a retrycount in the reconciliiation status,

Also we should distinguish fatal (like config errors) and recoverable errors 
with a different exception type and those should not be retried.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [DISCUSS]Support the merge statement in FlinkSQL

[Jingsong Li]

Hi zoucao,

Thanks for your proposal. I believe this discussion will take us one
step further for iceberg/hudi integration.

## `MERGE` for streaming

I feel that `MERGE` is very good for stream computing. And, this is
where our Flink can have an advantage over other computation systems.

MERGE INTO target_table USING source_table;

Under the semantics of stream computation, the incremental data of
source_table is read in real time, and these incremental data are
merged into the target_table in real time.

I think this is a great capability, and further research and
discussion is needed for detailed `MERGE INTO` streaming support.

## Calcite sql extensions

I'm not sure that calcite is good at extending its SQL syntax, a worst
case scenario is that Flink needs to maintain a version of calcite of
its own.

I would prefer that we try to push the syntax to the calcite community
as much as possible unless we have a clear solution for sql syntax
extensions.

Best,
Jingsong

On Thu, Feb 17, 2022 at 12:53 AM Francesco Guardiani
 wrote:
>
> > In the theory aspect, incremental data should be carefully considered for
> streaming data. In this situation,  the data flow from target_table to
> target_table
> will be a loop, and the incremental data with one key will keep going
> through
> the loop. It looks very strange.
>
> This is the same concern I have here, I don't see how MERGE can work in a
> streaming scenario without modifying its preliminary assumptions and
> semantics.
>
> Even assuming we put some hard constraint on the state size, for example
> requiring to specify a window definition (like in interval joins), I still
> think that the fundamental assumption of MERGE here is a problem: the
> target table is both a sink and a source. And I think this is a big issue,
> as we cannot reasonably assume that sink and sources are available for the
> same table definition or that they behave similarly.
>
> Also, talking about the batch implementation, I don't understand how you
> would implement this: from what I see in the "*validator*" paragraph of
> your document, you convert the merge statement to a bunch of other sql
> statements, but you omit the initial join, fundamental for the semantics of
> MERGE. Perhaps can you provide more details about it?
>
> On another note, I think we can take inspiration from MERGE and its "event
> driven" semantics, in order to have something that works both for batch and
> streaming, say a "Flink-ified" version of MERGE.
>
> For example, something that I can think of could be:
>
> PUSH TO target_table
> FROM source_table
> ON [window TVF]
> [when_clause [...]]
>
> Where when_clause looks like the ones from MERGE (looking at the pgsql).
> This has the window TVF constraint, so the state doesn't grow indefinitely,
> and the source_table is effectively any select you can think of, removing
> the assumption that the target is both a sink and a source. This statement
> at the end produces a changelog stream, pushed to the output table. A
> statement like this could then allow you to have something similar to the
> MERGE, just by replacing source_table with a select performing the join. Of
> course this is an example, and might not make much sense, but I hope it
> gives you the idea.
>
> FG
>
>
> On Mon, Feb 14, 2022 at 4:28 AM OpenInx  wrote:
>
> > I'm currently maintaining the iceberg flink modules from apache iceberg
> > community.
> >
> > Currently, the spark has a great integration experience with iceberg format
> > v2 in batch mode.  In this document [1],
> > The merge into syntax from spark sql extensions does really help a lot when
> > people want to change row-level data.
> >
> > We flink currently has a good integration with iceberg format v2 in
> > streaming mode, I mean people can export their
> > change log data into an iceberg table directly by writing a few sql.
> > This[2] is a good material to read if anybody want to
> > create a simple demo.
> >
> > But I'd say in the batch scenarios,  we flink sql currently lack few
> > critical SQL syntax (for integrating iceberg format v2 in batch mode
> > better):
> > 1.  ALTER TABLE to change columns.
> > 2.  UPDATE/DELETE sql to change the unexpected rows in a given table.
> > 3.  MERGE INTO to merge a batch changing row set  (mixed with
> > insert/delete/update) into the given table.
> >
> > In short, if we want to provide better integration and user experience with
> > iceberg v2 in batch, then I think the support of the above syntax
> > is very important (from iceberg perspective).
> >
> > > I think it's better to make that time investment at Calcite's
> > implementation before bringing this to Flink.
> >
> > I find that there are some sql syntax which are critical for flink sql
> > while not for other generic sql parser.  Is it possible to implement our
> > flink sql plugin/extensions which
> > extends the core calcite sql. Going a step further, is it possible for us
> > to achieve a better abstraction of the flink sql fra

Re: Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Lincoln Lee]

Congratulations Feng and Zhipeng!

Best,
Lincoln Lee


Yuepeng Pan  于2022年2月18日周五 12:45写道：

>
>
>
> Congratulations!
>
>
> Best,
> Yuepeng Pan
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 在 2022-02-18 12:41:18，"Jingsong Li"  写道：
> >Congratulations!
> >
> >Best,
> >Jingsong
> >
> >On Fri, Feb 18, 2022 at 9:47 AM Zhipeng Zhang 
> wrote:
> >>
> >> Thank you everyone for the warm welcome!
> >>
> >> Best,
> >> Zhipeng
> >>
> >> Jinzhong Li  于2022年2月17日周四 19:58写道：
> >>
> >> > Congratulations!
> >> >
> >> >
> >> > Best,
> >> >
> >> > Jinzhong
> >> >
> >> > Robert Metzger  于2022年2月16日周三 21:32写道：
> >> >
> >> > > Hi everyone,
> >> > >
> >> > > On behalf of the PMC, I'm very happy to announce two new Flink
> >> > > committers: Feng Wang and Zhipeng Zhang!
> >> > >
> >> > > Feng is one of the most active Flink evangelists in China, with
> plenty of
> >> > > public talks, blog posts and other evangelization activities. The
> PMC
> >> > wants
> >> > > to recognize and value these efforts by making Feng a committer!
> >> > >
> >> > > Zhipeng Zhang has made significant contributions to flink-ml, like
> most
> >> > of
> >> > > the FLIPs for our ML efforts.
> >> > >
> >> > > Please join me in welcoming them as committers!
> >> > >
> >> > >
> >> > > Best,
> >> > > Robert
> >> > >
> >> >
> >>
> >>
> >> --
> >> best,
> >> Zhipeng
>

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Lincoln Lee]

Congratulations!

Best,
Lincoln Lee


Jingsong Li  于2022年2月18日周五 12:42写道：

> Congratulations!
>
> Best,
> Jingsong
>
> On Thu, Feb 17, 2022 at 8:08 PM Jinzhong Li 
> wrote:
> >
> > Congratulations!
> >
> >
> > Best,
> >
> > Jinzhong
> >
> > On Wed, Feb 16, 2022 at 9:23 PM Robert Metzger 
> wrote:
> >
> > > Hi all,
> > >
> > > I would like to formally announce a few new Flink PMC members on the
> dev@
> > > list. The PMC has not done a good job of always announcing new PMC
> members
> > > (and committers) recently. I'll try to keep an eye on this in the
> future to
> > > improve the situation.
> > >
> > > Nevertheless, I'm very happy to announce some very active community
> members
> > > as new PMC members:
> > >
> > > - Igal Shilman, added to the PMC in October 2021
> > > - Konstantin Knauf, added to the PMC in January 2022
> > > - Yun Gao, added to the PMC in February 2022
> > >
> > > Please join me in welcoming them to the Flink PMC!
> > >
> > > Best,
> > > Robert
> > >
>

[jira] [Created] (FLINK-26237) PulsarSourceOrderedE2ECase failed on azure due to timeout

[Yun Gao (Jira)]

Yun Gao created FLINK-26237:
---

 Summary: PulsarSourceOrderedE2ECase failed on azure due to timeout
 Key: FLINK-26237
 URL: https://issues.apache.org/jira/browse/FLINK-26237
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.0
Reporter: Yun Gao



{code:java}
Feb 17 10:43:42 [ERROR] Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time 
elapsed: 636.317 s <<< FAILURE! - in 
org.apache.flink.tests.util.pulsar.PulsarSourceOrderedE2ECase
Feb 17 10:43:42 [ERROR] 
org.apache.flink.tests.util.pulsar.PulsarSourceOrderedE2ECase.testScaleDown(TestEnvironment,
 DataStreamSourceExternalContext, CheckpointingMode)[2]  Time elapsed: 155.986 
s  <<< FAILURE!
Feb 17 10:43:42 java.lang.AssertionError: 
Feb 17 10:43:42 
Feb 17 10:43:42 Expecting
Feb 17 10:43:42   
Feb 17 10:43:42 to be completed within 2M.
Feb 17 10:43:42 
Feb 17 10:43:42 exception caught while trying to get the future result: 
java.util.concurrent.TimeoutException
Feb 17 10:43:42 at 
java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1784)
Feb 17 10:43:42 at 
java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928)
Feb 17 10:43:42 at 
org.assertj.core.internal.Futures.assertSucceededWithin(Futures.java:109)
Feb 17 10:43:42 at 
org.assertj.core.api.AbstractCompletableFutureAssert.internalSucceedsWithin(AbstractCompletableFutureAssert.java:400)
Feb 17 10:43:42 at 
org.assertj.core.api.AbstractCompletableFutureAssert.succeedsWithin(AbstractCompletableFutureAssert.java:396)
Feb 17 10:43:42 at 
org.apache.flink.connector.testframe.testsuites.SourceTestSuiteBase.checkResultWithSemantic(SourceTestSuiteBase.java:766)
Feb 17 10:43:42 at 
org.apache.flink.connector.testframe.testsuites.SourceTestSuiteBase.restartFromSavepoint(SourceTestSuiteBase.java:399)
Feb 17 10:43:42 at 
org.apache.flink.connector.testframe.testsuites.SourceTestSuiteBase.testScaleDown(SourceTestSuiteBase.java:285)
Feb 17 10:43:42 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
Feb 17 10:43:42 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Feb 17 10:43:42 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Feb 17 10:43:42 at java.lang.reflect.Method.invoke(Method.java:498)
Feb 17 10:43:42 at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestTemplateMethod(TimeoutExtension.java:92)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
Feb 17 10:43:42 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:214)
Feb 17 10:43:42 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)

{code}

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31719&view=logs&j=af184cdd-c6d8-5084-0b69-7e9c67b35f7a&t=160c9ae5-96fd-516e-1c91-deb81f59292a&l=15832



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26238) PulsarSinkITCase.writeRecordsToPulsar failed on azure

[Yun Gao (Jira)]

Yun Gao created FLINK-26238:
---

 Summary: PulsarSinkITCase.writeRecordsToPulsar failed on azure
 Key: FLINK-26238
 URL: https://issues.apache.org/jira/browse/FLINK-26238
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.0
Reporter: Yun Gao



{code:java}
Feb 17 12:19:44 [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time 
elapsed: 342.177 s <<< FAILURE! - in 
org.apache.flink.connector.pulsar.sink.PulsarSinkITCase
Feb 17 12:19:44 [ERROR] 
org.apache.flink.connector.pulsar.sink.PulsarSinkITCase.writeRecordsToPulsar(DeliveryGuarantee)[3]
  Time elapsed: 302.4 s  <<< FAILURE!
Feb 17 12:19:44 java.lang.AssertionError: 
Feb 17 12:19:44 
Feb 17 12:19:44 Actual and expected should have same size but actual size is:
Feb 17 12:19:44   0
Feb 17 12:19:44 while expected size is:
Feb 17 12:19:44   179
Feb 17 12:19:44 Actual was:
Feb 17 12:19:44   []
Feb 17 12:19:44 Expected was:
Feb 17 12:19:44   ["NONE-CzYEIFDd-0-eELBphcHiu",
Feb 17 12:19:44 "NONE-CzYEIFDd-1-odr3NpH6pg",
Feb 17 12:19:44 "NONE-CzYEIFDd-2-HfIphNFXoM",
Feb 17 12:19:44 "NONE-CzYEIFDd-3-iaZ9v2HCnw",
Feb 17 12:19:44 "NONE-CzYEIFDd-4-6KkXK34GZl",
Feb 17 12:19:44 "NONE-CzYEIFDd-5-jK9UxXSQcX",
Feb 17 12:19:44 "NONE-CzYEIFDd-6-HipVPVNqZA",
Feb 17 12:19:44 "NONE-CzYEIFDd-7-lT4lVH3CzX",
Feb 17 12:19:44 "NONE-CzYEIFDd-8-4jShEBuQaS",
Feb 17 12:19:44 "NONE-CzYEIFDd-9-fInSd97msu",
Feb 17 12:19:44 "NONE-CzYEIFDd-10-dGBm5e92os",
Feb 17 12:19:44 "NONE-CzYEIFDd-11-GkINb6Dipx",
Feb 17 12:19:44 "NONE-CzYEIFDd-12-M7Q8atHhNQ",
Feb 17 12:19:44 "NONE-CzYEIFDd-13-EG2FpyziCL",
Feb 17 12:19:44 "NONE-CzYEIFDd-14-4HwGJSOkTk",
Feb 17 12:19:44 "NONE-CzYEIFDd-15-UC0IwwKN0O",
Feb 17 12:19:44 "NONE-CzYEIFDd-16-D9FOV8hKBq",
Feb 17 12:19:44 "NONE-CzYEIFDd-17-J2Zb6pNmOO",
Feb 17 12:19:44 "NONE-CzYEIFDd-18-abo3YgkYKP",
Feb 17 12:19:44 "NONE-CzYEIFDd-19-4Q5GbBRSc6",
Feb 17 12:19:44 "NONE-CzYEIFDd-20-WxSP9oExJP",
Feb 17 12:19:44 "NONE-CzYEIFDd-21-0wiqq21CY1",
Feb 17 12:19:44 "NONE-CzYEIFDd-22-3iJQiFjgQu",
Feb 17 12:19:44 "NONE-CzYEIFDd-23-78je74YwU6",
Feb 17 12:19:44 "NONE-CzYEIFDd-24-tEkEaF9IuD",
Feb 17 12:19:44 "NONE-CzYEIFDd-25-vDi5h44tjJ",
Feb 17 12:19:44 "NONE-CzYEIFDd-26-GzIh4FLlvP",

{code}

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31739&view=logs&j=fc5181b0-e452-5c8f-68de-1097947f6483&t=995c650b-6573-581c-9ce6-7ad4cc038461&l=27095



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[godfrey he]

Congratulations!

Best,
Godfrey

Lincoln Lee  于2022年2月18日周五 14:07写道：
>
> Congratulations!
>
> Best,
> Lincoln Lee
>
>
> Jingsong Li  于2022年2月18日周五 12:42写道：
>
> > Congratulations!
> >
> > Best,
> > Jingsong
> >
> > On Thu, Feb 17, 2022 at 8:08 PM Jinzhong Li 
> > wrote:
> > >
> > > Congratulations!
> > >
> > >
> > > Best,
> > >
> > > Jinzhong
> > >
> > > On Wed, Feb 16, 2022 at 9:23 PM Robert Metzger 
> > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I would like to formally announce a few new Flink PMC members on the
> > dev@
> > > > list. The PMC has not done a good job of always announcing new PMC
> > members
> > > > (and committers) recently. I'll try to keep an eye on this in the
> > future to
> > > > improve the situation.
> > > >
> > > > Nevertheless, I'm very happy to announce some very active community
> > members
> > > > as new PMC members:
> > > >
> > > > - Igal Shilman, added to the PMC in October 2021
> > > > - Konstantin Knauf, added to the PMC in January 2022
> > > > - Yun Gao, added to the PMC in February 2022
> > > >
> > > > Please join me in welcoming them to the Flink PMC!
> > > >
> > > > Best,
> > > > Robert
> > > >
> >

Re: Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[godfrey he]

Congratulations!

Best,
Godfrey

Lincoln Lee  于2022年2月18日周五 14:05写道：
>
> Congratulations Feng and Zhipeng!
>
> Best,
> Lincoln Lee
>
>
> Yuepeng Pan  于2022年2月18日周五 12:45写道：
>
> >
> >
> >
> > Congratulations!
> >
> >
> > Best,
> > Yuepeng Pan
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 在 2022-02-18 12:41:18，"Jingsong Li"  写道：
> > >Congratulations!
> > >
> > >Best,
> > >Jingsong
> > >
> > >On Fri, Feb 18, 2022 at 9:47 AM Zhipeng Zhang 
> > wrote:
> > >>
> > >> Thank you everyone for the warm welcome!
> > >>
> > >> Best,
> > >> Zhipeng
> > >>
> > >> Jinzhong Li  于2022年2月17日周四 19:58写道：
> > >>
> > >> > Congratulations!
> > >> >
> > >> >
> > >> > Best,
> > >> >
> > >> > Jinzhong
> > >> >
> > >> > Robert Metzger  于2022年2月16日周三 21:32写道：
> > >> >
> > >> > > Hi everyone,
> > >> > >
> > >> > > On behalf of the PMC, I'm very happy to announce two new Flink
> > >> > > committers: Feng Wang and Zhipeng Zhang!
> > >> > >
> > >> > > Feng is one of the most active Flink evangelists in China, with
> > plenty of
> > >> > > public talks, blog posts and other evangelization activities. The
> > PMC
> > >> > wants
> > >> > > to recognize and value these efforts by making Feng a committer!
> > >> > >
> > >> > > Zhipeng Zhang has made significant contributions to flink-ml, like
> > most
> > >> > of
> > >> > > the FLIPs for our ML efforts.
> > >> > >
> > >> > > Please join me in welcoming them as committers!
> > >> > >
> > >> > >
> > >> > > Best,
> > >> > > Robert
> > >> > >
> > >> >
> > >>
> > >>
> > >> --
> > >> best,
> > >> Zhipeng
> >

[jira] [Created] (FLINK-26239) EventTimeWindowCheckpointingITCase.testSlidingTimeWindow failed on azure

[Yun Gao (Jira)]

Yun Gao created FLINK-26239:
---

 Summary: EventTimeWindowCheckpointingITCase.testSlidingTimeWindow 
failed on azure
 Key: FLINK-26239
 URL: https://issues.apache.org/jira/browse/FLINK-26239
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Checkpointing
Affects Versions: 1.15.0
Reporter: Yun Gao


{code:java}
2022-02-17T11:46:39.1850375Z Feb 17 11:46:39 Starting 
org.apache.flink.test.checkpointing.EventTimeWindowCheckpointingITCase#testSlidingTimeWindow[statebackend
 type =ROCKSDB_INCREMENTAL, buffersPerChannel = 2].
2022-02-17T11:46:39.1854584Z 
org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
2022-02-17T11:46:39.1855470Zat 
org.apache.flink.runtime.jobmaster.JobResult.toJobExecutionResult(JobResult.java:144)
2022-02-17T11:46:39.1856444Zat 
org.apache.flink.runtime.minicluster.MiniClusterJobClient.lambda$getJobExecutionResult$3(MiniClusterJobClient.java:141)
2022-02-17T11:46:39.1857393Zat 
java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:616)
2022-02-17T11:46:39.1858400Zat 
java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591)
2022-02-17T11:46:39.1865249Zat 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
2022-02-17T11:46:39.1866299Zat 
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
2022-02-17T11:46:39.1867590Zat 
org.apache.flink.runtime.rpc.akka.AkkaInvocationHandler.lambda$invokeRpc$1(AkkaInvocationHandler.java:259)
2022-02-17T11:46:39.1868546Zat 
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
2022-02-17T11:46:39.1869254Zat 
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
2022-02-17T11:46:39.1869828Zat 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
2022-02-17T11:46:39.1870367Zat 
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
2022-02-17T11:46:39.1871131Zat 
org.apache.flink.util.concurrent.FutureUtils.doForward(FutureUtils.java:1389)
2022-02-17T11:46:39.1872123Zat 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.lambda$null$1(ClassLoadingUtils.java:93)
2022-02-17T11:46:39.1875765Zat 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:68)
2022-02-17T11:46:39.1877055Zat 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.lambda$guardCompletionWithContextClassLoader$2(ClassLoadingUtils.java:92)
2022-02-17T11:46:39.1878032Zat 
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
2022-02-17T11:46:39.1879084Zat 
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
2022-02-17T11:46:39.1879697Zat 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
2022-02-17T11:46:39.1880252Zat 
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
2022-02-17T11:46:39.1880840Zat 
org.apache.flink.runtime.concurrent.akka.AkkaFutureUtils$1.onComplete(AkkaFutureUtils.java:47)
2022-02-17T11:46:39.1881357Zat 
akka.dispatch.OnComplete.internal(Future.scala:300)
2022-02-17T11:46:39.1881788Zat 
akka.dispatch.OnComplete.internal(Future.scala:297)

...

2022-02-17T11:46:39.1915003Z Caused by: 
org.apache.flink.util.FlinkRuntimeException: Exceeded checkpoint tolerable 
failure threshold.
2022-02-17T11:46:39.1915653Zat 
org.apache.flink.runtime.checkpoint.CheckpointFailureManager.checkFailureAgainstCounter(CheckpointFailureManager.java:160)
2022-02-17T11:46:39.1916393Zat 
org.apache.flink.runtime.checkpoint.CheckpointFailureManager.handleJobLevelCheckpointException(CheckpointFailureManager.java:123)
2022-02-17T11:46:39.1917125Zat 
org.apache.flink.runtime.checkpoint.CheckpointFailureManager.handleCheckpointException(CheckpointFailureManager.java:90)
2022-02-17T11:46:39.1917819Zat 
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.abortPendingCheckpoint(CheckpointCoordinator.java:2046)
2022-02-17T11:46:39.1918594Zat 
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.abortPendingCheckpoint(CheckpointCoordinator.java:2025)
2022-02-17T11:46:39.1919268Zat 
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.access$600(CheckpointCoordinator.java:98)
2022-02-17T11:46:39.1920052Zat 
org.apache.flink.runtime.checkpoint.CheckpointCoordinator$CheckpointCanceller.run(CheckpointCoordinator.java:2104)
2022-02-17T11:46:39.1920852Zat 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2022-02-17T11:46:39.1921390Zat 
java.util.concurrent.FutureTask.run(FutureTask.java:266)
2022-02-17T11:46:39.1922079Zat 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Schedule

[jira] [Created] (FLINK-26240) PulsarSinkITCase.tearDown failed in azure

[Leonard Xu (Jira)]

Leonard Xu created FLINK-26240:
--

 Summary: PulsarSinkITCase.tearDown failed in azure
 Key: FLINK-26240
 URL: https://issues.apache.org/jira/browse/FLINK-26240
 Project: Flink
  Issue Type: Bug
Reporter: Leonard Xu
 Fix For: 1.15.0


{code:java}
[ERROR] Picked up JAVA_TOOL_OPTIONS: -XX:+HeapDumpOnOutOfMemoryError
2022-02-18T04:16:39.9647195Z Feb 18 04:16:39 [INFO] Running 
org.apache.flink.connector.pulsar.sink.PulsarSinkITCase
2022-02-18T04:16:50.3942088Z Feb 18 04:16:50 [ERROR] Tests run: 1, Failures: 0, 
Errors: 1, Skipped: 0, Time elapsed: 10.402 s <<< FAILURE! - in 
org.apache.flink.connector.pulsar.sink.PulsarSinkITCase
2022-02-18T04:16:50.3942900Z Feb 18 04:16:50 [ERROR] 
org.apache.flink.connector.pulsar.sink.PulsarSinkITCase  Time elapsed: 10.402 s 
 <<< ERROR!
2022-02-18T04:16:50.3943824Z Feb 18 04:16:50 java.lang.IllegalStateException: 
java.io.IOException: Couldn't connect to zookeeper server
2022-02-18T04:16:50.3944479Z Feb 18 04:16:50at 
org.apache.flink.connector.pulsar.testutils.runtime.embedded.PulsarEmbeddedRuntime.startUp(PulsarEmbeddedRuntime.java:91)
2022-02-18T04:16:50.3945184Z Feb 18 04:16:50at 
org.apache.flink.connector.pulsar.testutils.PulsarTestEnvironment.beforeAll(PulsarTestEnvironment.java:90)
2022-02-18T04:16:50.3945939Z Feb 18 04:16:50at 
org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.lambda$invokeBeforeAllCallbacks$10(ClassBasedTestDescriptor.java:381)
2022-02-18T04:16:50.3946661Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
2022-02-18T04:16:50.3947345Z Feb 18 04:16:50at 
org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.invokeBeforeAllCallbacks(ClassBasedTestDescriptor.java:381)
2022-02-18T04:16:50.3948194Z Feb 18 04:16:50at 
org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.before(ClassBasedTestDescriptor.java:205)
2022-02-18T04:16:50.3948848Z Feb 18 04:16:50at 
org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.before(ClassBasedTestDescriptor.java:80)
2022-02-18T04:16:50.3949645Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:148)
2022-02-18T04:16:50.3950418Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
2022-02-18T04:16:50.3951073Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
2022-02-18T04:16:50.3951899Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
2022-02-18T04:16:50.3952498Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
2022-02-18T04:16:50.3953118Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
2022-02-18T04:16:50.3953754Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
2022-02-18T04:16:50.3954362Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
2022-02-18T04:16:50.3954857Z Feb 18 04:16:50at 
java.util.ArrayList.forEach(ArrayList.java:1259)
2022-02-18T04:16:50.3955489Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:41)
2022-02-18T04:16:50.3956218Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:155)
2022-02-18T04:16:50.3956858Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
2022-02-18T04:16:50.3957484Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
2022-02-18T04:16:50.3958177Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
2022-02-18T04:16:50.3958770Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
2022-02-18T04:16:50.3959569Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
2022-02-18T04:16:50.3960201Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
2022-02-18T04:16:50.3960812Z Feb 18 04:16:50at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
2022-02-18T04:16:50.3961507Z Feb 18 04:16:50at 
org.junit.plat

[jira] [Created] (FLINK-26241) Pulsar.RoundRobinTopicRouterTest failed due to lang.ArithmeticException

[Leonard Xu (Jira)]

Leonard Xu created FLINK-26241:
--

 Summary: Pulsar.RoundRobinTopicRouterTest failed due to 
lang.ArithmeticException 
 Key: FLINK-26241
 URL: https://issues.apache.org/jira/browse/FLINK-26241
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Reporter: Leonard Xu
 Fix For: 1.15.0






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26242) Pulsar connector tests fails the JVM with exit code 255

[Yun Gao (Jira)]

Yun Gao created FLINK-26242:
---

 Summary: Pulsar connector tests fails the JVM with exit code 255
 Key: FLINK-26242
 URL: https://issues.apache.org/jira/browse/FLINK-26242
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.0
Reporter: Yun Gao


{code:java}
23:03:52,970 [metadata-store-906-1] INFO  
org.apache.pulsar.broker.namespace.OwnedBundle               [] - Unloading 
pulsar/standalone/127.0.0.1:43356/0x_0x namespace-bundle with 0 
topics completed in 1.0 ms
23:03:52,970 [                main] INFO  
org.apache.pulsar.broker.namespace.OwnedBundle               [] - Disabling 
ownership: pulsar/127.0.0.1:43356/0x_0x
23:03:52,971 [metadata-store-906-1] INFO  
org.apache.pulsar.broker.namespace.OwnershipCache            [] - Resource lock 
for /namespace/pulsar/127.0.0.1:43356/0x_0x has expired
23:03:52,971 [metadata-store-906-1] INFO  
org.apache.pulsar.metadata.coordination.impl.LockManagerImpl [] - Released 
resource lock on /namespace/pulsar/127.0.0.1:43356/0x_0x
23:03:52,971 [metadata-store-906-1] INFO  
org.apache.pulsar.broker.namespace.OwnedBundle               [] - Unloading 
pulsar/127.0.0.1:43356/0x_0x namespace-bundle with 0 topics 
completed in 1.0 ms
23:03:52,971 [                main] INFO  
org.apache.pulsar.broker.namespace.OwnedBundle               [] - Disabling 
ownership: public/default/0xc000_0x
23:03:52,972 [metadata-store-906-1] INFO  
org.apache.pulsar.broker.namespace.OwnershipCache            [] - Resource lock 
for /namespace/public/default/0xc000_0x has expired
23:03:52,973 [metadata-store-906-1] INFO  
org.apache.pulsar.metadata.coordination.impl.LockManagerImpl [] - Released 
resource lock on /namespace/public/default/0xc000_0x
23:03:52,973 [metadata-store-906-1] INFO  
org.apache.pulsar.broker.namespace.OwnedBundle               [] - Unloading 
public/default/0xc000_0x namespace-bundle with 0 topics completed 
in 1.0 ms
23:03:52,973 [                main] INFO  
org.apache.pulsar.broker.service.BrokerService               [] - Unloading 7 
namespace-bundles completed in 0.009 seconds
23:03:52,973 [                main] INFO  
org.apache.pulsar.broker.service.BrokerService               [] - Event loops 
shutting down gracefully...
23:03:52,974 [    pulsar-io-905-10] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0x79d7ad85, L:/127.0.0.1:55188 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,974 [     pulsar-io-905-6] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0x98490f33, L:/127.0.0.1:55180 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,974 [     bookie-io-888-9] INFO  
org.apache.bookkeeper.proto.BookieRequestHandler             [] - Channels 
disconnected: [id: 0x28997aa1, L:/127.0.0.1:35707 ! R:/127.0.0.1:55188]
23:03:52,974 [     bookie-io-888-5] INFO  
org.apache.bookkeeper.proto.BookieRequestHandler             [] - Channels 
disconnected: [id: 0x4a15d8d9, L:/127.0.0.1:35707 ! R:/127.0.0.1:55180]
23:03:52,975 [     bookie-io-888-3] INFO  
org.apache.bookkeeper.proto.BookieRequestHandler             [] - Channels 
disconnected: [id: 0xbf8feb70, L:/127.0.0.1:35707 ! R:/127.0.0.1:55176]
23:03:52,975 [     pulsar-io-905-4] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0xe8635990, L:/127.0.0.1:55176 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,975 [    pulsar-io-905-12] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0x50cd9cf3, L:/127.0.0.1:55192 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,975 [     pulsar-io-905-5] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0x83aa4bab, L:/127.0.0.1:55178 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,975 [     bookie-io-888-4] INFO  
org.apache.bookkeeper.proto.BookieRequestHandler             [] - Channels 
disconnected: [id: 0x1fb66760, L:/127.0.0.1:35707 ! R:/127.0.0.1:55178]
23:03:52,975 [    bookie-io-888-11] INFO  
org.apache.bookkeeper.proto.BookieRequestHandler             [] - Channels 
disconnected: [id: 0x72c5c9d1, L:/127.0.0.1:35707 ! R:/127.0.0.1:55192]
23:03:52,975 [     pulsar-io-905-3] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0xb6a6a3d0, L:/127.0.0.1:55174 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,975 [    pulsar-io-905-13] INFO  
org.apache.bookkeeper.proto.PerChannelBookieClient           [] - Disconnected 
from bookie channel [id: 0x23fa0dd7, L:/127.0.0.1:55194 ! 
R:127.0.0.1/127.0.0.1:35707]
23:03:52,975 [    bookie-io-888-10] INFO  
org.apache.bookkeeper.proto.Bookie

[jira] [Created] (FLINK-26243) RoundRobinTopicRouterTest.routeMessagesInRoundRobin failed on azure due to divide by zero

[Yun Gao (Jira)]

Yun Gao created FLINK-26243:
---

 Summary: RoundRobinTopicRouterTest.routeMessagesInRoundRobin 
failed on azure due to divide by zero
 Key: FLINK-26243
 URL: https://issues.apache.org/jira/browse/FLINK-26243
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.0
Reporter: Yun Gao


{code:java}
Feb 18 03:17:52 [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time 
elapsed: 0.013 s <<< FAILURE! - in 
org.apache.flink.connector.pulsar.sink.writer.router.RoundRobinTopicRouterTest
Feb 18 03:17:52 [ERROR] 
org.apache.flink.connector.pulsar.sink.writer.router.RoundRobinTopicRouterTest.routeMessagesInRoundRobin
  Time elapsed: 0.005 s  <<< ERROR!
Feb 18 03:17:52 java.lang.ArithmeticException: / by zero
Feb 18 03:17:52 at 
org.apache.flink.connector.pulsar.sink.writer.router.RoundRobinTopicRouter.route(RoundRobinTopicRouter.java:57)
Feb 18 03:17:52 at 
org.apache.flink.connector.pulsar.sink.writer.router.RoundRobinTopicRouterTest.routeMessagesInRoundRobin(RoundRobinTopicRouterTest.java:78)
Feb 18 03:17:52 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
Feb 18 03:17:52 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Feb 18 03:17:52 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Feb 18 03:17:52 at java.lang.reflect.Method.invoke(Method.java:498)
Feb 18 03:17:52 at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:214)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:210)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:135)
Feb 18 03:17:52 at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:66)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
Feb 18 03:17:52 at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
Feb 18 03

[NOTICE] Pulsar tests disabled

[Chesnay Schepler]

FYI: I just disabled all Pulsar tests on master in 
296c3be7576940d6bd76f4d065a0b70bceb06991.


They are currently the main source of test instabilities, and I don't 
see any real efforts or progress on those being addressed.