Re: Re: Introducer Pulsar admin api to pulsar-client-go

Hi Eric, Thanks for sharing the updates! I discussed this project with Max previously. We would like to contribute docs for it, and I've already added "Go admin API (coming soon)" to the new Pulsar API docs already [1], which brings many benefits, such as: - Build excitement before launch. - Gen

Re: [Discussion] Add a new default method to to the ManagedLedgerInterceptor

+1, It's a bug fix and the impact of adding this method is minimal. Thanks, Haiting On Tue, Mar 14, 2023 at 7:14 PM Yunze Xu wrote: > > +1. I support cherry-picking it to release branches even if new > default methods are added. It won't affect any existing use because > the interface is customi

Re: [DISCUSS] new idea: reverse reading a topic

> Here, the goal is to read a topic from a known messageId to previous messages > until a constraint depending on read messages. I get your point, but can you give a more detailed use case? Thanks, Haiting On Tue, Mar 14, 2023 at 6:40 PM Alexandre DUVAL wrote: > > Hi, > > The way you suggest wo

Re: [VOTE] PIP-249: Pulsar website redesign

+1 binding Thanks, Haiting On Wed, Mar 15, 2023 at 10:37 AM tison wrote: > > +1 (non-binding) > > Best, > tison. > > > Yu 于2023年3月15日周三 09:41写道： > > > +1 > > Thanks, Asaf and Emidio! > > The new copywriting and visuals are fantastic! > > > > On Wed, Mar 15, 2023 at 4:56 AM Dave Fisher wrote: >

Re: Release 2.11.1

+1 Thanks, Haiting On Wed, Mar 15, 2023 at 11:46 AM Yubiao Feng wrote: > > +1 > > Thanks > Yubiao Feng > > On Wed, Mar 15, 2023 at 11:43 AM guo jiwei wrote: > > > Hello, Pulsar community: > > > > I'd like to propose releasing Apache Pulsar 2.11.1. It's been about > > two months since 2.11.0 was

RE: Re: Introducer Pulsar admin api to pulsar-client-go

Hi Zhangjian, We can share some progress on our side: we have completed: * Extracted the pulsar-admin-go library from the pulsarctl and moved it to a separate repo under StreamNative (now it is private) * Updated the project layout and rename some pkg names like the cli pkg what we wil

Re: Release 2.11.1

+1 Thanks Yubiao Feng On Wed, Mar 15, 2023 at 11:43 AM guo jiwei wrote: > Hello, Pulsar community: > > I'd like to propose releasing Apache Pulsar 2.11.1. It's been about > two months since 2.11.0 was released. > > There are about over 200 PRS [0] cherry-picked to branch-2.11 since > the last r

Release 2.11.1

Hello, Pulsar community: I'd like to propose releasing Apache Pulsar 2.11.1. It's been about two months since 2.11.0 was released. There are about over 200 PRS [0] cherry-picked to branch-2.11 since the last release. If you have any important fixes or any questions, please reply to this email an

Re: [Discuss] PIP-256: Building Great Developer Experience with API Content

Hi Yu, Thanks for starting this thread! Perhaps you can reorganize the content in PIP template form so that we known the background and what is proposed at first. I read the doc and the changes proposed are at the last six pages (Changing the Admin API docs information architecture). The previous

Re: [Discuss] PIP-256: Building Great Developer Experience with API Content

Hi Yu, Your first document is really website analytics which should be shared with the community which might have different conclusions. It would be helpful in understanding motivation. I feel it needs to be in an issue as markdown where it is easy to review. I’ll note that it is dated from Jul

Re: [VOTE] PIP-249: Pulsar website redesign

+1 (non-binding) Best, tison. Yu 于2023年3月15日周三 09:41写道： > +1 > Thanks, Asaf and Emidio! > The new copywriting and visuals are fantastic! > > On Wed, Mar 15, 2023 at 4:56 AM Dave Fisher wrote: > > > +1(binding) > > > > Please fix the following sentence: “ Pulsar, although released to Apache >

