Re: [Discuss] Separate Function API from Pub/Sub API for python client

2021-02-22 Thread Sijie Guo
Matteo - Thank you for providing the context! Yes. It is related to gRPC pulled by the state requirements. - Sijie On Mon, Feb 22, 2021 at 12:03 PM Matteo Merli wrote: > Yes, there are a bunch of dependencies that are only needed for state > store, such as the bk state store client and everyth

Re: [Discuss] Separate Function API from Pub/Sub API for python client

2021-02-22 Thread Matteo Merli
Yes, there are a bunch of dependencies that are only needed for state store, such as the bk state store client and everything it's pulling in, with the biggest offender being GRPC client lib. -- Matteo Merli On Mon, Feb 22, 2021 at 11:59 AM Sanjeev Kulkarni wrote: > > IIUC, its because of the

Re: [Discuss] Separate Function API from Pub/Sub API for python client

2021-02-22 Thread Sanjeev Kulkarni
IIUC, its because of the various state store related dependencies that are polluting this? On Mon, Feb 22, 2021 at 10:48 AM Jerry Peng wrote: > [ External sender. Exercise caution. ] > > Hi Sijie, > > Are you referring to the fact that the Pulsar python package (wheel > package) includes both pu

Re: [Discuss] Separate Function API from Pub/Sub API for python client

2021-02-22 Thread Jerry Peng
Hi Sijie, Are you referring to the fact that the Pulsar python package (wheel package) includes both pub/sub API and the function API? I If so, why are there a lot of dependencies being pulled in? For Pulsar Python Functions, shouldn't only the following files be pulled into the python package?

[Discuss] Separate Function API from Pub/Sub API for python client

2021-02-22 Thread Sijie Guo
Hi, Currently, the python pulsar client couples function API together with Pub/Sub API. That means the python client pulls in a lot of unnecessary dependencies for people who only use pub/sub API. As discussed in the community meeting last week, I am starting an email thread for discussing it. I