Re: Resolving classpath problem with Pulsar IO and PulsarAdmin/PulsarClient

If we're going to use dependency injection on the Java side, I recommend using Dagger2 since it's much easier to maintain than other Java DI frameworks. I love DI, and I've thought about introducing it in Pulsar already. However, with that said, DI doesn't necessarily remove dependencies; it just m

Re: Resolving classpath problem with Pulsar IO and PulsarAdmin/PulsarClient

Enrico, I think there are a couple of different things coupled in this proposal. Let's make them clear before talking about dependency injection. 1) The main problem of PulsarAdmin is not dependency injection. The main problem is PulsarAdmin uses classes from 3rd party dependencies. PR#9842

Resolving classpath problem with Pulsar IO and PulsarAdmin/PulsarClient

Hello, currently in 2.8.0-SNAPSHOT we added an API to access PulsarAdmin from a Pulsar Sink Connector. The Api is Context.getPulsarAdmin and Context.getPulsarAdmin(clusterName) https://github.com/apache/pulsar/blob/0469dfe2c7804bd9ca9ea34e95d83b2196216cf9/pulsar-functions/api-java/src/main/java/o