Re: [VOTE] PIP-249: Pulsar website redesign

+1 Thanks, Asaf and Emidio! The new copywriting and visuals are fantastic! On Wed, Mar 15, 2023 at 4:56 AM Dave Fisher wrote: > +1(binding) > > Please fix the following sentence: “ Pulsar, although released to Apache > in 2017 (and actually built in 2012), ” it is not correct. Pulsar code was >

Re: [Discuss] PIP-256: Building Great Developer Experience with API Content

Hi Asaf, thanks for your reminder! The corresponding issue was filed at https://github.com/apache/pulsar/issues/19755 previously. Since it's a large initiative containing many content and complex formats, I've made it in Google Docs first and will relocate them to the issue once it's accepted by

Re: [DISCUSS] PIP-253: Expose producer metrics for deadLetterProducer and retryLetterProducer

Thanks for the suggestion Asaf, unfortunately that hasn't resolved the issue with SpotBugs. You can see the commit here . When I try to compile, I receive the same error message. Best, Kai On Tue, Mar 14, 2023 at 2:

Re: [VOTE] PIP-249: Pulsar website redesign

+1(binding) Please fix the following sentence: “ Pulsar, although released to Apache in 2017 (and actually built in 2012), ” it is not correct. Pulsar code was donated to the Apache Software Foundation via a Software Grant in 2017 (and initially created in 2012) Best, Dave Sent from my iPhone

Re: Data quality problem

I appreciate your interest in this. > What would the ideal data developer > workflow look like? Here are the first things coming to my mind on what would be ideal features: Schema mapping code MUST be possible to auto-generate. - Maintaining the mapping between a data system (whether that's

Re: [Discuss] PIP-256: Building Great Developer Experience with API Content

Side note: PIP should be in markdown in a GitHub issue for prosperity. External links lose permissions over time, come and go. On Mon, Mar 13, 2023 at 6:00 PM Yu wrote: > Hi community, > > Based on the [2022 Report] Pulsar Website Content Analysis (GA) [1], the > Pulsar API doc is one of the t

Re: [Discuss] PIP-248: Add backlog eviction metric

> Need to replace (place link) with link. I replaced the `Motivation` with your advice. > We discussed adding the subscription name which triggered the time limit to > Topics.getStats(). > Why? Since we have `pulsar_storage_backlog_eviction_count`, I think we don't need to expose the subscriptio

Re: [VOTE] PIP-249: Pulsar website redesign

+1 (binding) On Tue, Mar 14, 2023 at 8:43 AM Matteo Merli wrote: > +1 (binding) > > > -- > Matteo Merli > > > > On Tue, Mar 14, 2023 at 8:29 AM Asaf Mesika wrote: > > > Hi, > > > > I would like to start the vote on PIP-249: Pulsar website redesign. > > > > PIP link: https://github.com/apache/p

Re: [VOTE] PIP-249: Pulsar website redesign

+1 (binding) -- Matteo Merli On Tue, Mar 14, 2023 at 8:29 AM Asaf Mesika wrote: > Hi, > > I would like to start the vote on PIP-249: Pulsar website redesign. > > PIP link: https://github.com/apache/pulsar/issues/19611 > > You can read the discussion thread here: > https://lists.apache.org/th

[VOTE] PIP-249: Pulsar website redesign

Hi, I would like to start the vote on PIP-249: Pulsar website redesign. PIP link: https://github.com/apache/pulsar/issues/19611 You can read the discussion thread here: https://lists.apache.org/thread/3of7dfhn4qk033hqlqpvbc8so6bcolz4 Thanks, Asaf

Re: [DISCUSS] PIP-249: Pulsar website redesign

With no other comments, I'm proceeding to open the vote. Thank you all for your feedback! On Tue, Mar 14, 2023 at 5:03 PM Asaf Mesika wrote: > > > On Mon, Mar 13, 2023 at 7:29 AM tison wrote: > >> Hi Asaf, >> >> SGTM. I don't have more comments on the proposal. I'll be glad to review >> the im

Re: [DISCUSS] PIP-249: Pulsar website redesign

On Mon, Mar 13, 2023 at 7:29 AM tison wrote: > Hi Asaf, > > SGTM. I don't have more comments on the proposal. I'll be glad to review > the implementation later :) > > BTW, Apache mailing list doesn't support inline pictures, so you may share > a link to the image? > I've updated the PIP when the

