Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

Dave. > > I also think it is a misuse of the developer list to specifically announce > new community members that just so happen to be recent SN hires. > > On Dec 9, 2021 at 3:24:29 PM, Sijie Guo wrote: > > > Dave - I don't think SN presents the community. We just shared o

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

Dec 10, 2021, at 11:10 AM, Sijie Guo wrote: > > > >> I also think it is a misuse of the developer list to specifically > announce > > new community members that just so happen to be recent SN hires. > > > > What do you mean by "announce new community mem

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

ls the > roadmap and that the way to get involved and help shape the technology is > by engaging with SN via their Ambassador program. > > On Fri, Dec 10, 2021 at 1:47 PM Dave Fisher wrote: > > > > > > On Dec 9, 2021, at 3:24 PM, Sijie Guo wrote: > > > > &g

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

; > If you want Ford Motor Company as a customer, you should join my Ford > > Ambassador Program. Ford would have a problem with that, and so should > the > > PMC of Apache Pulsar. > > > > This is exactly what Confluent started doing with the Kafka community. > They >

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

hing they could to make Confluent == Kafka. Great for Confluent, > terrible for the community. > > SN != Pulsar > > On Dec 10, 2021 at 7:25:29 PM, Sijie Guo wrote: > > > Chris and Dave, > > > > Thank you for bringing the concern up. However, I don’t think the con

Re: Status of Pulsar 2.9.0 and starting 2.9.1

My take is - if we haven't announced 2.9, I would suggest just redoing the 2.9.0 release. - Sijie On Sun, Dec 12, 2021 at 6:35 PM Hang Chen wrote: > I am a little confused about why we should skip 2.9.0 and not continue > to release 2.9.0 by including the critical bug fixes. In fact, the > Puls

Re: Status of Pulsar 2.9.0 and starting 2.9.1

h maven central. They don’t > > let anyone republish versions. > > > > There are no do overs on versions. We simply cannot redo 2.9.0 at this > > moment. > > > > All the best, > > Dave > > > > Sent from my iPhone > > > > > On

Re: Status of Pulsar 2.9.0 and starting 2.9.1

gt; > https://downloads.apache.org/pulsar/pulsar-2.9.0/ > > > > (2) we have published 2.9.0 artifacts through maven central. They don’t > > let anyone republish versions. > > > > There are no do overs on versions. We simply cannot redo 2.9.0 at this > > moment. &

Re: Status of Pulsar 2.9.0 and starting 2.9.1

ocess. - Sijie On Mon, Dec 13, 2021 at 10:04 AM Dave Fisher wrote: > > > > On Dec 13, 2021, at 9:57 AM, Sijie Guo wrote: > > > > I am fine with doing 2.9.1. > > > > I am trying to understand what happened between released 2.9.0 and > > announcing it.

Re: Log4j2 Zero Day vulnerability (CVE-2021-44228)

I have updated the blog post in https://github.com/apache/pulsar/pull/13274/files *If upgrading is not an option, you may also mitigate by adding `-Dlog4j2.formatMsgNoLookups=true` to the `PUSLAR_EXTRA_OPTS` in the `configData` section for proxy, broker, bookkeeper, zookeeper, auto-recovery, and r

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

12:44 PM Joshua Eric wrote: > > > That is an additional problem, that a PMC member doesn’t see an issue > with > > an SN employee promoting a new SN hire. > > > > At least half a dozen people join the community daily. Why aren’t we > > celebrating all of them? No of

Re: [DISCUSSION] PIP-117: Change Pulsar standalone defaults

+1 On Tue, Dec 14, 2021 at 9:18 AM Matteo Merli wrote: > https://github.com/apache/pulsar/issues/13302 > > Copying here for quoting convenience > > > > > > ## Motivation > > Pulsar standalone is the "Pulsar in a box" version of a Pulsar cluster, > where > all the components are started with

Re: [DISCUSSION] PIP-118: Do not restart brokers when ZooKeeper session expires

+1 On Tue, Dec 14, 2021 at 10:03 AM Matteo Merli wrote: > https://github.com/apache/pulsar/issues/13304 > > > Pasted below for quoting convenience. > > --- > > > ## Motivation > > After all the work done for PIP-45 that was already included in 2.8 and 2.9 > releases, it enabled the concept o

Re: [DISCUSSION] PIP-119: Enable consistent hashing by default on KeyShared dispatcher

