2018-05-10 11:10:49 UTC - Daniel Ferreira Jorge: Hi, is the issue <https://github.com/apache/incubator-pulsar/issues/1069> already on the python client? I could not find any docs regarding the settings. Thanks ---- 2018-05-10 11:12:18 UTC - Sijie Guo: @Daniel Ferreira Jorge not yet, it is in Java client only. We have bunch of features to catch-up in c++ / python client in 2.1 release. ---- 2018-05-10 11:12:41 UTC - Sijie Guo: 2.1 is a one-month release ---- 2018-05-10 11:12:59 UTC - Sijie Guo: Hopefully we can get them in cpp and python clients ---- 2018-05-10 11:13:18 UTC - Daniel Ferreira Jorge: @Sijie Guo Ok, thanks! ---- 2018-05-10 12:55:29 UTC - Daniel Ferreira Jorge: Hi, I'm taking a look on pulsar functions and it looks awesome! I have some questions: 1. What versions of python does it support? 2. What would be the recommended way to manage python requirements (pip) as of now? ---- 2018-05-10 14:28:32 UTC - Ntale Lukama: @Ntale Lukama has joined the channel ---- 2018-05-10 14:32:02 UTC - Ntale Lukama: We are implementing Pulsar for on of our use cases and I am looking into various failure scenarios for Pulsar and mitigation strategies... What are the ones I should definitely consider? ---- 2018-05-10 18:10:32 UTC - Jon Bock: @Senthilkumar Kalaiselvan: You can read the writeup of a third party’s results running the OpenMessaging benchmark with Kafka and Pulsar here: <https://info.streaml.io/benchmarking-streaming-messaging-platforms>
This was on an untuned environment using an earlier version of Pulsar, there have been significant performance improvements then (especially in 2.0) that I’d expect you to see if you run the benchmark yourself. ---- 2018-05-10 18:24:26 UTC - Ali Ahmed: @Daniel Ferreira Jorge 1) We support both python 2 and python 3 2) For now the worker nodes should have the functions dependencies installed on the the host with pip if you prefer. In future version we will consider pex and docker support so python bundles with dependencies can we submitted to workers ---- 2018-05-10 19:56:49 UTC - Sanjeev Kulkarni: @Ntale Lukama what failure scenarios are you talking about. The primary ones that I see are broker/bookie machine failures ---- 2018-05-10 19:57:24 UTC - Ntale Lukama: components failure within Pulsar ---- 2018-05-10 19:57:54 UTC - Sanjeev Kulkarni: on a broker failure, any topics that are being handled by that broker are switched automatically to another broker within milliseconds. And this will be handled transparently by the pulsar client ---- 2018-05-10 19:58:32 UTC - Sanjeev Kulkarni: so user shouldn’t notice anything other than momentary pause in publishing/consuming ---- 2018-05-10 19:58:46 UTC - Karthik Ramasamy: @Ntale Lukama - here are the relevant slides ---- 2018-05-10 19:58:48 UTC - Karthik Ramasamy: <https://www.slideshare.net/KarthikRamasamy3/linked-in-stream-processing-meetup-apache-pulsar?qid=f7fade7e-632c-47fe-aa68-aea84a622866&v=&b=&from_search=2> ---- 2018-05-10 19:59:33 UTC - Sanjeev Kulkarni: in the above slideshare shared by karthik, take a look at slides 11-14 ---- 2018-05-10 19:59:36 UTC - Ntale Lukama: @Karthik Ramasamy thanks a lot ---- 2018-05-10 19:59:49 UTC - Ntale Lukama: let me take a look at the slides ---- 2018-05-10 20:28:04 UTC - Sanjeev Kulkarni: @Daniel Ferreira Jorge for running functions, you will need to install the following packages. pip install pulsar-client protobuf futures grpcio grpcio-tools ---- 2018-05-10 20:44:13 UTC - Ntale Lukama: @Karthik Ramasamy what about failure scenarios affecting Disk I/O, authentication or Geo-replication, etc... ---- 2018-05-10 20:45:57 UTC - Ali Ahmed: @Ntale Lukama pulsar guarantees fsync before acknowledgement so you won’t lose data ---- 2018-05-10 20:54:57 UTC - Ntale Lukama: Fantastic! ---- 2018-05-10 20:55:05 UTC - Ntale Lukama: Thanks @Ali Ahmed ---- 2018-05-10 20:57:11 UTC - Ali Ahmed: just for added clarification in case there is confusion published benchmark and latency numbers are always with fsync, you cannot disable that in pulsar ---- 2018-05-10 23:43:49 UTC - Matteo Merli: <!here> @Josh West @Byron Since several people were asking to take a look at Go client API, I’ve created a PR with current work in progress. Any feedback from Go developers (or not) is welcome. <https://github.com/apache/incubator-pulsar/pull/1764> +1 : Byron, Nozomi Kurihara, Sijie Guo, jia zhai, Ali Ahmed, Jerry Peng ---- 2018-05-11 01:12:44 UTC - Josh West: nice @Matteo Merli thanks ---- 2018-05-11 01:26:40 UTC - Kesav Kolla: @Kesav Kolla has joined the channel ---- 2018-05-11 01:56:12 UTC - Senthilkumar Kalaiselvan: Sure, Thanks. I'll take a look. ----
