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

> 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 would like to learn what @Sanjeev Kulkarni >> and @Jerry Peng think about it. >> >> - Sijie >> >

Re: [DISCUSS] PIP-65: Adapting Pulsar IO Sources to support Batch Sources

g the > > > > discovered tasks. So the discovered tasks are published to its output > > > > topic. > > > > - BatchSource: can be implemented using a function that is receiving > > the > > > > batch source tasks and execute the source task. > > > >

Re: [DISCUSS] PIP-65: Adapting Pulsar IO Sources to support Batch Sources

topic. > > > - BatchSource: can be implemented using a function that is receiving > the > > > batch source tasks and execute the source task. > > > > > > So it seems that this can be achieved using the existing framework by > > > combining two funct

Re: [DISCUSS] PIP-65: Adapting Pulsar IO Sources to support Batch Sources

Pinging the community about this. Would love feedback on this. Thanks! On Wed, May 13, 2020 at 10:34 PM Sanjeev Kulkarni wrote: > Hi all, > > The current interfaces for sources in Pulsar IO are geared towards > streaming sources where data is available on a continuous basis. The

[DISCUSS] PIP-65: Adapting Pulsar IO Sources to support Batch Sources

Hi all, The current interfaces for sources in Pulsar IO are geared towards streaming sources where data is available on a continuous basis. There exist a whole bunch of data sources where data is not available on a continuous/streaming fashion, but rather arrives periodically/in spurts. These set

Re: [DISCUSS] PIP-62: Move connectors, adapters, and presto connector to separate repositories

s. In any case, we should have > > a ~daily build against the "latest" master in order to avoid > > regressions. > > > > > > -- > > Matteo Merli > > > > > > On Thu, Apr 9, 2020 at 1:11 PM Sanjeev Kulkarni > > wrote: > >

Re: [DISCUSS] PIP-62: Move connectors, adapters, and presto connector to separate repositories

Thanks Sijie for writing this proposal. I whole-heartedly agree with this proposal. Not only does it reduce Pulsar build time and make our lives as pulsar developers simple, it will also make connector/adaptor contributions less frictionless for contributors. No longer will developers need to know

Re: [DRAFT] Pulsar report 2019-03

Also 2.3.0 and not 2.2.0 On Wed, Mar 13, 2019 at 9:19 AM Ivan Kelly wrote: > typo when talking about PIPs. s/sever/several/ > > -Ivan > > On Wed, Mar 13, 2019 at 6:47 AM Matteo Merli wrote: > > > > ## Description: > > > > Pulsar is a highly scalable, low latency messaging platform running on >

Re: [discussion] break down the gaint integration test job into multiple integration jobs

+1 On Fri, Feb 8, 2019 at 8:52 PM Sijie Guo wrote: > `Hi all, > > Integration job has been a pain point for merging pull requests. The total > run time of the integration job typically is around an hour. If an > integration test is failing, retrigger the job requires another hour to > run. rerun

Re: Integration test fixes

Could you pl merge master in your branch and try again? Matteo fixed some bugs in integrated tests that might be affecting this On Wed, Jan 30, 2019 at 7:35 AM David Kjerrumgaard wrote: > I have merged PR-2865 with > master and am not getting the foll

Re: [DISCUSS] Skip tests for documentation related changes

If developers are in charge of checking the checkbox, it might lead to errors. Any way to make it automatic? Since docs are restricted to certain areas of repo, maybe we can have some rules around that? On Mon, Jan 28, 2019 at 12:12 PM Sijie Guo wrote: > Hi all, > > Currently for every documenta

Re: Planning to kickoff 2.2.1 release

+1 On Wed, Dec 12, 2018 at 4:02 PM Matteo Merli wrote: > We have accumulated a fair amount of fixes after 2.2.0 release. > > https://github.com/apache/pulsar/milestone/19?closed=1 > > One of the requirements was to have BookKeeper 4.7.3 which is now available > so I would recommend that we proce

Re: [DRAFT] November report

Looks good! On Wed, Nov 14, 2018 at 2:27 PM Jia Zhai wrote: > +1. 👍 > > On Thu, Nov 15, 2018 at 3:36 AM Matteo Merli wrote: > > > Please take a look > > > > - > > > > ## Description: > > > > Pulsar is a highly scalable, low latency messaging platform running on > > commodity hardware. It pr

Re: integration tests

+1 on making it mandatory. On Tue, Oct 9, 2018 at 9:36 PM Matteo Merli wrote: > Should we ask infra to make the integration tests check to be mandatory? > > On Tue, Oct 9, 2018 at 9:26 PM Sijie Guo wrote: > > > Hi all, > > > > Currently Apache Jenkins has been back to normal for a few days and

Re: Pulsar release 2.2

; > protobuf.util.JsonFormat$ParserImpl.merge(JsonFormat.java:1273) > > at > > org.apache.pulsar.functions.runtime.shaded.com.google. > > protobuf.util.JsonFormat$ParserImpl.merge(JsonFormat.java:1155) > > at > > org.apache.pulsar.functions.runtime.shad

Re: Pulsar release 2.2

Hi Joe, Have we started the 2.2 release process yet? Thanks! On Thu, Sep 27, 2018 at 9:18 PM Dave Fisher wrote: > Hurray for rolling the first TLP release! > > Regards, > Dave > > Sent from my iPhone > > > On Sep 27, 2018, at 11:43 PM, Joe Francis wrote: > > > > Good. I will get this going. > >