+1 On Tue, Dec 14, 2021 at 10:15 AM Matteo Merli wrote: > Pasted below for quoting convenience. > > > > > ## Motivation > > The consistent hashing implementation to uniformly assign keys to consumers > in the context of a KeyShared subscription, was introduced in > https://github.com/ap

Re: [DISCUSSION] PIP-120: Enable client memory limit by default

+1 On Tue, Dec 14, 2021 at 11:20 AM Matteo Merli wrote: > https://github.com/apache/pulsar/issues/13306 > > > Pasted below for quoting convenience. > > > > > ## Motivation > > In Pulsar 2.8, we have introduced a setting to control the amount of memory > used by a client instance. > > ``

Re: [VOTE] PIP-120: Enable client memory limit by default

+1 On Wed, Dec 22, 2021 at 2:08 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il Mer 22 Dic 2021, 16:58 Michael Marshall ha > scritto: > > > +1 > > > > - Michael > > > > On Wed, Dec 22, 2021 at 6:10 AM Hang Chen wrote: > > > > > > +1 > > > > > > Thanks, > > > Hang > > > > > > PengHui

Re: [VOTE] PIP-119: Enable consistent hashing by default on KeyShared dispatcher

+1 On Tue, Dec 21, 2021 at 3:23 PM Matteo Merli wrote: > This is the voting thread for PIP-119. It will stay open for at least 48h. > > https://github.com/apache/pulsar/issues/13305 > > --- > > ## Motivation > > The consistent hashing implementation to uniformly assign keys to consumers

Re: [VOTE] PIP-118: Do not restart brokers when ZooKeeper session expires

+1 On Tue, Dec 21, 2021 at 3:22 PM Matteo Merli wrote: > https://github.com/apache/pulsar/issues/13304 > > Following the discussion, I have updated the proposal to also include > the deprecation and renaming of the config setting name to > `metadataSessionExpiredPolicy`. > > > > --- > ## Mot

Re: [VOTE] PIP-123: Introduce Pulsar metadata CLI tool

+1 On Tue, Dec 21, 2021 at 3:59 PM Matteo Merli wrote: > This is the voting thread for PIP-123. It will stay open for at least 48h. > > https://github.com/apache/pulsar/issues/13346 > > > - > ## Motivation > > For a very long time, we have included a CLI command to start the ZooKeeper >

Re: [VOTE] PIP-117: Change Pulsar standalone defaults

+1 On Tue, Dec 21, 2021 at 3:49 PM Matteo Merli wrote: > This is the voting thread for PIP-117. It will stay open for at least 48h. > > https://github.com/apache/pulsar/issues/13302 > > > > ## Motivation > > Pulsar standalone is the "Pulsar in a box" version of a Pulsar cluster, > where > a

Re: [DISCUSS] Proceeding with PIP-62 plan, before Apache Pulsar 2.10.0 is released

Sorry. When you say "we discussed", who are "we"? Is it DataStax? I believe we want to keep SQL until the code change lands in Trino. Because there are still users using this component. - Sijie On Tue, Dec 21, 2021 at 11:34 PM Enrico Olivelli wrote: > Lari, > > Il giorno mer 22 dic 2021 alle o

Re: Warm Geetings on New Year 2022

Thanks Yu and many contributors for the hard work on documentation! Happy New Year! - Sijie On Fri, Dec 31, 2021 at 3:07 AM Yu wrote: > Hi Pulsar enthusiasts, > > > With 2022 knocking on our doors, I would like to take this opportunity to > express sincere gratitude to you for making what Puls

Re: Sending 2.6 release line to EOF

Agree to have a vote to keep a record. - Sijie On Mon, Jan 3, 2022 at 3:40 PM 陳智弘 wrote: > I think having a vote and quickly announce the EOF of 2.6.x will be better > to the community. > > > Dave Fisher 於 2022年1月4日 週二 06:06 寫道： > > > I don’t think we need a VOTE. Let’s do this by LAZY CONSENS

Re: Docker image docker pull apachepulsar/pulsar:2.8.2 missing from dockerhub

Hi Francisc, The 2.8.2 image is there: https://hub.docker.com/layers/apachepulsar/pulsar/2.8.2/images/sha256-d538416d5afe03360e10d5beb44bdad33d7303d137fc66c264108426875f61c6?context=explore - Sijie On Thu, Dec 30, 2021 at 8:15 AM Francisc Florian Munteanu < francisc.florian.munte...@infovista.co

Re: [DISCUSS] Apache Pulsar 2.10.0 release

