[jira] [Created] (FLINK-35328) AutoScale supports setting the maximum floating parallelism by the number of Pulsar partitions
Wenbing Shen created FLINK-35328: Summary: AutoScale supports setting the maximum floating parallelism by the number of Pulsar partitions Key: FLINK-35328 URL: https://issues.apache.org/jira/browse/FLINK-35328 Project: Flink Issue Type: Improvement Components: Kubernetes Operator Reporter: Wenbing Shen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35196) bouncycastle class not found for flink pulsar connector
Wenbing Shen created FLINK-35196: Summary: bouncycastle class not found for flink pulsar connector Key: FLINK-35196 URL: https://issues.apache.org/jira/browse/FLINK-35196 Project: Flink Issue Type: Bug Components: Connectors / Pulsar Affects Versions: pulsar-4.1.0 Reporter: Wenbing Shen 2024-04-22 14:45:48 java.lang.NoClassDefFoundError: org/apache/pulsar/shade/org/bouncycastle/util/Arrays at org.apache.flink.connector.pulsar.table.sink.PulsarWritableMetadata.readMetadata(PulsarWritableMetadata.java:67) at org.apache.flink.connector.pulsar.table.sink.PulsarWritableMetadata.applyWritableMetadataInMessage(PulsarWritableMetadata.java:55) at org.apache.flink.connector.pulsar.table.sink.PulsarTableSerializationSchema.serialize(PulsarTableSerializationSchema.java:106) at org.apache.flink.connector.pulsar.table.sink.PulsarTableSerializationSchema.serialize(PulsarTableSerializationSchema.java:40) at org.apache.flink.connector.pulsar.sink.writer.PulsarWriter.write(PulsarWriter.java:143) at org.apache.flink.streaming.runtime.operators.sink.SinkWriterOperator.processElement(SinkWriterOperator.java:160) at org.apache.flink.streaming.runtime.tasks.OneInputStreamTask$StreamTaskNetworkOutput.emitRecord(OneInputStreamTask.java:233) at org.apache.flink.streaming.runtime.io.AbstractStreamTaskNetworkInput.processElement(AbstractStreamTaskNetworkInput.java:134) at org.apache.flink.streaming.runtime.io.AbstractStreamTaskNetworkInput.emitNext(AbstractStreamTaskNetworkInput.java:105) at org.apache.flink.streaming.runtime.io.StreamOneInputProcessor.processInput(StreamOneInputProcessor.java:65) at org.apache.flink.streaming.runtime.tasks.StreamTask.processInput(StreamTask.java:542) at org.apache.flink.streaming.runtime.tasks.mailbox.MailboxProcessor.runMailboxLoop(MailboxProcessor.java:231) at org.apache.flink.streaming.runtime.tasks.StreamTask.runMailboxLoop(StreamTask.java:831) at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:780) at org.apache.flink.runtime.taskmanager.Task.runWithSystemExitMonitoring(Task.java:935) at org.apache.flink.runtime.taskmanager.Task.restoreAndInvoke(Task.java:914) at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:728) at org.apache.flink.runtime.taskmanager.Task.run(Task.java:550) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-29207) Pulsar message eventTime may be incorrectly set to a negative number
Wenbing Shen created FLINK-29207: Summary: Pulsar message eventTime may be incorrectly set to a negative number Key: FLINK-29207 URL: https://issues.apache.org/jira/browse/FLINK-29207 Project: Flink Issue Type: Bug Components: Connectors / Pulsar Affects Versions: 1.15.2 Reporter: Wenbing Shen Attachments: image-2022-09-06-17-20-27-220.png, image-2022-09-06-17-21-46-923.png We'd better judge that the timestamp is greater than 0, we should skip setting eventTime when timestamp less than or equal to 0, otherwise the pulsar client will throw an exception. !image-2022-09-06-17-21-46-923.png! !image-2022-09-06-17-20-27-220.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
