Re: Preparing for Pulsar 4.0: cleaning up the Managed Ledger interfaces

In high level I see this work as needed cleanup indeed and very much needed On Tue, 11 Jun 2024 at 20:29 Lari Hotari wrote: > Hi all, > > We have the next LTS release, Pulsar 4.0, scheduled for October. The > current master branch will most likely become the 4.0 release branch in > September. >

Re: [DISCUSS] PIP-184: Cluster migration or Blue-Green cluster deployment support in Pulsar

e.org/features/ On Thu, Jul 14, 2022 at 8:13 PM Rajan Dhabalia wrote: > On Thu, Jul 14, 2022 at 9:59 AM Asaf Mesika wrote: > > > > > > > No, as it's mentioned in PIP: this API will terminate the topic so, it > > will > > > not allow any new write and p

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

Hi Haiting, I've noticed Shadow Topic is *not* covered in the documentation. Can you please add documentation for it? It's such a great feature, it's almost a waste not having it documented. Once it is, I can it to the proud list of features Pulsar have in this lovely page we recently launched:

Re: [VOTE] PIP-342: Support OpenTelemetry metrics in Pulsar client

+1 (non-binding) On Thu, Mar 14, 2024 at 8:29 PM Apurva Telang wrote: > +1 (non-binding) > > On Thu, Mar 14, 2024 at 2:12 AM mattison chao > wrote: > > > +1 (binding) > > > > Best, > > Mattison > > On Mar 14, 2024 at 15:55 +0800, Lari Hotari , wrote: > > > +1 (binding) > > > > > > -Lari > > > >

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> > I have selected these examples from the most recent discussions and they > may not be the best examples to fully illustrate the point. You should respect people's time by taking the time to craft your replies in this discussion. >From my experience, I've been contributing a lot in recent year

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I personally agree it is frustrating to update in multiple places. It's not time consuming, just annoying. Maybe we can only update for the support LTS version and onwards? On Mar 6 2024, at 1:56 pm, Kiryl Valkovich wrote: > Idea: don't require updating versioned docs from contributors. > Making

Re: [ANNOUNCE] New Committer: Kiryl Valkovich

Congrats! You are definitely a great addition to Pulsar committers! On Thu, Feb 29, 2024 at 4:58 AM Zixuan Liu wrote: > Congrats! > > Lari Hotari 于2024年2月27日周二 14:14写道： > > > Congrats, Kiryl! > > > > -Lari > > > > On Tue, 27 Feb 2024 at 06:53, tison wrote: > > > > > > The Apache Pulsar Project

PIP-264: Implementation status update

Hi, PIP-264 (approved Sep 2023) fixes many pitfalls of the current metric system inside Pulsar. We partly do so by adding another option of adding metrics: OpenTelemetry Java SDK, and then redefining the existing metrics using OTel. The first part was adding OpenTelemetry Java SDK into Pulsar in

Re: [DISCUSS] PIP-331: WASM Function API

Hi ZiCheng, Brilliant suggestion! I replied in the PR section, which I couldn't understand. On Tue, Jan 30, 2024 at 1:18 PM dragon-zhang wrote: > Hi Pulsar Community, > > I want to add a new feature that supports run WASM bytecode to the > pulsar-functions module. > > Please see the PIP: http

Re: Ability to decrease partition count in pulsar

Hey Girish, First, I say that I *love* this proposal and, in general, those types of proposals. This is what strides Pulsar towards being an even more next-generation messaging system. I read and have a few questions and brainstorming ideas popping into my mind: 1. The current design basically s

Re: [VOTE] PIP-330: getMessagesById gets all messages

+1 (non-binding) On Tue, Jan 16, 2024 at 4:43 AM Dezhi Liu wrote: > +1 (non-binding) > > Thanks, > Dezhi Liu > > On 2024/01/15 09:33:48 Zixuan Liu wrote: > > Hi Pulsar Community, > > > > Voting for PIP-330: getMessagesById gets all messages > > > > PIP: https://github.com/apache/pulsar/pull/2187

Re: [VOTE] PIP-323: Complete Backlog Quota Telemetry