+1. All make sense to me! We probably need to move to the feature frozen stage in order to cut a release at the end of January. - Sijie On Sun, Dec 26, 2021 at 8:46 PM PengHui Li wrote: > Hi, everyone > > I hope you’ve all been doing well. I would like to start an email thread to > discuss fe

Re: Lifting Kubernetes minimum version requirement for Apache Pulsar Helm Charts from k8s 1.14 to 1.18

Can you clarify what is the main change? I see most of the changes are done in the CI part. - Sijie On Tue, Jan 4, 2022 at 1:41 AM Lari Hotari wrote: > Hi all, > > Currently k8s 1.14 version is used in CI to verify the Helm chart changes. > > k8s 1.14 became end-of-life 2019-12-11 , over 2 year

Re: [VOTE] PIP-130: Apply redelivery backoff policy for ack timeout

+1 On Wed, Jan 5, 2022 at 12:12 AM Ran Gao wrote: > +1 > > Best, > Ran Gao > > On 2022/01/04 03:34:33 PengHui Li wrote: > > This is the voting thread for PIP-130. It will stay open for at least 48 > > hours. > > > > https://github.com/apache/pulsar/issues/13528 > > > > Pasted below for quoting c

Re: [DISCUSSION] PIP-122: Change loadBalancer default loadSheddingStrategy to ThresholdShedder

+1 ThresholdShedder is a much better policy On Tue, Jan 4, 2022 at 6:24 AM Hang Chen wrote: > https://github.com/apache/pulsar/issues/13340 > > Pasted below for quoting convenience. > > > ### Motivation > The ThresholdShedder load balance policy since Pulsar 2.6.0 by > https://github.com/ap

Re: Voting time period minimum

I believe 48 hours vote is only for PIP, which was agreed in the dev@. For other activities, this project follows the ASF 72 hours rule. - Sijie On Mon, Jan 3, 2022 at 8:17 PM Dave Fisher wrote: > Yes please! I did not notice that. > > Personally I would be ok with 72 hours lazy consensus, but

Re: upcoming change: Apache Pulsar Helm Chart switching from Pulsar 2.7.4 version to 2.8.2; known issue with ZK when TLS is enabled

The fundamental problem I see is that we don't have a proper helm chart release and we don't have good versioning guidance. Chart should have its own version, which is independent of the Pulsar version. Also, we need to provide a guide to the community - most of the time, you don't need to upgrad

Re: [PR] Pulsar non root docker image

Is Functions being verified? - Sijie On Wed, Jan 5, 2022 at 11:26 AM Michael Marshall wrote: > PR 13376 is ready for review, PTAL. > > What approach should we take regarding docker image size? > I propose providing a minimal image along with documentation > on how to add your own debugging tool

Re: [PR] Pulsar non root docker image

5da0f95794259694cc781e8960b7e52fac06b > > On Thu, Jan 6, 2022 at 7:00 PM Sijie Guo wrote: > > > > Is Functions being verified? > > > > - Sijie > > > > On Wed, Jan 5, 2022 at 11:26 AM Michael Marshall > > wrote: > > > > > PR 13376 is

Re: New Feature Proposal: flag to require a non-partitioned topic on Producer/Consumer Builder

I don't think we should expose this feature flag on the client-side. Ideally, people shouldn't be aware of partitioned vs non-partitioned. - Sijie On Wed, Feb 16, 2022 at 1:37 AM Enrico Olivelli wrote: > Ping > > Il Dom 13 Feb 2022, 11:49 Enrico Olivelli ha > scritto: > > > Hello, > > I have a

Re: New Pulsar website goes live!

Hi Yu, Thank you and all the other contributors for all the great work! Well done. - Sijie On Wed, Feb 16, 2022 at 8:04 PM Yu wrote: > Thanks for your quick feedback, Penghui and Dianjin. > > As mentioned in the last email, "*...**there are some known issues (eg. > localized pages and some CLI

Pulsar Helm Chart Repo is broken

Hi all, I think the new website push has broken the Pulsar Helm Chart repo. We might need to take a look at how to fix it. - Sijie

Re: Pulsar Helm Chart Repo is broken

I send a notice to users@ mailing list and #general channel about the situation. - Sijie On Wed, Feb 16, 2022 at 8:46 PM Sijie Guo wrote: > Hi all, > > I think the new website push has broken the Pulsar Helm Chart repo. > > We might need to take a look at how to fix it. > > - Sijie >

[NOTICE] Pulsar Helm Charts Repo is temporarily down

