syhily commented on PR #91: URL: https://github.com/apache/flink-connector-pulsar/pull/91#issuecomment-2079354340
> > The pulsar-client-all should be upgrade to the 3.0.4 in the mean time. > > @syhily After `pulsar-client-all` was updated to 3.0.4, the unit test failed. I took a brief look and found that `publishTimeStopCursor` seemed to be connected to the consumer and then seek position, so consumer will be disconnect.Then after reconnecting the consumer, an exception of `Exclusive consumer is already connected` occurred. I think this requires more detailed investigation shows that this may be due to some changes in the internal implementation of pulsar-client-all due to version upgrades, and troubleshooting is not that easy. > > So I think it is worth using a separate PR to upgrade pulsar-client-all to version 3.0.4 and solve the problems caused by the related upgrade. > > This PR only solves the problem that the table api cannot find the bouncycastle class. > > Related error logs: [apache/flink-connector-pulsar/actions/runs/8832359197/job/24249517876?pr=91](https://github.com/apache/flink-connector-pulsar/actions/runs/8832359197/job/24249517876?pr=91) > > PTAL. Thanks. Thanks for your works. I think we can divide the work into two steps. Bump pulsar-client-all do require a lot of works. But since the pulsar-client-all depends on the legacy 15on. I think we can exclude these dependencies first in this PR and use 18on. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