Re: [DISCUSS] PIP-186: Introduce two phase deletion protocol based on system topic

On Sun, Mar 12, 2023 at 7:21 PM Yan Zhao wrote: > > > In the LedgerDeletionService start, it will create a producer for > sending > > > pending delete ledger. When deleting a ledger, the producer sends > > > PendingDeleteLedgerInfo to the system-topic. If the sent succeeds, > delete > > > the led

Re: [DISCUSS] PIP-246: Improved PROTOBUF_NATIVE schema compatibility checks without using avro-protobuf

Hi Sinan, The doc looks much better! I have a few additional comments: Pasting comment from previous emails: Can you convert the code block which is actually a quote in the beginning of the PIP to something which doesn't require to scroll horizontally so much? Use https://docs.github.com/en/get

[DISCUSS] PIP-255: Assign topic partitions to bundle by round robin

Hi all, I created a proposal to assign topic partitions to bundles by round robin: https://github.com/apache/pulsar/issues/19806 It is already running in our production environment, and it has a good performance. Thanks!

Re: [Discussion] Add a new default method to to the ManagedLedgerInterceptor

+1. I support cherry-picking it to release branches even if new default methods are added. It won't affect any existing use because the interface is customized by the 3rd party provider. No compatibility issue will happen. Thanks, Yunze On Tue, Mar 14, 2023 at 4:27 PM Enrico Olivelli wrote: > >

Re: [DISCUSS] new idea: reverse reading a topic

Hi, The way you suggest works when we know how many messages we want to read. It can be a nice feature too, but this is not my case here. Here, the goal is to read a topic from a known messageId to previous messages until a constraint depending on read messages. It looks hasPreviousMessage()

Re: Data quality problem

Hi Devin, This topic remains of great interest to me. I think there is still a wide schema usability gap between traditional batch data systems (RDBMS for example) and those in the messaging/streaming space. Pulsar provides no mechanism for real-time schema verification of > message content. Ar

Re: [DISCUSS] PIP-253: Expose producer metrics for deadLetterProducer and retryLetterProducer

Good catch by SpotBugs. What if in this method @Override public ConsumerStatsRecorder getStats() { return stats; } You change return type to ConsumerStats so it's immutable ? On Sat, Mar 11, 2023 at 4:41 AM Kai Levy wrote: > I made a start on the implementation with `setRetryLetterProduc

Re: [VOTE] PIP-253 Expose producer metrics for deadLetterProducer and retryLetterProducer

+1 (non binding) On Fri, Mar 10, 2023 at 11:36 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il Ven 10 Mar 2023, 21:36 Michael Marshall ha > scritto: > > > +1 (binding) > > > > Thanks for your PIP! Feel free to tag me to help review the PR when we > > get to that step. > > > > Thanks,

Re: [Discuss] PIP-248: Add backlog eviction metric

> > Pulsar has a feature called backlog quota (place link) Need to replace (place link) with link. >1. Find the backlog subscriptions >After received the alarm, users could request Topics#getStats(topicName, >true/false, true, true) > >

Re: [DISCUSS] PMC/Committer Emiratus status

I have found this interesting reading about this topic https://www.apache.org/dev/pmc.html#pmc-removal Quoting it here: "Typically, PMC members who are no longer able to participate will resign from the PMC. However, if a PMC chooses to remove one of its members (without that member's request or

Re: [Discussion] Add a new default method to to the ManagedLedgerInterceptor

Il giorno mar 14 mar 2023 alle ore 06:47 Gavin gao ha scritto: > > The issue is: https://github.com/apache/pulsar/pull/19727 > > This issue tries to address the index generator rolled back problem when > entries add failed. > > A new default method `afterFailedAddEntry` is added to interface > Man