Hi everyone, Just want to let everyone know that the Pulsar Helm Charts repo is temporarily down due to the new Pulsar website push. The `charts/index.yaml` was not added to the new Pulsar site. So if you are using the helm command to pull the charts, it will fail. A bunch of the committers is loo

Re: Pulsar Helm Chart Repo is broken

tch today is causing this > exception, we should update the helm chart ci to fix this issue, will take > a look at it later > > Thanks, > Guangning > > Sijie Guo 于2022年2月17日周四 12:52写道： > > > I send a notice to users@ mailing list and #general channel about the > >

Re: New Pulsar website goes live!

sar website, do not hesitate to > add it here [2], thanks. > > [1] https://github.com/apache/pulsar/pull/14344 > [2] > > https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#bookmark=id.86uprmy9cv2w > > > On Thu, Feb 17, 2022 at 12:42 PM

Re: New Pulsar website goes live!

Maybe we should roll back to the old website first. - Sijie On Thu, Feb 17, 2022 at 8:33 AM Sijie Guo wrote: > Remove users@ > > Yu - I have received quite a few questions about broken links. > > https://pulsar.apache.org/docs/en/security-jwt/ <- This is broken. > > I

Re: [Discuss] Apache pulsar node client 1.6.0 release

+1 On Thu, Feb 17, 2022 at 3:49 AM Guangning E wrote: > Recently many users want to use the oauth2 feature based on the node js > client. I've added this feature, so I'd like to start a release for the > pulsar node js 1.6.0 client. > > > > > Thanks, > Guangning >

Rollback Pulsar Website Change

Hi all, All the Pulsar links out there (Google, Stackoverflow, etc) are broken. I am sending PRs to rollback the website push. - Sijie

Re: Rollback Pulsar Website Change

https://github.com/apache/pulsar-site/pull/3 https://github.com/apache/pulsar/pull/14356 Changes to roll back the website. - Sijie On Thu, Feb 17, 2022 at 11:30 AM Sijie Guo wrote: > Hi all, > > All the Pulsar links out there (Google, Stackoverflow, etc) are broken. I > am se

Re: Rollback Pulsar Website Change

The website has been rolled back to the old one. - Sijie On Thu, Feb 17, 2022 at 12:37 PM Lari Hotari wrote: > Change to roll back Apache Pulsar Helm chart publishing to new site: > https://github.com/apache/pulsar-helm-chart/pull/234 > > -Lari > > On 2022/02/17 19:44:

Re: New Pulsar website goes live!

i, Feb 18, 2022 at 1:07 AM Sijie Guo wrote: > > > Maybe we should roll back to the old website first. > > > > - Sijie > > > > On Thu, Feb 17, 2022 at 8:33 AM Sijie Guo wrote: > > > > > Remove users@ > > > > > > Yu - I have rece

Re: [DISCUSS] Releasing pulsar-client-go 0.8.1

+1 On Sun, Mar 6, 2022 at 6:46 PM r...@apache.org wrote: > +1 > > -- > Thanks > Xiaolong Ran > > PengHui Li 于2022年3月5日周六 18:10写道： > > > +1 > > > > Penghui > > > > On Sat, Mar 5, 2022 at 4:58 AM Matteo Merli > > wrote: > > > > > +1 Thanks Rui, we should eliminate the GPL dependency ASAP. > > >

Re: [Discuss] Create Pulsar client release notes

Yu, thank you for driving this effort! Great to see a proposal focusing on this! +1 On Fri, Mar 4, 2022 at 2:59 AM Yu wrote: > Hi Pulsarers, > > For Pulsar release notes [1], we had issues below for a long time. > > - All contents are on a single Pulsar release note page. No navigations. > It's

Re: Happy International Women’s Day!

Best wishes to all the female contributors! - Sijie On Tue, Mar 8, 2022 at 9:00 AM Yu wrote: > Dear Pulsar female contributors, > > Success doesn’t come easy and women never give up. Thanks for bringing so > much love and support to the Pulsar community. And every man needs a > woman when his l

Re: [ANNOUNCE] Apache Pulsar Go Client 0.8.1 released

Congrats! Rui - Thank you for driving this important fix for the license issue! - Sijie On Tue, Mar 15, 2022 at 2:10 AM Rui Fu wrote: > The Apache Pulsar team is proud to announce Apache Pulsar Go Client > version 0.8.1. > > Pulsar is a highly scalable, low latency messaging platform running o