The vote is now closed. The PIP is approved, with 4 +1 binding votes, by Yubaio, Mattison, Penghui and Guo. On Mon, Dec 18, 2023 at 4:55 PM mattison chao wrote: > +1(binding) > > Best, > Mattison > > > On Dec 13, 2023, at 16:22, Asaf Mesika wrote: > > > >

Re: [VOTE] PIP-320: OpenTelemetry Scaffolding

n-binding) > > > > On Mon, Dec 11, 2023 at 4:50 AM Lari Hotari wrote: > > > > > +1 (binding) > > > > > > -Lari > > > > > > On 2023/12/11 07:33:53 Asaf Mesika wrote: > > > > Hi, > > > > > > &g

[VOTE] PIP-323: Complete Backlog Quota Telemetry

Hi, I'm starting the vote for PIP-323, since it has been reviewed by several people and all comments have been resolved. Reminder: PIP-323 is introduced to fill the gap of backlog quota telemetry. It allows the user to know when a time-based backlog quota is about to exceed, and how many times i

[DISCUSS] PIP-323: Complete Backlog Quota Telemetry

picks up PIP-248 <https://github.com/apache/pulsar/issues/19601> which was left stale and unapproved, improves it a bit and will implement once approved. Thanks, Asaf Mesika

[VOTE] PIP-320: OpenTelemetry Scaffolding

into OpenTelemetry. Thank you! Asaf Mesika

Re: [DISCUSS] Introducing Apache Pulsar Office Hour Meetings

e: > >>> > >>> Hello, > >>> this sounds like a good idea. > >>> It is not clear to me who is going to run these meetings (also when > and how) > >>> > >>> Can you please share some more context ? Maybe I missed something &g

Re: [DISCUSS] PIP-320: OpenTelemetry Scaffolding

On Wed, Nov 29, 2023 at 12:18 AM Enrico Olivelli wrote: > Asaf, > > > > Il Mar 28 Nov 2023, 19:14 Asaf Mesika ha scritto: > > > Hi, > > > > This is the first sub-PIP for parent PIP-264 > > <https://github.com/apache/pulsar/pull/21080> ("En

[DISCUSS] PIP-320: OpenTelemetry Scaffolding

Hi, This is the first sub-PIP for parent PIP-264 ("Enhanced OTel-based metric system"). This PIPs goal is to introduce OpenTelemetry into Apache Pulsar. When this PIP is implemented, we will be able to start converting (not replacing) existing metrics

Re: [DISCUSS] Introducing Apache Pulsar Office Hour Meetings

I believe Mattisson wanted some feedback/suggestion before proceeding to the announcement to the users via Slack and website On Mon, Nov 20, 2023 at 5:42 PM Julien Jakubowski wrote: > Thank you for this. This will be a huge benefit to the user community! > Could you please share this on the co

Re: [DISCUSS] Introducing Apache Pulsar Office Hour Meetings

I think it's a wonderful idea. Since community engagement in the community meetings are quite low (1-3 people top), hopefully we can engage more users through those open office hours. On Fri, Nov 17, 2023 at 5:11 AM mattison chao wrote: > Dear Apache Pulsar Community, > > I hope you are doing

Re: [DISCUSS] Replace stale bot with ping-pong workflow

Submitted a PR to disable it: https://github.com/apache/pulsar/pull/21549 On Tue, Nov 7, 2023 at 3:58 PM Asaf Mesika wrote: > Tison let's start as you suggested by disabling it > > > On Tue, May 16, 2023 at 5:13 AM Yunze Xu wrote: > >> +1 to me >> >> Thank

Re: [DISCUSS] PIP-310: Support custom publish rate limiters

I just want to add one thing to the mix here. You can see by the amount of plugin interfaces Pulsar has, somebody "left the door open" for too long. You can agree with me that the number of those interfaces is not normal for any open source software. I know HBase for example, or Kafka - never seen

Re: [DISCUSS] Replace stale bot with ping-pong workflow

Tison let's start as you suggested by disabling it On Tue, May 16, 2023 at 5:13 AM Yunze Xu wrote: > +1 to me > > Thanks, > Yunze > > On Sun, May 14, 2023 at 9:28 PM Dave Fisher wrote: > > > > Hi - > > > > I have not looked at all your links but I think this is a great idea. > This will help e

