PIP 21: Pulsar Edge Component

Hi folks, This is a PIP to add a Pulsar Edge component to enable to deployment of Pulsar functions on resource-constrained environments, such as IoT gateways to allow the processing to occur closer to the event source.

Build failed in Jenkins: pulsar-master #689

See Changes: [github] [blog] Enable blog in website and add one for 2.1.0 release (#2308) -- [...truncated 1.03 MB...] [INFO] Pulsar SQL :: Parent

Re: Consult: PIP work progress

Zongyang, Thank you for reaching out to Pulsar community. In general, PIP is used for proposing new features, improvements and user impact changes. However I don't think Pulsar community has defined any strict rules for people submitting PIP. The general rule for PIP is for people in the

Re: [ANNOUNCE] Apache Pulsar 2.1.0-incubating released

w00t!! > On Aug 4, 2018, at 3:46 AM, Jia Zhai wrote: > > Con~. Thanks a lot for the great work. > > On Sat, Aug 4, 2018 at 2:14 AM, Sijie Guo wrote: > >> The Apache Pulsar team is proud to announce Apache Pulsar version >> 2.1.0-incubating. >> >> This is the seventh Pulsar release after

Build failed in Jenkins: pulsar-master #687

See Changes: [github] Avoid creating output topic on tenant namespace if output-topic not -- [...truncated 1.09 MB...] Compact still running

PIP 20: Mechanism to revoke TLS authentication

Hi folks, This is a PIP to add a mechanism to block TLS client certs from accessing Pulsar if they have been compromised. This is a relatively small change, but I thought it best to put it to the community before moving ahead with it, as people may have opinions on the approach. The PIP is

Consult: PIP work progress

Hi Pulsar Community! Zongyang, here! I'm now reading PIP(Pulsar Improvement Proposal) on github. And I am a little confused about how PIP works and what are the principles of PIP. Disscused in more details, the actual problems are: 1. Do we need a State of PIP named released, which means