Re: Performance Engineering Track at ApacheCon NA?

Sharan, I think it is a very great idea to have a performance engineering track. Some committers and I are definitely interested in contributing talks to this track. - Sijie On Fri, Mar 11, 2022 at 4:44 AM sharanf wrote: > Hi All > > The call for tracks for ApacheCon NA is open. There is a sug

Re: Performance Engineering Track at ApacheCon NA?

very much for the response and interest! I will post an update > about the track as soon as I have one. > > > > Thanks > > Sharan > > > > On 2022/03/15 23:59:46 Sijie Guo wrote: > > > Sharan, > > > > > > I think it is a very gr

Pulsar Summit San Francisco 2022 CFP is open!

Hi, all the Pulsar community members, Pulsar Summit San Francisco 2022 CFP is open now! It will be our *first-ever in-person Pulsar Summit *in San Francisco! We're glad to invite you to share your experience and add up to the wonderfulness. As a speaker, you will receive the chance to demonstrate

Re: NSQ Protocol Support

We introduced the protocol handler framework in 2.5.0. This framework allows people implementing its own protocol by leveraging Pulsar’s current event stream storage and many other enterprise features. Kafka-on-Pulsar (KoP) is one of the examples implemented using this framework. A team of enginee

Re: Python 27 End of life

Please create a PIP for that. This requires a discussion and vote. - Sijie On Sat, Jan 4, 2020 at 5:04 PM Ali Ahmed wrote: > Python 2.7 is officially EOL. We should remove associated build artifacts > and update base docker build and distribution images to jdk11 and python3. > Ideally before th

Re: Python 27 End of life

out what is the real proposal here. Thanks, Sijie On Mon, Jan 6, 2020 at 11:47 AM Ali Ahmed wrote: > Here is proposal for it, please add comments. > > > https://docs.google.com/document/d/1kcRIvJVd8pfKxX3lgCRT1XWUAvh5HyHh9XCGIYZ5Flk/edit?usp=sharing > > > > On Sun, Jan

[VOTE] Pulsar Release 2.5.0 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.5.0. It fixes the following issues: https://github.com/apache/pulsar/milestone/22?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the sou

Current master is broken

Hi all, The current master was broken due to conflicts from two unrelated merges. Penghui sent a pull request to fix the broken master: https://github.com/apache/pulsar/pull/6006 Until the pull request is merged, please not trigger any Jenkins CI since they will not pass anyway. Thanks, Sijie

Re: Flaky tests [VOTE] Pulsar Release 2.5.0 Candidate 2

gt; - validate connectors > > > > Regards, > > Yong > > > > On Mon, 6 Jan 2020 at 20:02, Sijie Guo wrote: > > > > > This is the second release candidate for Apache Pulsar, version 2.5.0. > > > > > > It fixes the following issue

Re: Pulsar Release 2.4.3 Discussion

Guangning, Thank you for bringing this up to the community and thanks for volunteering the release. However, I think there is one problem needs to be addressed for release 2.4.3 - how to label the fixes for 2.4.3? I am assuming those tasks that need to be cherry-picked to 2.4.3 are already inclu

Re: [DISCUSS] Contribute DotPulsar to Apache Pulsar

It seems that there is no objections to accepting this repo. I will start an official vote in a separate email thread. On Tue, Dec 24, 2019 at 1:09 PM xiaolong ran wrote: > Daniel: > > Thank you for everything you’ve done. very nice work. > > The change LGTM +1 > > -- > Thanks > Xiaolong Ran > >

[VOTE] Accept DotPulsar as part of Apache Pulsar project

Hi all, I'd like to start a vote thread for accepting DotPulsar [1] as part of Apache Pulsar project. DotPulsar is a pulsar client library for .NET which was originally developed by Danske Commodities A/S Please vote with your opin

Re: Github action migration Discussion

+1 Github has more resources to run CI jobs as the contributions keep growing. On Tue, Jan 14, 2020 at 11:06 AM Guangning E wrote: > After a period of testing, Github's action is much more stable than > Jenkins. Jenkins now has a large number of tasks in the queue and > insufficient resources. T

Re: [Discuss] Create alpha tag in pulsar-client-go

If the tag is used for developing the Go Functions for 2.6.0, that should be fine. +1 from me On Tue, Jan 14, 2020 at 11:00 PM xiaolong ran wrote: > Hello all committers: > > Currently, the Go Functions depends on the cgo client, users need to > build pulse-client-cpp before using. This is a bad

