[jira] [Commented] (FLINK-29359) Pulsar Table Connector pom config and packaging
[ https://issues.apache.org/jira/browse/FLINK-29359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760716#comment-17760716 ] Yufei Zhang commented on FLINK-29359: - [~tison] Yeah I think when the ticket is created it was still an issue. But I didn't update it timely and I'm unaware of the current situation now. But I think it should be safe to close this ticket~ > Pulsar Table Connector pom config and packaging > --- > > Key: FLINK-29359 > URL: https://issues.apache.org/jira/browse/FLINK-29359 > Project: Flink > Issue Type: Sub-task > Components: Connectors / Pulsar >Affects Versions: 1.17.0 >Reporter: Yufei Zhang >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-29359) Pulsar Table Connector pom config and packaging
[ https://issues.apache.org/jira/browse/FLINK-29359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760716#comment-17760716 ] Yufei Zhang edited comment on FLINK-29359 at 8/31/23 4:56 AM: -- [~tison] Yeah I think when the ticket is created it was still an issue. But I didn't update it timely and I'm unaware of the current situation now. I think it should be safe to close this ticket~ was (Author: affe): [~tison] Yeah I think when the ticket is created it was still an issue. But I didn't update it timely and I'm unaware of the current situation now. But I think it should be safe to close this ticket~ > Pulsar Table Connector pom config and packaging > --- > > Key: FLINK-29359 > URL: https://issues.apache.org/jira/browse/FLINK-29359 > Project: Flink > Issue Type: Sub-task > Components: Connectors / Pulsar >Affects Versions: 1.17.0 >Reporter: Yufei Zhang >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-25582) flink sql kafka source cannot special custom parallelism
[ https://issues.apache.org/jira/browse/FLINK-25582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644704#comment-17644704 ] Yufei Zhang commented on FLINK-25582: - I currently use `table.exec.resource.default-parallelism` to set the sql source parallelism. But still it would be nice to set the source parallelism explicitly. > flink sql kafka source cannot special custom parallelism > > > Key: FLINK-25582 > URL: https://issues.apache.org/jira/browse/FLINK-25582 > Project: Flink > Issue Type: Improvement > Components: Connectors / Kafka, Table SQL / API >Affects Versions: 1.13.0, 1.14.0 >Reporter: venn wu >Priority: Not a Priority > Labels: auto-deprioritized-minor, pull-request-available > > when use flink sql api, all operator have same parallelism, but in some times > we want specify the source / sink parallelism for kafka source, i noticed the > kafka sink already have parameter "sink.parallelism" to specify the sink > parallelism, but kafka source no, so we want flink sql api, have a parameter > to specify the kafka source parallelism like sink. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29696) [Doc] Operator helm install command points to wrong repo
Yufei Zhang created FLINK-29696:
---
Summary: [Doc] Operator helm install command points to wrong repo
Key: FLINK-29696
URL: https://issues.apache.org/jira/browse/FLINK-29696
Project: Flink
Issue Type: Improvement
Components: Documentation, Kubernetes Operator
Reporter: Yufei Zhang
In the operator documentation, the repo is added via:
`helm repo add flink-operator-repo
https://downloads.apache.org/flink/flink-kubernetes-operator-/`
But later in the Operation-> Helm, the code instruct us to use
`{{{}helm install flink-kubernetes-operator helm/flink-kubernetes-operator`{}}}
{{}}
Here we won't be able to download the helm chart since we are not using the
right repo.
You can assign this Jira to me and I can submit a PR to fix it~
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-29390) Pulsar SQL Connector: SQLClient E2E testing
Yufei Zhang created FLINK-29390: --- Summary: Pulsar SQL Connector: SQLClient E2E testing Key: FLINK-29390 URL: https://issues.apache.org/jira/browse/FLINK-29390 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Affects Versions: 1.17.0 Reporter: Yufei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29360) Pulsar Table Connector Documentation
Yufei Zhang created FLINK-29360: --- Summary: Pulsar Table Connector Documentation Key: FLINK-29360 URL: https://issues.apache.org/jira/browse/FLINK-29360 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Affects Versions: 1.17.0 Reporter: Yufei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29358) Pulsar Table Connector testing
Yufei Zhang created FLINK-29358: --- Summary: Pulsar Table Connector testing Key: FLINK-29358 URL: https://issues.apache.org/jira/browse/FLINK-29358 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Affects Versions: 1.17.0 Reporter: Yufei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29359) Pulsar Table Connector pom config and packaging
Yufei Zhang created FLINK-29359: --- Summary: Pulsar Table Connector pom config and packaging Key: FLINK-29359 URL: https://issues.apache.org/jira/browse/FLINK-29359 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Affects Versions: 1.17.0 Reporter: Yufei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29357) Pulsar Table Sink code: implementation
Yufei Zhang created FLINK-29357: --- Summary: Pulsar Table Sink code: implementation Key: FLINK-29357 URL: https://issues.apache.org/jira/browse/FLINK-29357 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Affects Versions: 1.17.0 Reporter: Yufei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29356) Pulsar Table Source code :implementation
Yufei Zhang created FLINK-29356: --- Summary: Pulsar Table Source code :implementation Key: FLINK-29356 URL: https://issues.apache.org/jira/browse/FLINK-29356 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Affects Versions: 1.17.0 Reporter: Yufei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FLINK-26202) Support Table API in Pulsar Source Connector
[ https://issues.apache.org/jira/browse/FLINK-26202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Zhang closed FLINK-26202. --- Resolution: Invalid Closed because moved to FLINK-26203 and will be tracked as a subticket under that ticket. > Support Table API in Pulsar Source Connector > > > Key: FLINK-26202 > URL: https://issues.apache.org/jira/browse/FLINK-26202 > Project: Flink > Issue Type: New Feature > Components: Connectors / Pulsar >Affects Versions: 1.15.0 >Reporter: Yufei Zhang >Priority: Minor > Labels: Pulsar, auto-deprioritized-major > > Currently pulsar connector only supports DataStream API, we plan to support > Table API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26203) Support Table API in Pulsar Connector
[ https://issues.apache.org/jira/browse/FLINK-26203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Zhang updated FLINK-26203: Summary: Support Table API in Pulsar Connector (was: Support Table API in Pulsar Sink Connector) > Support Table API in Pulsar Connector > - > > Key: FLINK-26203 > URL: https://issues.apache.org/jira/browse/FLINK-26203 > Project: Flink > Issue Type: New Feature > Components: Connectors / Pulsar >Reporter: Yufei Zhang >Priority: Minor > Labels: Pulsar, auto-deprioritized-major > > Currently Pulsar connector only supports DataStream API. We plan to support > Table API as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-26203) Support Table API in Pulsar Sink Connector
[ https://issues.apache.org/jira/browse/FLINK-26203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607175#comment-17607175 ] Yufei Zhang commented on FLINK-26203: - I'm currently working on this Jira ( and FLINK-26202). However the Jira layout is not ideal. I have a plan to rework the Jira layout. # Close FLINK-26202 # Rename FLINK-26203 to support both source and sink Table API # create sub tickets under this ticket to track source and sink and other components (documentation, testing, etc.) Feel free to assign this ticket to me~ > Support Table API in Pulsar Sink Connector > -- > > Key: FLINK-26203 > URL: https://issues.apache.org/jira/browse/FLINK-26203 > Project: Flink > Issue Type: New Feature > Components: Connectors / Pulsar >Reporter: Yufei Zhang >Priority: Minor > Labels: Pulsar, auto-deprioritized-major > > Currently Pulsar connector only supports DataStream API. We plan to support > Table API as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-26541) SQL Client should support submitting SQL jobs in application mode
[ https://issues.apache.org/jira/browse/FLINK-26541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539178#comment-17539178 ] Yufei Zhang commented on FLINK-26541: - [~martijnvisser] I think he says "This feature is absolutely necessary, as FlinkSQL is becoming more and more populsar, and we saw the strength in application mode. It would feel so much better when we combine these two" > SQL Client should support submitting SQL jobs in application mode > - > > Key: FLINK-26541 > URL: https://issues.apache.org/jira/browse/FLINK-26541 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes, Deployment / YARN, Table SQL / > Client >Reporter: Jark Wu >Priority: Major > > Currently, the SQL Client only supports submitting jobs in session mode and > per-job mode. As the community going to drop the per-job mode (FLINK-26000), > SQL Client should support application mode as well. Otherwise, SQL Client can > only submit SQL in session mode then, but streaming jobs should be submitted > in per-job or application mode to have bettter resource isolation. > Disucssions: https://lists.apache.org/thread/2yq351nb721x23rz1q8qlyf2tqrk147r -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (FLINK-26541) SQL Client should support submitting SQL jobs in application mode
[ https://issues.apache.org/jira/browse/FLINK-26541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539178#comment-17539178 ] Yufei Zhang edited comment on FLINK-26541 at 5/19/22 3:02 AM: -- [~martijnvisser] I think he/she says "This feature is absolutely necessary, as FlinkSQL is becoming more and more populsar, and we saw the strength in application mode. It would feel so much better when we combine these two" was (Author: affe): [~martijnvisser] I think he says "This feature is absolutely necessary, as FlinkSQL is becoming more and more populsar, and we saw the strength in application mode. It would feel so much better when we combine these two" > SQL Client should support submitting SQL jobs in application mode > - > > Key: FLINK-26541 > URL: https://issues.apache.org/jira/browse/FLINK-26541 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes, Deployment / YARN, Table SQL / > Client >Reporter: Jark Wu >Priority: Major > > Currently, the SQL Client only supports submitting jobs in session mode and > per-job mode. As the community going to drop the per-job mode (FLINK-26000), > SQL Client should support application mode as well. Otherwise, SQL Client can > only submit SQL in session mode then, but streaming jobs should be submitted > in per-job or application mode to have bettter resource isolation. > Disucssions: https://lists.apache.org/thread/2yq351nb721x23rz1q8qlyf2tqrk147r -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (FLINK-27009) Support SQL job submission in flink kubernetes opeartor
[ https://issues.apache.org/jira/browse/FLINK-27009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520062#comment-17520062 ] Yufei Zhang commented on FLINK-27009: - I agree, submitting SQL jobs in application mode seems a big need for many users. Would be great to see a discussion in ML. > Support SQL job submission in flink kubernetes opeartor > --- > > Key: FLINK-27009 > URL: https://issues.apache.org/jira/browse/FLINK-27009 > Project: Flink > Issue Type: New Feature > Components: Kubernetes Operator >Reporter: Biao Geng >Priority: Major > > Currently, the flink kubernetes opeartor is for jar job using application or > session cluster. For SQL job, there is no out of box solution in the > operator. > One simple and short-term solution is to wrap the SQL script into a jar job > using table API with limitation. > The long-term solution may work with > [FLINK-26541|https://issues.apache.org/jira/browse/FLINK-26541] to achieve > the full support. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FLINK-26645) Pulsar Source subscribe to a single topic partition will consume all partitions from that topic
Yufei Zhang created FLINK-26645: --- Summary: Pulsar Source subscribe to a single topic partition will consume all partitions from that topic Key: FLINK-26645 URL: https://issues.apache.org/jira/browse/FLINK-26645 Project: Flink Issue Type: Bug Components: Connectors / Pulsar Affects Versions: 1.14.4, 1.15.0 Reporter: Yufei Zhang Fix For: 1.15.0, 1.14.4 Say users subscribe to 4 partitions of a topic with 16 partitions, current Pulsar source will actually consume from all 16 partitions. Expect to consume from 4 partitions only. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-26642) Pulsar sink fails with non-partitioned topic
[
https://issues.apache.org/jira/browse/FLINK-26642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506717#comment-17506717
]
Yufei Zhang commented on FLINK-26642:
-
Roger. I'll try to reproduce it.
> Pulsar sink fails with non-partitioned topic
>
>
> Key: FLINK-26642
> URL: https://issues.apache.org/jira/browse/FLINK-26642
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.15.0
>Reporter: goldenyang
>Priority: Major
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Flink support pulsar sink now in
> [FLINK-20732|https://issues.apache.org/jira/browse/FLINK-20732]. I
> encountered a problem when using pulsar sink in master branch, when I use
> non-partitioned topic.
> The current test found that both partitioned topics and non-partitioned
> topics ending with -partition-i can be supported, but ordinary
> non-partitioned topics without -partition-i will have problems, such as
> 'test_topic'.
> Reproducing the problem requires writing to a non-partitioned topic. Below is
> the stack information when the exception is encountered. I briefly
> communicated with [~Jianyun Zhao] , this may be a bug.
>
> {code:java}
> 2022-03-08 21:39:13,622 - INFO -
> [flink-akka.actor.default-dispatcher-13:Execution@1419] - Source: Pulsar
> Source -> (Sink: Writer -> Sink: Committer, Sink: Print to Std. Out) (1/6)
> (44af5e8a2b9d553952c7ed3e5d40e672) switched from RUNNING to FAILED on
> 54284e57-42a9-4e2e-9c41-54b0ad559832 @ 127.0.0.1
> (dataPort=-1).java.lang.IllegalArgumentException: You should provide topics
> for routing topic by message key hash.at
> org.apache.flink.shaded.guava30.com.google.common.base.Preconditions.checkArgument(Preconditions.java:144)at
>
> org.apache.flink.connector.pulsar.sink.writer.router.RoundRobinTopicRouter.route(RoundRobinTopicRouter.java:54)at
>
> org.apache.flink.connector.pulsar.sink.writer.PulsarWriter.write(PulsarWriter.java:138)at
>
> org.apache.flink.streaming.runtime.operators.sink.SinkWriterOperator.processElement(SinkWriterOperator.java:124)at
>
> org.apache.flink.streaming.runtime.tasks.CopyingChainingOutput.pushToOperator(CopyingChainingOutput.java:82)at
>
> org.apache.flink.streaming.runtime.tasks.CopyingChainingOutput.collect(CopyingChainingOutput.java:57)at
>
> org.apache.flink.streaming.runtime.tasks.CopyingChainingOutput.collect(CopyingChainingOutput.java:29)at
>
> org.apache.flink.streaming.runtime.tasks.BroadcastingOutputCollector.collect(BroadcastingOutputCollector.java:77)at
>
> org.apache.flink.streaming.runtime.tasks.BroadcastingOutputCollector.collect(BroadcastingOutputCollector.java:32)at
>
> org.apache.flink.streaming.runtime.tasks.SourceOperatorStreamTask$AsyncDataOutputToOutput.emitRecord(SourceOperatorStreamTask.java:205)at
>
> org.apache.flink.streaming.api.operators.source.SourceOutputWithWatermarks.collect(SourceOutputWithWatermarks.java:110)at
>
> org.apache.flink.connector.pulsar.source.reader.emitter.PulsarRecordEmitter.emitRecord(PulsarRecordEmitter.java:41)at
>
> org.apache.flink.connector.pulsar.source.reader.emitter.PulsarRecordEmitter.emitRecord(PulsarRecordEmitter.java:33)at
>
> org.apache.flink.connector.base.source.reader.SourceReaderBase.pollNext(SourceReaderBase.java:143)at
>
> org.apache.flink.connector.pulsar.source.reader.source.PulsarOrderedSourceReader.pollNext(PulsarOrderedSourceReader.java:106)at
>
> org.apache.flink.streaming.api.operators.SourceOperator.emitNext(SourceOperator.java:382)at
>
> org.apache.flink.streaming.runtime.io.StreamTaskSourceInput.emitNext(StreamTaskSourceInput.java:68)at
>
> org.apache.flink.streaming.runtime.io.StreamOneInputProcessor.processInput(StreamOneInputProcessor.java:65)at
>
> org.apache.flink.streaming.runtime.tasks.StreamTask.processInput(StreamTask.java:519)at
>
> org.apache.flink.streaming.runtime.tasks.mailbox.MailboxProcessor.runMailboxLoop(MailboxProcessor.java:203)at
>
> org.apache.flink.streaming.runtime.tasks.StreamTask.runMailboxLoop(StreamTask.java:804)at
>
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:753)at
>
> org.apache.flink.runtime.taskmanager.Task.runWithSystemExitMonitoring(Task.java:948)at
> org.apache.flink.runtime.taskmanager.Task.restoreAndInvoke(Task.java:927)at
> org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:741)at
> org.apache.flink.runtime.taskmanager.Task.run(Task.java:563)at
> java.lang.Thread.run(Thread.java:748) {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FLINK-26192) PulsarOrderedSourceReaderTest fails with exit code 255
[
https://issues.apache.org/jira/browse/FLINK-26192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493800#comment-17493800
]
Yufei Zhang commented on FLINK-26192:
-
Got it, I'll bring this issue up with my team tomorrow~ Thanks for your advice
~ We'll try our best to solve it soon.
> PulsarOrderedSourceReaderTest fails with exit code 255
> --
>
> Key: FLINK-26192
> URL: https://issues.apache.org/jira/browse/FLINK-26192
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.15.0
>Reporter: Dawid Wysakowicz
>Assignee: Chesnay Schepler
>Priority: Major
> Labels: pull-request-available
>
> https://dev.azure.com/wysakowiczdawid/Flink/_build/results?buildId=1367=logs=f3dc9b18-b77a-55c1-591e-264c46fe44d1=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d=26787
> {code}
> Feb 16 13:49:46 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
> on project flink-connector-pulsar: There are test failures.
> Feb 16 13:49:46 [ERROR]
> Feb 16 13:49:46 [ERROR] Please refer to
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire-reports for
> the individual test results.
> Feb 16 13:49:46 [ERROR] Please refer to dump files (if any exist)
> [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
> Feb 16 13:49:46 [ERROR] The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> Feb 16 13:49:46 [ERROR] Command was /bin/sh -c cd
> /__w/1/s/flink-connectors/flink-connector-pulsar &&
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xms256m -Xmx2048m
> -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -Duser.country=US -Duser.language=en -jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire/surefirebooter3139517882560779643.jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire
> 2022-02-16T13-48-34_435-jvmRun1 surefire3358354372075396323tmp
> surefire_08509996975514960300tmp
> Feb 16 13:49:46 [ERROR] Error occurred in starting fork, check output in log
> Feb 16 13:49:46 [ERROR] Process Exit Code: 255
> Feb 16 13:49:46 [ERROR]
> org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM
> terminated without properly saying goodbye. VM crash or System.exit called?
> Feb 16 13:49:46 [ERROR] Command was /bin/sh -c cd
> /__w/1/s/flink-connectors/flink-connector-pulsar &&
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xms256m -Xmx2048m
> -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -Duser.country=US -Duser.language=en -jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire/surefirebooter3139517882560779643.jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire
> 2022-02-16T13-48-34_435-jvmRun1 surefire3358354372075396323tmp
> surefire_08509996975514960300tmp
> Feb 16 13:49:46 [ERROR] Error occurred in starting fork, check output in log
> Feb 16 13:49:46 [ERROR] Process Exit Code: 255
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> Feb 16 13:49:46 [ERROR] at
>
[jira] [Commented] (FLINK-26211) PulsarSourceUnorderedE2ECase failed on azure due to multiple causes
[
https://issues.apache.org/jira/browse/FLINK-26211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493786#comment-17493786
]
Yufei Zhang commented on FLINK-26211:
-
This seems to be a duplicate of FLINK-26210.
> 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
>Priority: Critical
> Labels: test-stability
>
> {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=logs=6e8542d7-de38-5a33-4aca-458d6c87066d=5846934b-7a4f-545b-e5b0-eb4d8bda32e1=15537
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FLINK-26192) PulsarOrderedSourceReaderTest fails with exit code 255
[
https://issues.apache.org/jira/browse/FLINK-26192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493777#comment-17493777
]
Yufei Zhang commented on FLINK-26192:
-
This looked to me the test VM crashed, let's keep observing it for a while, if
it does not happen again for 1 month, can we close it ?
> PulsarOrderedSourceReaderTest fails with exit code 255
> --
>
> Key: FLINK-26192
> URL: https://issues.apache.org/jira/browse/FLINK-26192
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.15.0
>Reporter: Dawid Wysakowicz
>Priority: Major
>
> https://dev.azure.com/wysakowiczdawid/Flink/_build/results?buildId=1367=logs=f3dc9b18-b77a-55c1-591e-264c46fe44d1=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d=26787
> {code}
> Feb 16 13:49:46 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
> on project flink-connector-pulsar: There are test failures.
> Feb 16 13:49:46 [ERROR]
> Feb 16 13:49:46 [ERROR] Please refer to
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire-reports for
> the individual test results.
> Feb 16 13:49:46 [ERROR] Please refer to dump files (if any exist)
> [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
> Feb 16 13:49:46 [ERROR] The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> Feb 16 13:49:46 [ERROR] Command was /bin/sh -c cd
> /__w/1/s/flink-connectors/flink-connector-pulsar &&
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xms256m -Xmx2048m
> -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -Duser.country=US -Duser.language=en -jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire/surefirebooter3139517882560779643.jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire
> 2022-02-16T13-48-34_435-jvmRun1 surefire3358354372075396323tmp
> surefire_08509996975514960300tmp
> Feb 16 13:49:46 [ERROR] Error occurred in starting fork, check output in log
> Feb 16 13:49:46 [ERROR] Process Exit Code: 255
> Feb 16 13:49:46 [ERROR]
> org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM
> terminated without properly saying goodbye. VM crash or System.exit called?
> Feb 16 13:49:46 [ERROR] Command was /bin/sh -c cd
> /__w/1/s/flink-connectors/flink-connector-pulsar &&
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xms256m -Xmx2048m
> -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -Duser.country=US -Duser.language=en -jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire/surefirebooter3139517882560779643.jar
> /__w/1/s/flink-connectors/flink-connector-pulsar/target/surefire
> 2022-02-16T13-48-34_435-jvmRun1 surefire3358354372075396323tmp
> surefire_08509996975514960300tmp
> Feb 16 13:49:46 [ERROR] Error occurred in starting fork, check output in log
> Feb 16 13:49:46 [ERROR] Process Exit Code: 255
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> Feb 16 13:49:46 [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> Feb 16 13:49:46 [ERROR] at
>
[jira] [Created] (FLINK-26203) Support Table API in Pulsar Sink Connector
Yufei Zhang created FLINK-26203: --- Summary: Support Table API in Pulsar Sink Connector Key: FLINK-26203 URL: https://issues.apache.org/jira/browse/FLINK-26203 Project: Flink Issue Type: New Feature Components: Connectors / Pulsar Reporter: Yufei Zhang Currently Pulsar connector only supports DataStream API. We plan to support Table API as well. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FLINK-26202) Support Table API in Pulsar Source Connector
Yufei Zhang created FLINK-26202: --- Summary: Support Table API in Pulsar Source Connector Key: FLINK-26202 URL: https://issues.apache.org/jira/browse/FLINK-26202 Project: Flink Issue Type: New Feature Components: Connectors / Pulsar Affects Versions: 1.15.0 Reporter: Yufei Zhang Currently pulsar connector only supports DataStream API, we plan to support Table API. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (FLINK-26161) Pulsar Connector: edge case: splits should be added to finishedSplits if was empty from beginning
[
https://issues.apache.org/jira/browse/FLINK-26161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yufei Zhang closed FLINK-26161.
---
Resolution: Invalid
When I look back at this issue, I think I had some misunderstanding at the
beginning. If the partitionSplit is empty, it will still enter the for loop. It
is empty at the beginning does not mean it will always be empty during the
polling. I'll close this issue.
> Pulsar Connector: edge case: splits should be added to finishedSplits if was
> empty from beginning
> -
>
> Key: FLINK-26161
> URL: https://issues.apache.org/jira/browse/FLINK-26161
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Reporter: Yufei Zhang
>Priority: Minor
> Labels: Pulsar
>
> Currently we add a split to finishedSplit in the read for loop, but if the
> split is empty and never enters for loop it should be checked whether to add
> to finishedSplit as well. This is an edge case and priority is low.
>
> {{// current code}}
> {{if (stopCursor.shouldStop(message)) {
> builder.addFinishedSplit(splitId);break;
> }}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FLINK-26161) Pulsar Connector: edge case: splits should be added to finishedSplits if was empty from beginning
[
https://issues.apache.org/jira/browse/FLINK-26161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17492635#comment-17492635
]
Yufei Zhang commented on FLINK-26161:
-
When I look back at this issue, I think I had some misunderstanding at the
beginning. If the partitionSplit is empty, it will still enter the for loop. It
is empty at the beginning does not mean it will always be empty during the
polling. I'll close this issue.
> Pulsar Connector: edge case: splits should be added to finishedSplits if was
> empty from beginning
> -
>
> Key: FLINK-26161
> URL: https://issues.apache.org/jira/browse/FLINK-26161
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Reporter: Yufei Zhang
>Priority: Minor
> Labels: Pulsar
>
> Currently we add a split to finishedSplit in the read for loop, but if the
> split is empty and never enters for loop it should be checked whether to add
> to finishedSplit as well. This is an edge case and priority is low.
>
> {{// current code}}
> {{if (stopCursor.shouldStop(message)) {
> builder.addFinishedSplit(splitId);break;
> }}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (FLINK-26161) Pulsar Connector: edge case: splits should be added to finishedSplits if was empty from beginning
Yufei Zhang created FLINK-26161:
---
Summary: Pulsar Connector: edge case: splits should be added to
finishedSplits if was empty from beginning
Key: FLINK-26161
URL: https://issues.apache.org/jira/browse/FLINK-26161
Project: Flink
Issue Type: Bug
Components: Connectors / Pulsar
Reporter: Yufei Zhang
Currently we add a split to finishedSplit in the read for loop, but if the
split is empty and never enters for loop it should be checked whether to add to
finishedSplit as well. This is an edge case and priority is low.
{{// current code}}
{{if (stopCursor.shouldStop(message)) {
builder.addFinishedSplit(splitId);break;
}}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (FLINK-26160) Pulsar Connector: stopCursor description should be changed. Connector only stop when auto discovery is disabled.
Yufei Zhang created FLINK-26160: --- Summary: Pulsar Connector: stopCursor description should be changed. Connector only stop when auto discovery is disabled. Key: FLINK-26160 URL: https://issues.apache.org/jira/browse/FLINK-26160 Project: Flink Issue Type: Bug Components: Connectors / Pulsar Reporter: Yufei Zhang In Pulsar source connector, the stopCursor description can mislead user to believe that the source connector will exit if a BoundedStopCursor is set. However this might not be true if auto partition discovery is enabled (the discovery loop will always run and expects new partitionSplits). We need to modify the description. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FLINK-26159) Pulsar Connector: should add description MAX_FETCH_RECORD in doc to explain slow consumption
Yufei Zhang created FLINK-26159: --- Summary: Pulsar Connector: should add description MAX_FETCH_RECORD in doc to explain slow consumption Key: FLINK-26159 URL: https://issues.apache.org/jira/browse/FLINK-26159 Project: Flink Issue Type: Bug Components: Connectors / Pulsar Reporter: Yufei Zhang Pulsar source connector can consume slow when the data volume is low (like 1 record/s), this is because the MAX_FETCH_RECORD is set to 100 by default, meaning that the pulsar source emits records either after a timeout (1s) or buffered messages has reached 100. Users will observe each message has a 1s delay. This can be add to the documentation and inform users how to change MAX_FETCH_RECORD -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-25686) Support Pulsar Schema evolution in Pulsar Source Connector
[ https://issues.apache.org/jira/browse/FLINK-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Zhang updated FLINK-25686: Summary: Support Pulsar Schema evolution in Pulsar Source Connector (was: Support Pulsar Schema evolution in Pulsar Connector) > Support Pulsar Schema evolution in Pulsar Source Connector > -- > > Key: FLINK-25686 > URL: https://issues.apache.org/jira/browse/FLINK-25686 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / Pulsar >Reporter: Yufei Zhang >Assignee: Yufei Zhang >Priority: Minor > Labels: Pulsar, pull-request-available > > Currently the source connector reads all messages as Message, and > implements a deserialization abstraction to deserialize the byte array > message. This deserialization abstraction supports both flink schema and > pulsar schema. However because of this extra layer of abstraction, even when > using pulsar schema, the schema info is not provided to the consumer > (client), so it is not using any pulsar’s schema validation mechanism. (If > pulsar client has a schema, it will send the schema to broker on connect and > broker will validate if it is a valid schema according to a preset > compatibility rule :[ > https://pulsar.apache.org/docs/en/schema-evolution-compatibility/|https://pulsar.apache.org/docs/en/schema-evolution-compatibility/]). > we need to support this schema evolution -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-25686) Support Pulsar Schema evolution in Pulsar Connector
[ https://issues.apache.org/jira/browse/FLINK-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477605#comment-17477605 ] Yufei Zhang commented on FLINK-25686: - Please assign this ticket to me [~fpaul] ~ Thank you ! > Support Pulsar Schema evolution in Pulsar Connector > --- > > Key: FLINK-25686 > URL: https://issues.apache.org/jira/browse/FLINK-25686 > Project: Flink > Issue Type: New Feature > Components: Connectors / Pulsar >Reporter: Yufei Zhang >Priority: Minor > Labels: Pulsar > > Currently the source connector reads all messages as Message, and > implements a deserialization abstraction to deserialize the byte array > message. This deserialization abstraction supports both flink schema and > pulsar schema. However because of this extra layer of abstraction, even when > using pulsar schema, the schema info is not provided to the consumer > (client), so it is not using any pulsar’s schema validation mechanism. (If > pulsar client has a schema, it will send the schema to broker on connect and > broker will validate if it is a valid schema according to a preset > compatibility rule :[ > https://pulsar.apache.org/docs/en/schema-evolution-compatibility/|https://pulsar.apache.org/docs/en/schema-evolution-compatibility/]). > we need to support this schema evolution -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FLINK-25686) Support Pulsar Schema evolution in Pulsar Connector
Yufei Zhang created FLINK-25686: --- Summary: Support Pulsar Schema evolution in Pulsar Connector Key: FLINK-25686 URL: https://issues.apache.org/jira/browse/FLINK-25686 Project: Flink Issue Type: New Feature Components: Connectors / Pulsar Reporter: Yufei Zhang Currently the source connector reads all messages as Message, and implements a deserialization abstraction to deserialize the byte array message. This deserialization abstraction supports both flink schema and pulsar schema. However because of this extra layer of abstraction, even when using pulsar schema, the schema info is not provided to the consumer (client), so it is not using any pulsar’s schema validation mechanism. (If pulsar client has a schema, it will send the schema to broker on connect and broker will validate if it is a valid schema according to a preset compatibility rule :[ https://pulsar.apache.org/docs/en/schema-evolution-compatibility/|https://pulsar.apache.org/docs/en/schema-evolution-compatibility/]). we need to support this schema evolution -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-25440) Apache Pulsar Connector Document description error about 'Starting Position'.
[ https://issues.apache.org/jira/browse/FLINK-25440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474583#comment-17474583 ] Yufei Zhang commented on FLINK-25440: - I can take up this ticket, would someone assign this to me ? Thanks ! > Apache Pulsar Connector Document description error about 'Starting Position'. > - > > Key: FLINK-25440 > URL: https://issues.apache.org/jira/browse/FLINK-25440 > Project: Flink > Issue Type: Bug > Components: Documentation >Affects Versions: 1.14.2 >Reporter: xiechenling >Priority: Minor > > Starting Position description error. > Start from the specified message time by Message.getEventTime(). > StartCursor.fromMessageTime(long) > it should be 'Start from the specified message time by publishTime.' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-23944) PulsarSourceITCase.testTaskManagerFailure is instable
[
https://issues.apache.org/jira/browse/FLINK-23944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474404#comment-17474404
]
Yufei Zhang commented on FLINK-23944:
-
I failed to find a way to trigger this failure case 100%. I had some
observations: # the mismatch begins in the middle. (not necessarily from the
start)
# It only happens in the second send and write after the failover call.
# The first send and write always succeed (at least from the reported
pipelines)
Since we cannot reproduce this reliably, my suggestion is to first determine
whether it's caused by data loss or ordering. (I think it's most likely data
loss, but can't confirm).So I would suggest: # assert on the size of the result
set first, and then compare ordering so we can know if this mismatch is caused
by data loss or wrong ordering or both.
# eliminate undeterministic test data. Currently in the
generateStringTestData() we generate random strings, and it's better to avoid
undeterminism in testing (except in random testing). We can add more debugging
info in the test string so we can better debug the issue next time it occurs.
What do you think [~syhily]
> PulsarSourceITCase.testTaskManagerFailure is instable
> -
>
> Key: FLINK-23944
> URL: https://issues.apache.org/jira/browse/FLINK-23944
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.14.0
>Reporter: Dian Fu
>Assignee: Yufan Sheng
>Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.15.0
>
>
> [https://dev.azure.com/dianfu/Flink/_build/results?buildId=430=logs=f3dc9b18-b77a-55c1-591e-264c46fe44d1=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d]
> It's from my personal azure pipeline, however, I'm pretty sure that I have
> not touched any code related to this.
> {code:java}
> Aug 24 10:44:13 [ERROR] testTaskManagerFailure{TestEnvironment,
> ExternalContext, ClusterControllable}[1] Time elapsed: 258.397 s <<< FAILURE!
> Aug 24 10:44:13 java.lang.AssertionError: Aug 24 10:44:13 Aug 24 10:44:13
> Expected: Records consumed by Flink should be identical to test data and
> preserve the order in split Aug 24 10:44:13 but: Mismatched record at
> position 7: Expected '0W6SzacX7MNL4xLL3BZ8C3ljho4iCydbvxIl' but was
> 'wVi5JaJpNvgkDEOBRC775qHgw0LyRW2HBxwLmfONeEmr' Aug 24 10:44:13 at
> org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) Aug 24 10:44:13
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8) Aug 24
> 10:44:13 at
> org.apache.flink.connectors.test.common.testsuites.SourceTestSuiteBase.testTaskManagerFailure(SourceTestSuiteBase.java:271)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FLINK-23944) PulsarSourceITCase.testTaskManagerFailure is instable
[
https://issues.apache.org/jira/browse/FLINK-23944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474282#comment-17474282
]
Yufei Zhang commented on FLINK-23944:
-
I'll try to investigate
> PulsarSourceITCase.testTaskManagerFailure is instable
> -
>
> Key: FLINK-23944
> URL: https://issues.apache.org/jira/browse/FLINK-23944
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.14.0
>Reporter: Dian Fu
>Assignee: Yufan Sheng
>Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.15.0
>
>
> [https://dev.azure.com/dianfu/Flink/_build/results?buildId=430=logs=f3dc9b18-b77a-55c1-591e-264c46fe44d1=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d]
> It's from my personal azure pipeline, however, I'm pretty sure that I have
> not touched any code related to this.
> {code:java}
> Aug 24 10:44:13 [ERROR] testTaskManagerFailure{TestEnvironment,
> ExternalContext, ClusterControllable}[1] Time elapsed: 258.397 s <<< FAILURE!
> Aug 24 10:44:13 java.lang.AssertionError: Aug 24 10:44:13 Aug 24 10:44:13
> Expected: Records consumed by Flink should be identical to test data and
> preserve the order in split Aug 24 10:44:13 but: Mismatched record at
> position 7: Expected '0W6SzacX7MNL4xLL3BZ8C3ljho4iCydbvxIl' but was
> 'wVi5JaJpNvgkDEOBRC775qHgw0LyRW2HBxwLmfONeEmr' Aug 24 10:44:13 at
> org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) Aug 24 10:44:13
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8) Aug 24
> 10:44:13 at
> org.apache.flink.connectors.test.common.testsuites.SourceTestSuiteBase.testTaskManagerFailure(SourceTestSuiteBase.java:271)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (FLINK-25159) Streamline E2E surefire configuration setup
[ https://issues.apache.org/jira/browse/FLINK-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459641#comment-17459641 ] Yufei Zhang edited comment on FLINK-25159 at 12/15/21, 4:40 AM: [~chesnay] Hi Chesnay, do you know how to configure the pipeline to run only one e2e tests ? I'm searching to run only pulsar e2e tests on pipeline. Thank you ~ EDIT: I currently only include puslar e2e in my testing pipeline in the surefire plugin, but wondering if there is a better way to do it EDIT2: also wondering what is the difference between e2e_1_ci_build and e2e_2_ci_build in the pipeline was (Author: affe): [~chesnay] Hi Chesnay, do you know how to configure the pipeline to run only one e2e tests ? I'm searching to run only pulsar e2e tests on pipeline. Thank you ~ EDIT: I currently only include puslar e2e in my testing pipeline in the surefire plugin, but wondering if there is a better way to do it > Streamline E2E surefire configuration setup > --- > > Key: FLINK-25159 > URL: https://issues.apache.org/jira/browse/FLINK-25159 > Project: Flink > Issue Type: Technical Debt > Components: Build System, Tests >Reporter: Chesnay Schepler >Assignee: Chesnay Schepler >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Our current surefire setup for the Java E2E tests is exceedingly complicated, > because of when it was introduced we split the e2e tests across separate > profiles. > This is at least currently not necessary. > Additionally, it appears that not many people are aware of this setup, which > has resulted in various tests for pulsar, pubsub, kinesis and kafka (and > maybe others) to not even being run on CI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (FLINK-25159) Streamline E2E surefire configuration setup
[ https://issues.apache.org/jira/browse/FLINK-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459641#comment-17459641 ] Yufei Zhang edited comment on FLINK-25159 at 12/15/21, 4:37 AM: [~chesnay] Hi Chesnay, do you know how to configure the pipeline to run only one e2e tests ? I'm searching to run only pulsar e2e tests on pipeline. Thank you ~ EDIT: I currently only include puslar e2e in my testing pipeline in the surefire plugin, but wondering if there is a better way to do it was (Author: affe): [~chesnay] Hi Chesnay, do you know how to configure the pipeline to run only one e2e tests ? I'm searching to run only pulsar e2e tests on pipeline. Thank you ~ > Streamline E2E surefire configuration setup > --- > > Key: FLINK-25159 > URL: https://issues.apache.org/jira/browse/FLINK-25159 > Project: Flink > Issue Type: Technical Debt > Components: Build System, Tests >Reporter: Chesnay Schepler >Assignee: Chesnay Schepler >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Our current surefire setup for the Java E2E tests is exceedingly complicated, > because of when it was introduced we split the e2e tests across separate > profiles. > This is at least currently not necessary. > Additionally, it appears that not many people are aware of this setup, which > has resulted in various tests for pulsar, pubsub, kinesis and kafka (and > maybe others) to not even being run on CI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-25159) Streamline E2E surefire configuration setup
[ https://issues.apache.org/jira/browse/FLINK-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459641#comment-17459641 ] Yufei Zhang commented on FLINK-25159: - [~chesnay] Hi Chesnay, do you know how to configure the pipeline to run only one e2e tests ? I'm searching to run only pulsar e2e tests on pipeline. Thank you ~ > Streamline E2E surefire configuration setup > --- > > Key: FLINK-25159 > URL: https://issues.apache.org/jira/browse/FLINK-25159 > Project: Flink > Issue Type: Technical Debt > Components: Build System, Tests >Reporter: Chesnay Schepler >Assignee: Chesnay Schepler >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Our current surefire setup for the Java E2E tests is exceedingly complicated, > because of when it was introduced we split the e2e tests across separate > profiles. > This is at least currently not necessary. > Additionally, it appears that not many people are aware of this setup, which > has resulted in various tests for pulsar, pubsub, kinesis and kafka (and > maybe others) to not even being run on CI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-25210) PulsarSource(Un)OrderedE2ECase is broken
[
https://issues.apache.org/jira/browse/FLINK-25210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459591#comment-17459591
]
Yufei Zhang commented on FLINK-25210:
-
[~trohrmann] Yeah, please assign this ticket to me
> PulsarSource(Un)OrderedE2ECase is broken
>
>
> Key: FLINK-25210
> URL: https://issues.apache.org/jira/browse/FLINK-25210
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Pulsar, Tests
>Affects Versions: 1.15.0
>Reporter: Chesnay Schepler
>Priority: Blocker
> Labels: test-stability
> Fix For: 1.15.0
>
>
> https://dev.azure.com/chesnay/flink/_build/results?buildId=1884=logs=0e31ee24-31a6-528c-a4bf-45cde9b2a14e=ff03a8fa-e84e-5199-efb2-5433077ce8e2
> {code:java}
> Dec 06 16:00:33 [ERROR]
> org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase Time
> elapsed: 58.114 s <<< ERROR!
> Dec 06 16:00:33 java.lang.IllegalArgumentException: Resource with path
> containers/txnStandalone.conf could not be found on any of these
> classloaders: [sun.misc.Launcher$AppClassLoader@3d4eac69]
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.getClasspathResource(MountableFile.java:151)
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.forClasspathResource(MountableFile.java:97)
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.forClasspathResource(MountableFile.java:66)
> Dec 06 16:00:33 at
> org.testcontainers.containers.GenericContainer.withClasspathResourceMapping(GenericContainer.java:1233)
> Dec 06 16:00:33 at
> org.testcontainers.containers.GenericContainer.withClasspathResourceMapping(GenericContainer.java:1225)
> Dec 06 16:00:33 at
> org.apache.flink.connector.pulsar.testutils.runtime.container.PulsarContainerRuntime.startUp(PulsarContainerRuntime.java:76)
> Dec 06 16:00:33 at
> org.apache.flink.connector.pulsar.testutils.PulsarTestEnvironment.startUp(PulsarTestEnvironment.java:96)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FLINK-25182) NoClassDefFoundError of PulsarAdminImpl by using flink-connector-pulsar:1.14 on k8s flink cluster
[ https://issues.apache.org/jira/browse/FLINK-25182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457059#comment-17457059 ] Yufei Zhang commented on FLINK-25182: - [~forsake0120] Hi, Looks like the issue has been resolved, would you mind comment on the root cause and close this issue ? Thank you so much~ > NoClassDefFoundError of PulsarAdminImpl by using flink-connector-pulsar:1.14 > on k8s flink cluster > - > > Key: FLINK-25182 > URL: https://issues.apache.org/jira/browse/FLINK-25182 > Project: Flink > Issue Type: Bug > Components: Connectors / Pulsar >Affects Versions: 1.14.0 > Environment: * Flink: HA cluster on k8s > * Flink Mode: session > * Version: Flink 1.14.0 > * Connector: flink-connector-pulsar_2.11:1.14.0 > * Pulsar cluster: ( by StreamNative' s helm charts) > * broker version: 2.8.0.8 > * bookie version: 2.7.2.8 > * pulsar proxy: 2.8.0.8 >Reporter: HeYe >Priority: Major > Attachments: image-2021-12-06-16-09-12-816.png, > image-2021-12-06-16-09-52-042.png, image-2021-12-06-16-10-13-697.png > > > NoClassDefFoundError of PulsarAdminImpl by using flink-connector-pulsar:1.14 > on k8s flink cluster > > Flink: Session mode in HA cluster on k8s > Version: Flink 1.14.0 > Connector: flink-connector-pulsar_2.11:1.14.0 > > The connector is worked by using IntelliJ IDEA, but meets exception on dev > k8s clusters, the exception please check screenshot > !image-2021-12-06-16-09-12-816.png! > !image-2021-12-06-16-09-52-042.png! > !image-2021-12-06-16-10-13-697.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (FLINK-25210) PulsarSource(Un)OrderedE2ECase is broken
[
https://issues.apache.org/jira/browse/FLINK-25210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454923#comment-17454923
]
Yufei Zhang edited comment on FLINK-25210 at 12/9/21, 4:37 AM:
---
CC [~chesnay] To reproduce/fix this, I guess I should use FLINK-25159's branch
as the base branch so the CI will actually run and create a new branch to debug
the E2E test.
was (Author: affe):
To reproduce/fix this, I guess I should use FLINK-25159's branch as the base
branch so the CI will actually run and create a new branch to debug the E2E
test.
> PulsarSource(Un)OrderedE2ECase is broken
>
>
> Key: FLINK-25210
> URL: https://issues.apache.org/jira/browse/FLINK-25210
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Pulsar, Tests
>Affects Versions: 1.15.0
>Reporter: Chesnay Schepler
>Priority: Blocker
> Fix For: 1.15.0
>
>
> https://dev.azure.com/chesnay/flink/_build/results?buildId=1884=logs=0e31ee24-31a6-528c-a4bf-45cde9b2a14e=ff03a8fa-e84e-5199-efb2-5433077ce8e2
> {code:java}
> Dec 06 16:00:33 [ERROR]
> org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase Time
> elapsed: 58.114 s <<< ERROR!
> Dec 06 16:00:33 java.lang.IllegalArgumentException: Resource with path
> containers/txnStandalone.conf could not be found on any of these
> classloaders: [sun.misc.Launcher$AppClassLoader@3d4eac69]
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.getClasspathResource(MountableFile.java:151)
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.forClasspathResource(MountableFile.java:97)
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.forClasspathResource(MountableFile.java:66)
> Dec 06 16:00:33 at
> org.testcontainers.containers.GenericContainer.withClasspathResourceMapping(GenericContainer.java:1233)
> Dec 06 16:00:33 at
> org.testcontainers.containers.GenericContainer.withClasspathResourceMapping(GenericContainer.java:1225)
> Dec 06 16:00:33 at
> org.apache.flink.connector.pulsar.testutils.runtime.container.PulsarContainerRuntime.startUp(PulsarContainerRuntime.java:76)
> Dec 06 16:00:33 at
> org.apache.flink.connector.pulsar.testutils.PulsarTestEnvironment.startUp(PulsarTestEnvironment.java:96)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FLINK-25159) Streamline E2E surefire configuration setup
[ https://issues.apache.org/jira/browse/FLINK-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454926#comment-17454926 ] Yufei Zhang commented on FLINK-25159: - Would you mind share the link to the currently in-progress branch ? I want to learn how to enable Pulsar E2E tests as described here. Thank you ! > Streamline E2E surefire configuration setup > --- > > Key: FLINK-25159 > URL: https://issues.apache.org/jira/browse/FLINK-25159 > Project: Flink > Issue Type: Improvement > Components: Build System, Tests >Reporter: Chesnay Schepler >Assignee: Chesnay Schepler >Priority: Major > Fix For: 1.15.0 > > > Our current surefire setup for the Java E2E tests is exceedingly complicated, > because of when it was introduced we split the e2e tests across separate > profiles. > This is at least currently not necessary. > Additionally, it appears that not many people are aware of this setup, which > has resulted in various tests for pulsar, pubsub, kinesis and kafka (and > maybe others) to not even being run on CI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-25210) PulsarSource(Un)OrderedE2ECase is brokern
[
https://issues.apache.org/jira/browse/FLINK-25210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454923#comment-17454923
]
Yufei Zhang commented on FLINK-25210:
-
To reproduce/fix this, I guess I should use FLINK-25159's branch as the base
branch so the CI will actually run and create a new branch to debug the E2E
test.
> PulsarSource(Un)OrderedE2ECase is brokern
> -
>
> Key: FLINK-25210
> URL: https://issues.apache.org/jira/browse/FLINK-25210
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Pulsar, Tests
>Affects Versions: 1.15.0
>Reporter: Chesnay Schepler
>Priority: Blocker
> Fix For: 1.15.0
>
>
> https://dev.azure.com/chesnay/flink/_build/results?buildId=1884=logs=0e31ee24-31a6-528c-a4bf-45cde9b2a14e=ff03a8fa-e84e-5199-efb2-5433077ce8e2
> {code:java}
> Dec 06 16:00:33 [ERROR]
> org.apache.flink.tests.util.pulsar.PulsarSourceUnorderedE2ECase Time
> elapsed: 58.114 s <<< ERROR!
> Dec 06 16:00:33 java.lang.IllegalArgumentException: Resource with path
> containers/txnStandalone.conf could not be found on any of these
> classloaders: [sun.misc.Launcher$AppClassLoader@3d4eac69]
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.getClasspathResource(MountableFile.java:151)
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.forClasspathResource(MountableFile.java:97)
> Dec 06 16:00:33 at
> org.testcontainers.utility.MountableFile.forClasspathResource(MountableFile.java:66)
> Dec 06 16:00:33 at
> org.testcontainers.containers.GenericContainer.withClasspathResourceMapping(GenericContainer.java:1233)
> Dec 06 16:00:33 at
> org.testcontainers.containers.GenericContainer.withClasspathResourceMapping(GenericContainer.java:1225)
> Dec 06 16:00:33 at
> org.apache.flink.connector.pulsar.testutils.runtime.container.PulsarContainerRuntime.startUp(PulsarContainerRuntime.java:76)
> Dec 06 16:00:33 at
> org.apache.flink.connector.pulsar.testutils.PulsarTestEnvironment.startUp(PulsarTestEnvironment.java:96)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (FLINK-25044) Add More Unit Test For Pulsar Source
Yufei Zhang created FLINK-25044: --- Summary: Add More Unit Test For Pulsar Source Key: FLINK-25044 URL: https://issues.apache.org/jira/browse/FLINK-25044 Project: Flink Issue Type: Improvement Components: Connectors / Pulsar Reporter: Yufei Zhang We should enhance the pulsar source connector tests by adding more unit tests. * SourceReader * SplitReader * Enumerator * SourceBuilder -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-25044) Add More Unit Test For Pulsar Source
[ https://issues.apache.org/jira/browse/FLINK-25044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448579#comment-17448579 ] Yufei Zhang commented on FLINK-25044: - I am currently working on this issue, feel free to assign it to me. > Add More Unit Test For Pulsar Source > > > Key: FLINK-25044 > URL: https://issues.apache.org/jira/browse/FLINK-25044 > Project: Flink > Issue Type: Improvement > Components: Connectors / Pulsar >Reporter: Yufei Zhang >Priority: Minor > Labels: testing > > We should enhance the pulsar source connector tests by adding more unit tests. > > * SourceReader > * SplitReader > * Enumerator > * SourceBuilder -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FLINK-24857) Upgrade SourceReaderTestBase to Use Junit 5
[ https://issues.apache.org/jira/browse/FLINK-24857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17441611#comment-17441611 ] Yufei Zhang commented on FLINK-24857: - Would be happy to help with this ticket~ > Upgrade SourceReaderTestBase to Use Junit 5 > --- > > Key: FLINK-24857 > URL: https://issues.apache.org/jira/browse/FLINK-24857 > Project: Flink > Issue Type: Technical Debt > Components: Test Infrastructure >Reporter: Yufei Zhang >Priority: Minor > Labels: test > > Currently SourceReaderTestBase uses Junit 4, it needs to be upgraded to Junit > 5 for new tests to use. > It affects two subclasses. > > * org/apache/flink/connector/kafka/source/reader/KafkaSourceReaderTest.java > * org/apache/flink/connector/base/source/reader/SourceReaderBaseTest.java > > These two classes needs to be fixed as well -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FLINK-24857) Upgrade SourceReaderTestBase to Use Junit 5
Yufei Zhang created FLINK-24857: --- Summary: Upgrade SourceReaderTestBase to Use Junit 5 Key: FLINK-24857 URL: https://issues.apache.org/jira/browse/FLINK-24857 Project: Flink Issue Type: Technical Debt Components: Test Infrastructure Reporter: Yufei Zhang Currently SourceReaderTestBase uses Junit 4, it needs to be upgraded to Junit 5 for new tests to use. It affects two subclasses. * org/apache/flink/connector/kafka/source/reader/KafkaSourceReaderTest.java * org/apache/flink/connector/base/source/reader/SourceReaderBaseTest.java These two classes needs to be fixed as well -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (FLINK-24856) Upgrade SourceReaderTestBase to Use Junit 5
[ https://issues.apache.org/jira/browse/FLINK-24856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Zhang closed FLINK-24856. --- Resolution: Invalid Cannot change assignee, will create from scratch. Sorry for any inconvenience > Upgrade SourceReaderTestBase to Use Junit 5 > --- > > Key: FLINK-24856 > URL: https://issues.apache.org/jira/browse/FLINK-24856 > Project: Flink > Issue Type: Technical Debt > Components: Test Infrastructure, Tests >Reporter: Yufei Zhang >Assignee: Martijn Visser >Priority: Minor > Fix For: 1.15.0 > > > We should update to the latest version of JUnit5, v5.8.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-24856) Upgrade SourceReaderTestBase to Use Junit 5
[ https://issues.apache.org/jira/browse/FLINK-24856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Zhang updated FLINK-24856: Labels: (was: pull-request-available) > Upgrade SourceReaderTestBase to Use Junit 5 > --- > > Key: FLINK-24856 > URL: https://issues.apache.org/jira/browse/FLINK-24856 > Project: Flink > Issue Type: Technical Debt > Components: Test Infrastructure, Tests >Reporter: Yufei Zhang >Assignee: Martijn Visser >Priority: Minor > Fix For: 1.15.0 > > > We should update to the latest version of JUnit5, v5.8.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FLINK-24856) Upgrade SourceReaderTestBase to Use Junit 5
Yufei Zhang created FLINK-24856: --- Summary: Upgrade SourceReaderTestBase to Use Junit 5 Key: FLINK-24856 URL: https://issues.apache.org/jira/browse/FLINK-24856 Project: Flink Issue Type: Technical Debt Components: Test Infrastructure, Tests Reporter: Yufei Zhang Assignee: Martijn Visser Fix For: 1.15.0 We should update to the latest version of JUnit5, v5.8.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
