syhily commented on PR #51: URL: https://github.com/apache/flink-connector-pulsar/pull/51#issuecomment-1584935420
> I have one query regarding this, Do we really need pulsar client all here in flink connector pulsar ? Cant we just use the only pulsar client that is used , using pulsar client all will bring other client that is not required here . Looking forward to hear your opinion on it I'm quite willing to answer this question because a lot of people ask the same question while a lot of the hidden details is not well documented. Pulsar has two kinds of the Java client, the admin API and the client API. `pulsar-client` only contains the client API while our connector highly relies on the admin API to solve some bugs in client API and fulfil the missing features in client API. So we can't use the `pulsar-client` separately. Since the `pulsar-admin` and `pulsar-client` are both depending on a lot of duplicated dependencies. The only way to avoid the class conflicting and to have a clean dependency tree is just using the `pulsar-client-all`. We are planning to drop the admin API usage because it just exposes a lot of dangerous operation to the end users and a lot of permission issues occurred. But this should take a long time to accomplish the pulsar client. We are still on the way. -- 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]