Re: [VOTE]Github action migration

+1 On Wed, Jan 15, 2020 at 10:16 AM Guangning E wrote: > The discussion is here > > https://lists.apache.org/thread.html/rff18ec60c9838cd69adee2840ead9cf8ee7cb6331c61845ad93e776e%40%3Cdev.pulsar.apache.org%3E > > Guangning E 于2020年1月15日周三 上午10:10写道： > > > Now pulsar's pull request is blocked on

Re: [VOTE] Pulsar Release 2.5.0 Candidate 2

China > > Mobile: +86 15810491983 > > > > > On Mon, Jan 13, 2020 at 5:39 PM Yong Zhang > wrote: > > > +1 (non-binding) > > > > - validate the checksum of the src, bin and connectors packages > > - compile the source code successfully > > - validat

[RESULTS] [VOTE] Pulsar Release 2.5.0 Candidate 2

Hi all, The vote is now closed with 6 +1, 0 +0, and 0 -1. In the 6 +1 votes: 3 binding votes: - Jia Zhai - Penghui Li - Sijie Guo 3 non-binding votes: - Guangning E - Xiaolong Ran - Yong Zhang Thanks, Sijie On Mon, Jan 6, 2020 at 8:02 PM Sijie Guo wrote: > This is the second rele

Re: Pulsar Release 2.4.3 Discussion

I will start a separate thread for discussing the release tag. On Mon, Jan 13, 2020 at 7:46 PM Sijie Guo wrote: > Guangning, > > Thank you for bringing this up to the community and thanks for > volunteering the release. > > However, I think there is one problem needs to be add

[DISCUSS] Introduce release labels for minor releases

Hi all, As we are discussing cutting a release for 2.4.3 in another thread, we should discuss how to label the changes (pull requests) for minor releases. Currently, we used milestones for both major releases (e.g. 2.5.0) and minor releases (e.g. 2.4.3). A change will be first merged to master an

Re: [DISCUSS] Introduce release labels for minor releases

:24，Chris Bartholomew > 写道： > > > > +1 > > Makes a lot of sense to me. Thanks, Sijie. > > > > Cheers, > > Chris > > > > On Fri, 17 Jan 2020 at 07:41, Sijie Guo wrote: > > > >> Hi all, > >> > >> As we are discussing cutting a

[VOTE] Adopt using release labels for minor releases

Hi all, This is the official vote thread for adopting using release labels for minor release as proposed in https://lists.apache.org/thread.html/ra057f9bb3385f62a9216a202260805074c3f1af77c144907fa1b50cd%40%3Cdev.pulsar.apache.org%3E Please vote with your opinions. The vote will be open for at lea

[ANNOUNCE] Apache Pulsar 2.5.0 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.5.0. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subsc

[DISCUSS] Homebrew libpulsar

