Re: [DISCUSS] PIP 29: One package for both pulsar client and pulsar admin

2019-02-11 Thread Matteo Merli
If the size difference is not that much, we could include that in `pulsar-client` too. (Perhaps moving the API part into `pulsar-client-api` as well. -- Matteo Merli On Sun, Feb 10, 2019 at 10:51 PM Enrico Olivelli wrote: > > As a new user I find this a great idea. > For the future I will be h

Re: [DISCUSS] PIP 29: One package for both pulsar client and pulsar admin

2019-02-10 Thread Enrico Olivelli
As a new user I find this a great idea. For the future I will be happy to see the admin API to be able to connect to the binary endpoint and not to the http one. Cheers Enrico Il giorno lun 11 feb 2019, 07:03 Sijie Guo ha scritto: > Hi all, > > Currently we are shipping `pulsar-client` and `pul

[DISCUSS] PIP 29: One package for both pulsar client and pulsar admin

2019-02-10 Thread Sijie Guo
Hi all, Currently we are shipping `pulsar-client` and `pulsar-client-admin` separately. They are both shaded packages. It is quite common to see applications using both `pulsar-client` and `pulsar-client-admin`. These applications will have redundant shaded classes in both `pulsar-client` and `pul