Re: Reporting and tooling to detect thread leaks in Pulsar tests

e last few weeks. Without support for > detecting > > > the resource leaks, it's really hard to keep the test suite clean. > > > > > > > > > > > > Looking forward to more reviews on > > > https://github.com/apache/pulsar/pull/21450

Re: Reporting and tooling to detect thread leaks in Pulsar tests

Larry, I know there is a way to add like a Job summary, so we can write it there - do you think this can increase visibility? On Sun, Oct 29, 2023 at 4:53 AM Lari Hotari wrote: > Hi all, > > I have submitted a PR (https://github.com/apache/pulsar/pull/21450) which > includes changes to add repor

Re: [DISCUSS] Roll up project status for pulsar-helm-chart

Tison, can we mark this repo as suggested? On Tue, Aug 8, 2023 at 12:24 PM Matteo Merli wrote: > Thanks Tison, > > I fully agree that we should have a clear representation of the actual > status of the Helm chart, so that users can have the correct expectation. > > In particular I think we shoul

Re: [DISCUSS] PIP-310: Support custom publish rate limiters

Replied in PR. On Thu, Oct 19, 2023 at 3:51 PM Girish Sharma wrote: > Hi, > Currently, there are only 2 kinds of publish rate limiters - polling based > and precise. Users have an option to use either one of them in the topic > publish rate limiter, but the resource group rate limiter only uses

Re: [DISCUSS] PIP-309: Adding Pulsar Client Stats Reporter

I've replied in the PR it self On Fri, Oct 20, 2023 at 2:24 AM Ying wrote: > Hi dev, > > Currently, Pulsar Client can provide recorded stats for both Producer and > Consumer, but not all stats are fixed values during the statsInterval. So > start the PIP-309 to add the Pulsar Client Stats Report

Re: [DISCUSS] Consistent code style (esp. ws/indent) and autotools

huge change, but to be more friendly to > developers, > > we should document the workarounds for the git blame issue. And we > should apply > > the spotless tool to every active branches. > > > > > On Sep 3, 2023, at 19:43, Asaf Mesika wrote: > > > > >

Re: [DISCUSS] Consistent code style (esp. ws/indent) and autotools

correction > >> seems like a waste of volunteer energy. > >> > >> Best, > >> Dave > >> > >> Sent from my iPhone > >> > >>>> On Aug 31, 2023, at 9:05 PM, Zixuan Liu wrote: > >>> > >>> This idea

Re: [DISCUSS] Consistent code style (esp. ws/indent) and autotools

Opentelemetry-java employs both spotless for coding style You run "./gradlew spotlessCheck" and it shows the problems. You run "./gradlew spotlessApply" to automatically fix it. It also uses errorprone to detect bugs. I wonder if we can run it only in GitHub PRs, so we can instruct it to run only

Re: [VOTE] PIP-264: Enhanced OTel-based metric system

Thank you all for your review and corresponding votes. The PIP vote has passed with 3 binding +1 votes by Matteo, Lari and Hang. On Wed, Aug 30, 2023 at 3:40 PM Lari Hotari wrote: > +1 (binding) > > -Lari > > On Mon, Aug 28, 2023 at 5:55 PM Asaf Mesika wrote: > > > Hi

[VOTE] PIP-264: Enhanced OTel-based metric system

Hi, I'm very happy to start the vote process for PIP-264. PIP is located at https://github.com/apache/pulsar/pull/21080. The PIP was at the discussion stage from April 27th (~4 months). I want to express my sincere gratitude to Matteo, Hang and Larry for taking the time to read through the *enti

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

I've relocated the PIP content from the issue ( https://github.com/apache/pulsar/issues/20197) to a PR ( https://github.com/apache/pulsar/pull/21080) so I could add TOC and also be inlined with the new process. On Mon, Aug 28, 2023 at 5:46 PM Asaf Mesika wrote: > Thanks for taking the

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

. > > > > > > -- > > Matteo Merli > > > > > > > > On Wed, Jun 14, 2023 at 6:10 PM Devin Bost wrote: > > > > > > Thanks for the details, Devin. Curios - 'We' stands for which > company? > > > > > > Wh

Re: [VOTE] PIP-268: Add support of topic stats/stats-internal using

So, I'm trying to summarize the motivation you have for this feature and what we know about it, so we can proceed with discussion. I think Pulsar users should be happy with using Pulsar and not hit a "wall", on the other hand, there are cons to adding it: * Exposing more to the API, adding more sur

Can we archive https://github.com/apache/pulsar-release?

Seems quite neglected

Re: New pip process reminder

w.apache.org/foundation/glossary.html#MajorityApproval> , and > the description of the voting process > <https://www.apache.org/foundation/voting.html>. So if I summarize, a PIP needs to follow the "the proposal requires three positive votes and no negative votes in order to

Re: [DISCUSS] Pluggable Pulsar Functions runtime to support new runtimes

Lari, would it be possible to explain in more detail the paint points you're describing? You say processing messages individually is slow; hence, processing them in batches is better. I guess it's especially useful if you need to group a batch based on a key. What I don't understand is how the fra

Re: [DISCUSS] PIP-267: Support multi-topic messageId deserialization to ack messages

lack#dev channel if you have more implementation questions. > > Thanks, > Rajan > > > > On Tue, Jun 20, 2023 at 11:31 AM Asaf Mesika > wrote: > > > On Tue, Jun 20, 2023 at 9:39 AM Rajan Dhabalia > > wrote: > > > > > > So you say in that s

Re: New pip process reminder

irectly making it difficult for many Pulsar committers and contributors > who don't belong to specific enterprises. > > Thanks, > Rajan > > > > > On Tue, Jun 20, 2023 at 12:14 PM Asaf Mesika > wrote: > > > Hi, > > > > This is just a reminder

New pip process reminder

Hi, This is just a reminder that PMC/Committers can only merge the PIP PR when the vote thread is concluded and in a positive manner, as described (" a lazy majority of at least 3 binding +1s votes") So please, before clicking that merge button, double-check those two conditions Thanks! Asaf

Re: [VOTE] PIP-267: Support multi-topic messageId deserialization to ack messages

-1 (non-binding) The reason I'm asking all these questions on the DISCUSS is that I still haven't managed to understand how you plan to solve the pain described. Not to mention the lack of information in the design document I mentioned in my replies to the discussion This DISCUSS thread is not re

Re: [DISCUSS] PIP-267: Support multi-topic messageId deserialization to ack messages

n't get it. Can you please help me understand this by elaborating so anyone, including me, can fully understand it? Preferably all your answers should be injected into the document, of course. Thanks! Asaf > Thanks, > Rajan > > On Mon, Jun 19, 2023 at 5:45 AM Asaf Mesika wrote:

Re: Improving the usability of the bookie Isolation feature

I want to add only one step to your plan. If you introduce this flag in Y.X, then in Y.(X+1), let's remove this flag and keep the "true" value as the behavior. On Mon, Jun 19, 2023 at 4:57 AM horizonzy wrote: > Background > > In the Pulsar, it has two features: > >- > >The first feature

Re: [VOTE] PIP-275: Introduce topicOrderedExecutorThreadNum to deprecate numWorkerThreadsForNonPersistentTopic in configuration

+1 (non binding) On Mon, Jun 19, 2023 at 9:19 AM 丛搏 wrote: > +1(binding) > > Thanks, > Bo > > houxiaoyu 于2023年6月19日周一 14:04写道： > > > > Hi, community: > > > > This thread is to start a vote for PIP-275: Introduce > > topicOrderedExecutorThreadNum to deprecate > > numWorkerThreadsForNonPersistent

Re: [DISCUSS] PIP-267: Support multi-topic messageId deserialization to ack messages

run than keeping the protocol > clear. > > > > If the above options are not feasible. At least, we should clarify > > it in the proposal and add comments in the proto file to avoid > > other clients transmitting the topic name to the broker. > > > >

Re: [VOTE] PIP-276: Add metric `pulsar_topic_load_times

Voting +1 (non-binding) On Fri, Jun 16, 2023 at 12:23 PM guo jiwei wrote: > @Asaf Thanks, I have addressed the comment. > > Regards > Jiwei Guo (Tboy) > > > On Fri, Jun 16, 2023 at 3:55 AM Asaf Mesika wrote: > > > -1 (non-binding) > > > > I'm

Re: [VOTE] PIP-276: Add metric `pulsar_topic_load_times

-1 (non-binding) I'm perfectly ok with the idea; just please fix the document. It looks too messy. Even 1 paragraph changes can look neat and clean. I left notes in the draft PR you opened for the pip. I'll change my non-binding vote once that's done. On Thu, Jun 15, 2023 at 11:07 AM guo jiwei

Re: Pulsar roadmap

/8 WDYT? On Wed, Jun 14, 2023 at 11:19 AM Enrico Olivelli wrote: > Asaf, > > Il Dom 4 Giu 2023, 15:37 Asaf Mesika ha scritto: > > > Hi, > > > > > > Do we have a place we manage future Pulsar roadmap? Big ticket items, > > smaller ticket ones? > >

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

f tue changes for users > are > > as trivial as replacing the queries in the grafana dashboard or in > alerting > > systems. > > > > Asaf, do you have prototype? Built over any version of Pulsar? > > > > Also, it would be very useful to start an initiative to coll

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

ed > alerts. > > In my experience you usually care about: > - in/out traffic (rates, bytes...) > - number of producer, consumers, topics, subscriptions... > - backlog > - jvm metrics > - function custom metrics > > I am trying to understand. Do you mean I can use it as

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

can't maintain > compatibility then it's a big red flag and not acceptable for the Pulsar > community. > > Thanks, > Rajan > > On Sun, May 21, 2023 at 9:01 AM Asaf Mesika wrote: > > > Thanks for the reply, Enrico. > > Completely agree. > > This mad

Re: [VOTE] PIP-274: Add metric `pulsar_topic_load_times`

Your pip number is wrong. Better close this thread and open a new one. Recommended to include a link to the PIP PR On Mon, Jun 12, 2023 at 9:15 AM guo jiwei wrote: > Hi, community: > The metrics are all started with `pulsar_`, so that both users and > operators can quickly find the metrics o

Re: [DISCUSS] PIP-263: Just auto-create no-partitioned DLQ And Prevent auto-create a DLQ for a DLQ

I agree with you. wasAutoCreated seems a bit like a patch in light of the recent issues. On Fri, Jun 9, 2023 at 9:03 AM Michael Marshall wrote: > > In general, these problems hint to me that we need better definitions > > for "system" and "special" topics that break the rules of auto created >

Re: [VOTE] PIP-272

After several ping pongs over the PR, I'm changing my vote: +1 (non-binding) Just please make sure to review all pending grammar suggestions. On Tue, Jun 6, 2023 at 10:53 PM Asaf Mesika wrote: > I'm sorry for not getting back to you sooner: Weekend, work, etc. > > I vote -

Re: [VOTE] PIP-272

I'm sorry for not getting back to you sooner: Weekend, work, etc. I vote -1 (non-binding), as I found something rather disturbing in the design. Can we please go back to the discussion (in the PR)? Rui Fu - I see you voted +1 (binding) - what do you think about the comments I've made? Thanks!

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

doing - very carefully - I've taken 11 months to design this. It's as open as it can be. I shared my intent before I started back in July in the community meetings. I published a preliminary idea doc in October to the community, and then went heads down to solve this huge challenge and wrote t

Re: [DISCUS] PIP-273: Add metric prefix for `topic_load_times`

You will break anyone using this from 2017. Perhaps add a new metric with correct name and mark that one deprecated. Next LTS version it can be removed? How does this things managed? On Sat, Jun 3, 2023 at 2:34 AM Dave Fisher wrote: > There are two PIP-273s. Whichever was last please update. >

Pulsar roadmap

Hi, Do we have a place we manage future Pulsar roadmap? Big ticket items, smaller ticket ones? I mean, I know we have GitHub issues, but that’s a forest. I was wondering if we have created a way to display those as a roadmap, or hierarchy? Thanks, Asaf

Re: [DISUCSS] Fix and republish the pulsar-all image for Pulsar 3.0.0

; scripts(build.sh > > > > and publish.sh) and use the shell scripts to build the image. > > > > > > > > I have verified the PR, and it works well. Please see more detail in > > > > the PR description. > > > > > > > > Thanks, >

Re: [DISCUSS] PIP-272 Add a `StateStoreConfig` to the `WorkerConfig`

SON string that can be deserialized to a `Map > Object>`, updated in pip > > 7. it should be `pulsar-admin functions localrun` command, updated in pip > > 8. the `stateStorageServiceUrl` won't be touched > > > > Sincerely > > Pengcheng Jiang > > >

PLEASE NOTE - from now on PIPs are PR based

Hi, I've completed all steps necessary for implementing "PIP-265: PR-based system for managing and reviewing PIPs" ( https://github.com/apache/pulsar/issues/20207). PLEASE NOTE, from now on, PIPs are to be submitted *through Pull Request*. You can read the process detail here: https://github.com

Re: [DISUCSS] Fix and republish the pulsar-all image for Pulsar 3.0.0

Good catch! How do you suggest we prevent it from happening next time? On Mon, May 29, 2023 at 1:34 PM Zike Yang wrote: > Hi, all > > Recently, we found an issue with the `pulsar-all:3.0.0` image. The > pulsar library included in `pulsar-all:3.0.0` is the version of > 2.11.0: > > ``` > docker r

Re: [DISCUSS] PIP-272 Add a `StateStoreConfig` to the `WorkerConfig`

Hi Pengcheng, Looks like a solid improvement, definitely helping people using their own state store. I have a few comments: 1. Background knowledge should explain what is a state storage 2. Move problem description from Background Knowledge to Motivation. I'm quoting the template to understand

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

I pushed the first PR defining the new process: https://github.com/apache/pulsar/pull/20418 On Wed, May 10, 2023 at 7:46 PM Asaf Mesika wrote: > The documentation has severe issues with diagrams in general, today. > There is no standard way yet to do it. We have all kinds of ways

Re: [VOTE] PIP-265: PR-based system for managing and reviewing PIPs

Who can help me by updating the wiki with pass vote to this? On Mon, May 22, 2023 at 4:20 PM Asaf Mesika wrote: > Thank you all for your votes. > > Summary > Binding votes: Peghui, Hang, Enrico, Mattisson, > Non binding: Max, Zike > Binding no vote (0): Dave Fisher > >

Re: [VOTE] PIP-265: PR-based system for managing and reviewing PIPs

s On Mon, May 22, 2023 at 3:27 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il giorno dom 21 mag 2023 alle ore 18:05 Asaf Mesika > ha scritto: > > > > We're not dropping. We're allowing both. > > Quoting from PIP below. > > Are yo

Re: [DISCUSS] PIP-270 Add config to set metadata size threshold for compression.

Hi, I have a couple of questions: current we support to set compression on ManagedLedger and ManagedCursor > metadata > by managedLedgerInfoCompressionType and managedCursorInfoCompressionType Can you please elaborate what is the metadata of ManagedLedger and ManagedCursor? Where is that metada

Re: [VOTE] PIP-265: PR-based system for managing and reviewing PIPs

> to understand decisions years in the future. Just yesterday I reviewed > email threads in another project from 16 years ago. > > > > Best, > > Dave > > > > Sent from my iPhone > > > > > On May 10, 2023, at 3:52 AM, Asaf Mesika > wrote: > &g

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

ng systems, dashboards and know-how in > troubleshooting Pulsar problems in production and dev > > Best regards > Enrico > > Il giorno lun 15 mag 2023 alle ore 02:17 Dave Fisher > ha scritto: > > > > > > > > > On May 10, 2023, at 1:01 AM, Asaf

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

Bumping, as I have received only 1 partial feedback so far on the PIP. Any feedback is highly appreciated! Thanks! Asaf On Wed, May 10, 2023 at 11:00 AM Asaf Mesika wrote: > > > On Tue, May 9, 2023 at 11:29 PM Dave Fisher wrote: > >> >> >> > On May 8, 202

Re: [DISCUSS] PIP-268: Add support of topic stats/stats-internal using client api

parate http endpoints. So, this api addresses scale, > performance, and use accessibility in pulsar. > > Thanks, > Rajan > > On Thu, May 11, 2023 at 6:24 AM Asaf Mesika wrote: > > > Before I dive into the PIP, I have several questions on the background > > provided below

Re: [DISCUSS] PIP-267: Support multi-topic messageId deserialization to ack messages

must not > know about different implementation of messageId and our goal is to > maintain that abstraction without telling user about MessageIdImpl or > TopicMessageIdImpl. > > Thanks, > Rajan > > > On Thu, May 11, 2023 at 7:29 AM Asaf Mesika wrote: > > > Hi Rajan,

Re: [DISCUSS] Add checklist for PMC binding vote of PIP

ve a summary list and select which of them are > understood. But why do we need a checklist? Is there any reason that > any item of the list is not selected? > > Thanks, > Yunze > > > > On Wed, May 10, 2023 at 3:32 PM Asaf Mesika wrote: > > > > Hi Yunze, >

Re: [VOTE] PIP-270 Add config to set metadata size threshold for compression

30 minutes is not enough time to read a pip :) On Thu, 11 May 2023 at 19:04 lifepuzzlefun wrote: > Hello Pulsar community, > > This thread is to start a PIP-270 Add config to set metadata size > threshold for compression > > > Discussion thread: > https://lists.apache.org/thread/6930c74m31rflr

Re: [DISCUSS] PIP-267: Support multi-topic messageId deserialization to ack messages

Hi Rajan, A few comments on the PIP as I couldn't understand it fully as some pieces of information is missing. First, I would like to remind about the rules, that exists in the beginning of the PIP template: In this specific case 1. I would include explanation and detail the data structures

Re: [DISCUSS] PIP-268: Add support of topic stats/stats-internal using client api

Before I dive into the PIP, I have several questions on the background provided below: On Tue, May 9, 2023 at 9:08 AM Rajan Dhabalia wrote: > Hi, > > Right now, Pulsar provides the topic's stats and stats-internal over HTTP > admin API, and this stats data is used by user applications and also

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

a PIP to add documentation to describe the feature. On Wed, May 10, 2023 at 3:58 PM Dave Fisher wrote: > > > Sent from my iPhone > > > On May 10, 2023, at 12:01 AM, Asaf Mesika wrote: > > > > On Tue, May 9, 2023 at 8:03 PM Dave Fisher wrote: > > > >

[VOTE] PIP-265: PR-based system for managing and reviewing PIPs

Hi, I'm starting the vote process for PIP-265. Link: https://github.com/apache/pulsar/issues/20207 Thanks! Asaf

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

for the PIP. Thanks! Asaf On Wed, May 10, 2023 at 10:00 AM Asaf Mesika wrote: > > > On Tue, May 9, 2023 at 8:03 PM Dave Fisher wrote: > >> >> >> > On May 9, 2023, at 5:47 AM, Asaf Mesika wrote: >> > >> > On Tue, May 9, 2023 at 5:18 AM Hang Ch

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

On Tue, May 9, 2023 at 11:29 PM Dave Fisher wrote: > > > > On May 8, 2023, at 2:49 AM, Asaf Mesika wrote: > > > > Your feedback made me realized I need to add "TL;DR" section, which I > just > > added. > > > > I'm quoting it here. It

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

ty of developers and users before we go and spend such a huge amount of work. 2nd reason is that the PIP was done to ensure all general sub PIPs will align and nothing will surprise us and find out after 1 year of work that we have stumbled into a wall which we can't pass. The master gives y

Re: [DISCUSS] Add checklist for PMC binding vote of PIP

breakage, divergence, and not > everyone will agree on the result. You worked for 11 months in apparent > secrecy, yet seemingly ignored Lari’s similar open discussion about scaling > which occurred in the same time frame. > > > > Being overly dependent on rules is not a replaceme

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

On Tue, May 9, 2023 at 8:03 PM Dave Fisher wrote: > > > > On May 9, 2023, at 5:47 AM, Asaf Mesika wrote: > > > > On Tue, May 9, 2023 at 5:18 AM Hang Chen wrote: > > > >> Thanks for driving this discussion. > >> > >> I agree to change the

Re: [DISCUSS] Add checklist for PMC binding vote of PIP

r Code” > > I'm trying to suggest ways which in my opinion would make the community better. I'm ok with getting concrete feedback why those ways do not achieve that. > Best, > Dave > > Sent from my iPhone > > > On May 7, 2023, at 9:55 AM, Asaf Mesika wrote: &

Re: Making Pulsar JIRA read only

read-only. > > >> > > >> I don't have the permission to perform, though. IMO this can go > through a > > >> lazy consensus process that any PMC member can help archive the > project > > >> while we can always reopen on demand. > >

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

r, they will want to migrate to it, despite the breaking change. This was a very short summary. You are most welcomed to read the full design document below and express feedback, so we can make it better. On Sun, May 7, 2023 at 7:52 PM Asaf Mesika wrote: > > > On Sun, May 7, 2023 at 4:23 PM

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

"wiki" folder, but it's not displayed in the wiki, right? > > Thanks, > Penghui > > On Sun, May 7, 2023 at 5:52 PM Asaf Mesika wrote: > > > Ping, in case it was lost in the barrage of mails > > > > On Sun, Apr 30, 2023 at 10:38 A

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

the README. All links pointing to that `PIP.md` file (from wiki, pulsar-site) will be > amended to point to the new README file. > Thanks, > Penghui > > On Sun, May 7, 2023 at 5:52 PM Asaf Mesika wrote: > > > Ping, in case it was lost in the barrage of mails

Re: [VOTE] PIP-261: Restructure Getting Started section

Who can help me update in https://github.com/apache/pulsar/wiki that it has passed? On Tue, May 9, 2023 at 5:01 PM Asaf Mesika wrote: > The vote has passed with 4 of binding +1 and 1 non-binding +1. > > > Binding: > Yunze Xu > Hang Chen > Yu > Penghui > > Non-bind

Re: [VOTE] PIP-261: Restructure Getting Started section

The vote has passed with 4 of binding +1 and 1 non-binding +1. Binding: Yunze Xu Hang Chen Yu Penghui Non-binding: Tison Thank you all, Asaf On Sun, May 7, 2023 at 12:20 PM Asaf Mesika wrote: > Hi, > > PIP-261 as been opened for quite some time, garnered feedback from 3 > peopl

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

the existing one to > "pip". > > I mean, we'd better don't use two dirs for proposals. > > > > Thanks, > > Penghui > > > > On Sun, May 7, 2023 at 5:52 PM Asaf Mesika > wrote: > > > > > Ping, in case it

Re: [VOTE] PIP-261: Restructure Getting Started section

> > > > > > > > Best, > > > > tison. > > > > > > > > > > > > Yunze Xu 于2023年5月7日周日 20:12写道： > > > > > > > > > +1 (binding) > > > > > > > > > > Than

Re: [DISCUSS] Add checklist for PMC binding vote of PIP

I understand that Dave, and hence I only started a discussion. What do you think of last reply I made there? On Sun, May 7, 2023 at 5:31 PM Dave Fisher wrote: > > > Sent from my iPhone > > > On Apr 18, 2023, at 5:14 AM, Asaf Mesika wrote: > > > > The problem I

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

ffort a lot! > > [1] https://lists.apache.org/thread/04jxqskcwwzdyfghkv4zstxxmzn154kf > [2] > https://github.com/streamnative/kop/blob/master/kafka-impl/src/main/java/io/streamnative/pulsar/handlers/kop/stats/PrometheusMetricsProvider.java > > Thanks, > Yunze > > O

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

I'm very appreciative for feedback from multiple pulsar users and devs on this PIP, since it has dramatic changes suggested and quite extensive positive change for the users. On Thu, Apr 27, 2023 at 7:32 PM Asaf Mesika wrote: > Hi all, > > I'm very excited to release a PIP I

Re: [DISCUSS] Add checklist for PMC binding vote of PIP

Ping, in case it was lost in the barrage of mails On Sun, Apr 30, 2023 at 3:54 PM Asaf Mesika wrote: > Is it ok if we use the following vote template? Per comments above, it > will be optional, yet recommended. > > +1 (binding) > > [v] PIP has all sections detailed i

Re: [DISCUSS] PIP-265: PR-based system for managing and reviewing PIPs

Ping, in case it was lost in the barrage of mails On Sun, Apr 30, 2023 at 10:38 AM Asaf Mesika wrote: > Hi, > > I've summarized all comments from > https://lists.apache.org/thread/5kpddlfh5xdbsjmv47ymnk3z6wd92jbh into a > PIP. > > PIP: https://github.com/apache/pu

  1   2   3   >