Hi all, It is my first time to realize that there is a libpulsar entry in homebrew. (https://github.com/apache/pulsar/issues/6091). Are Pulsar committers responsible for updating this? Or homebrew team is updating that entry? If the committers are responsible for updating it, it should have been

Re: [DISCUSS] Homebrew libpulsar

ff8a33e9627c7a46d5f8d2546f > Author: FX Coudert > Date: Mon Apr 15 17:40:36 2019 +0200 > > libpulsar 2.3.1 > > Closes #38947. > > Signed-off-by: FX Coudert > > commit 3c0b62cc0288f6d5dfb0ed9f682d6e245d1e3cfe > Author: Steven Peters > Date: Mon Mar 4 12:41:16 2019 -0

Re: [DISCUSS] Homebrew libpulsar

is already released. > We could certainly include it as a post-step in our release process, > to do after the official release announcement is done. > > > > -- > Matteo Merli > > > On Tue, Jan 21, 2020 at 11:08 AM Sijie Guo wrote: > > > > Thanks Dave

[RESULT] [VOTE] Accept DotPulsar as part of Apache Pulsar project

72 hours have passed. I am happy to announce that Pulsar PMC accepts DotPulsar as a sub-project. The vote has received 7 +1 votes, 0 +0 votes, 0 -1 votes. The 7 +1 votes include 4 bindings votes, 3 non-binding votes. Binding votes are: - Jia Zhai - Joe F - Penghui Li - Sijie Guo Non-binding

[RESULT] [VOTE] Adopt using release labels for minor releases

> > > > -- > > > Thanks > > > Xiaolong Ran > > > > > > > > > > 在 2020年1月19日，上午11:03，Guangning E 写道： > > > > > > > > +1(non-binding) LGTM > > > > > > > > Thanks, > > > > Guangning > > &

Re: [RESULT] [VOTE] Adopt using release labels for minor releases

I will change the current minor release milestones (2.4.3 and 2.5.1) to use release labels and remove them. - Sijie On Wed, Jan 22, 2020 at 12:35 AM Sijie Guo wrote: > 72 hours have passed. I am happy to announce that we are adopting using > release labels for minor releases. > >

Re: [RESULT] [VOTE] Adopt using release labels for minor releases

FYI. I have created a "Committer Guide" ( https://github.com/apache/pulsar/wiki/Committer-Guide). Added the notes on how to add labels and milestones when merging pull requests. Thanks, Sijie On Wed, Jan 22, 2020 at 12:37 AM Sijie Guo wrote: > I will change the current minor relea

Re: [RESULT] [VOTE] Adopt using release labels for minor releases

: https://github.com/apache/pulsar/milestone/27 Minor release (2.4.3): https://github.com/apache/pulsar/labels/release%2F2.4.3 Minor release (2.5.1): https://github.com/apache/pulsar/labels/release%2F2.5.1 - Sijie On Wed, Jan 22, 2020 at 12:52 AM Sijie Guo wrote: > FYI. I have created a &quo

Re: [VOTE]Github action migration

, Jan 21, 2020 at 4:27 AM Guangning E wrote: > Vote result: > Sijie Guo +1(binding) > xiaolong ran +1(binding) > Enrico Olivelli +1(non-binding) > Yuva raj +1(non-binding) > lan.liang +1(non-binding) > PengHui Li +1(binding) > Jia Zhai +1(binding) > Now we can start th

[ANNOUNCE] Pulsar Summit San Francisco 2020 Call for Presentation extended!

You can find more detailed track descriptions and the form to submit a proposal on the Pulsar Summit website at --> https://pulsar-summit.org/call-for-presentations/ --> https://sessionize.com/pulsar-summit-san-francisco-2020/ As usual, accepted speakers get a free conference pass. Best reg

[DISCUSS] A new repo for github actions

Hi all, We are customizing some Github Actions for running Pulsar CI. 1) we have a customized GitHub action for setting up maven. But this action currently is hosted on a personal project (see https://github.com/apache/pulsar/issues/6012). 2) I am introducing another action in https://github.com

Formalize PIP workflow

Hi all, We are using PIP for adopting major changes to Pulsar. It was done in a lazy-consensus way. It was very efficient for growing the community and driving innovations in the Pulsar community. However, we don't have a clear workflow for PIP. It is actually causing some confusion and inconsiste

Re: [DISCUSS] A new repo for github actions

gt; PengHui Li 于2020年2月1日 周六上午10:02写道： > > > LGTM +1 > > > > Guangning E 于2020年2月1日周六 上午9:36写道： > > > > > That's great > > > > > > Thanks, > > > Guangning > > > > > > Sijie Guo 于2020年2月1日周六 上午5:55写道： > >

pulsarbot

Hi all, After we moved CI from Jenkins to Github Actions, only committers have the ability to trigger re-running the failed checks. It is inconvenient for contributors. As you might already notice, I introduced a pulsarbot action in pulsar-test-infra ( https://github.com/apache/pulsar-test-infra/

Re: pulsarbot

/pulsarbot/README.md Thanks, Sijie On Tue, Feb 4, 2020 at 11:53 PM Sijie Guo wrote: > Hi all, > > After we moved CI from Jenkins to Github Actions, only committers have the > ability to trigger re-running the failed checks. It is inconvenient for > contributors. > > As you mi

Re: [DISCUESS] PIP 57: Improve Broker's Zookeeper Session Timeout Handling

Sorry for the late reply. Joe - There are two things I would like to clarify first. 1) I think you have a misunderstanding about the zookeeper lock "ephemeral znode" and bookkeeper/ML fencing. Let's step back to understand the current Pulsar's behavior first. - A zookeeper lock doesn't prevent a

Re: [DISCUESS] PIP 57: Improve Broker's Zookeeper Session Timeout Handling

Since we used to compare bookkeeper/distributedlog and raft, I think bookkeeper/ML is pretty close to RAFT. If there is a TLA for RAFT, it should be a good starting point to follow. If you are planning to start the work, happy to join the force. - Sijie > > Joe > > On Sun, Feb 23, 2020 at 1

Re: Pulsar Release 2.5.1 Discussion

@Guangning E LGTM +1 Thank you for driving the release! - Sijie On Sat, Feb 22, 2020 at 1:54 AM xiaolong ran wrote: > Thanks Guangning E work for this. > > LGTM +1 > > -- > Thanks > Xiaolong Ran > > > 在 2020年2月22日，下午4:52，Guangning E 写道： > > > > Hi everyone, > > > > There are a few bug fixes

Re: Performance and production readiness of Pulsar Standalone

On Fri, Feb 28, 2020 at 6:49 AM Kramer, Andre wrote: > Hello, > > We have found that Pulsar standalone (which has zookeeper and bookie in > same Java process as the broker) on a simple throughput test showed over 3 > times the message throughput rate as did 3 separate processes (Zookeeper, 1 > Br

Re: Support Consumers Set Custom Retry Delay

Dezhi, Thank you for sharing this proposal. I have added this proposal to PIP-58 ( https://github.com/apache/pulsar/wiki/PIP-58-:-Support-Consumers--Set-Custom-Retry-Delay ). +1 for this proposal since it is extending the capability of dead letter policy. Thanks, Sijie On Wed, Feb 26, 2020 at 7

Re: Performance and production readiness of Pulsar Standalone

t with standalone than running separately (in > Kubernetes pods). > > Andre > > -----Original Message- > From: Sijie Guo > Sent: 28 February 2020 16:38 > To: Dev > Subject: Re: Performance and production readiness of Pulsar Standalone > > On Fri, Feb 28

Re: [RESULT] [VOTE] Accept DotPulsar as part of Apache Pulsar project

FYI. IP clearance is done in gene...@incubator.apache.org. I am moving forward with transferring the dotpulsar repo. INFRA Jira is created: https://issues.apache.org/jira/browse/INFRA-19920 - Sijie On Wed, Jan 22, 2020 at 12:26 AM Sijie Guo wrote: > 72 hours have passed. I am happy

Re: PIP for gRPC protocol handler

Christophe, Thank you for putting this up. I have moved your proposal to pulsar wiki and assign the proposal with PIP-59. https://github.com/apache/pulsar/wiki/PIP-59%3A-gPRC-Protocol-Handler - Sijie On Thu, Mar 5, 2020 at 7:27 AM Christophe Bornet wrote: > Dear Pulsar team, > > I'd like to p

Reschedule Pulsar Summit SF to August/September

Dear all, In light of growing concern and the further spread of the COVID-19 (Corona) virus and after close consultation with event stakeholders and the organizing parties, we have decided to reschedule the Pulsar Summit San Francisco *from April to August/September*. It was decided that with due

TGI Pulsar - weekly live stream about Pulsar and its ecosystem

Hi all, We are starting a weekly live stream - "TGI Pulsar" on Youtube this week. https://www.youtube.com/channel/UCywxUI5HlIyc0VEKYR4X9Pg/live It will happen every Friday at 1 pm PST. Each week we will invite one Pulsar committer or end-user to the live stream to chat about a topic of Apache Pul

Re: TGI Pulsar - weekly live stream about Pulsar and its ecosystem

Yes. Those live streams will be recorded and published on Youtube. - Sijie On Tue, Mar 10, 2020 at 2:44 PM Eugen Dueck wrote: > Hi Sijie > > Will the live streams be recorded for those you cannot watch them live? > > Eugen > > ---------- > *差出人:* Sij

Re: [RESULT] [VOTE] Accept DotPulsar as part of Apache Pulsar project

FYI. The DotPulsar repo is transferred to under apache now. https://github.com/apache/pulsar-dotpulsar - Sijie On Tue, Mar 3, 2020 at 12:54 AM Sijie Guo wrote: > FYI. IP clearance is done in gene...@incubator.apache.org. I am moving > forward with transferring the dotpulsar repo. >

Re: deadletter policy related

Hi Arun, Currently, the dead letter policy only worked for a shared subscription. It doesn't work for the subscriptions that have ordering implications such as "failover", "key_shared", and "exclusive". To better understand your requirements, what are the actions when a key is moved to a dead let

Re: Consumer Side Not Getting All Message and Deduplication Porcess is Not Working

> 1. Unable to remove duplicate message in broker.below Is my Code and config File. How did you send the messages and how did you verify the messages are duplicated? Just FYI the duplication is identified by sequence id, not by content. Just want to make sure the verification method you used is c

  1   2   3   4   5   6   >