Re: [VOTE] PIP-254: Support configuring client version with a description suffix

+1 (binding) Enrico Il giorno mer 29 mar 2023 alle ore 09:16 丛搏 ha scritto: > > +1 (binding) > > Thanks, > Bo > > Lin Lin 于2023年3月27日周一 17:49写道： > > > > +1 > > > > Thanks, > > Lin Lin > > > > On 2023/03/15 07:54:20 Yunze Xu wrote: > > > Hi all, > > > > > > This thread is to start the vote for P

Re: [DISCUSS] We must change the way we review PIPs

I agree that we should finally have PIPs committed to git somewhere. When a PIP is approved it can be committed, but we must run the VOTE and wait for 3 binding +1, this is hard to do with a PR. It already happened a few times that people committed patches related to unapproved PIPs. Regarding t

[DISCUSS] Dropping the StreamingDispatcher

Hello, It has been a long time that we have in the Pulsar code a new experimental Dispatcher implementation named StreamingDispatcher. https://github.com/apache/pulsar/pull/9056 There are many flaky tests about that feature and I believe that it has never been used in Production by anyone, becaus

Re: [DISCUSS] Dropping the StreamingDispatcher

e code now in Pulsar 3.0 Enrico > Thanks, > Yunze > > On Tue, Apr 4, 2023 at 3:09 PM Gavin gao wrote: > > > > +1, I totally agree with this idea. > > > > Enrico Olivelli 于2023年4月4日周二 14:47写道： > > > > > Hello, > > > It has been

Re: [BUGS] Pulsar 3.0 GKE Cluster Won't Start

Dave, IIUC (from offline discussion) those tests started to fail only recently, as we run those tests against the master branch of apache/pulsar repo. Does the beginning of failures match the upgrade to BK 4.16 ? The problem may be related to the handling of ByteBufs, IIRC there are a few changes

Re: [DISCUSS] forbid user to upload `BYTES` schema

Il giorno ven 14 apr 2023 alle ore 16:48 Christophe Bornet ha scritto: > > The change was not reverted for 3.0.0-RC so in the current state the > Flink Pulsar catalog won't work with Pulsar 3.0. > To give more details, Flink Pulsar stores Flink Table metadata in the > metadata of BYTES schema topi

Re: [Discuss] Suggestion for a "clear" parameter in Pulsar-admin to simplify tenant and namespace cleanup

The proposal sounds really useful, especially for automated testing. +1 Enrico Il giorno sab 15 apr 2023 alle ore 12:07 Xiangying Meng ha scritto: > > Dear Girish, > > Thank you for your response and suggestion to extend the use of the > `boolean force` flag for namespaces and tenants. > I under

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

Asaf, I understand your intent. I think that when anyone casts a +1, especially with '(binding)' they know well what they are doing. It is not an 'I like it', but it is an important assumption of responsibility. This applies to all the VOTEs. Requiring this checklist may be good in order to help

Re: [Discuss] Suggestion for a "clear" parameter in Pulsar-admin to simplify tenant and namespace cleanup

nt and namespace intact > > while > > > cleaning up their contents. > > Ah, I see now. Yes, in that case a clear command is better. Will this > > command also take into account the value of the broker config > > `forceDeleteNamespaceAllowed` in case someone is c

Re: [NOTICE] Please don't cherry-pick commits to branch-3.0 without consensus

Il Lun 24 Apr 2023, 12:35 PengHui Li ha scritto: > Can we cherry-pick fixes for the new features that were introduced to > 3.0.0? > We do lots of chaos testing, stress testing for new delayed messages, and > load balancer > before the 3.0.0 release. Is it reasonable to have the fixes without > re

Re: [DISCUSS] Release Pulsar C++ Client 3.2.0

+1 Enrico Il Lun 24 Apr 2023, 11:28 Zike Yang ha scritto: > +1 > > Thanks, > Zike Yang > > On Fri, Apr 21, 2023 at 12:42 PM Yunze Xu > wrote: > > > > Hi all, > > > > I would like to propose releasing the Pulsar C++ Client 3.2.0. > > > > It has been over 2 months since the last release (3.1.2)

Re: [VOTE] Reactive Java client for Apache Pulsar 0.3.0 Candidate 1

I am not able to see the tests passing. I am on M1, I tried with JDK11 and JDK17. I have also tried to run them with amd64 emulation, same results. See the details below Enrico rg.apache.pulsar.reactive.client.adapter.ReactiveMessagePipelineE2ETest Test shouldConsumeMessages() FAILED (50.2s

Re: [VOTE] Reactive Java client for Apache Pulsar 0.3.0 Candidate 1

+1 (binding) - Run unit tests locally (It turned out that I had a problem on my docker environment. I apologize for the noise) - Verified signatures and digests Thank you Enrico Il giorno mer 26 apr 2023 alle ore 09:43 Enrico Olivelli ha scritto: > > I am not able to see the tests passin

Re: [VOTE] Pulsar Release 3.0.0 Candidate 4

+1 (binding) - Verified checksums and signatures - Built from sources and run smoke tests with Pulsar standalone/pulsar-perf/pulsar-shell - Verified that using Pulsar 3.0 with the JMS API (Starlight for JMS) works well and the JMS 2.x TCK fully passes (https://github.com/datastax/pulsar-jms/pull/1

Re: [ANNOUNCE] Apache Pulsar 3.0.0 released

Congratulations ! This is a great milestone for our community ! Enrico Il giorno mer 3 mag 2023 alle ore 04:22 tison ha scritto: > > Cool! > > Thanks to the release managers' work and everyone who make this release > happen! > > Best, > tison. > > > Zike Yang 于2023年5月3日周三 10:03写道： >> >> The A

Re: [VOTE] PIP-255: Make the partition assignment strategy pluggable

+1 (binding) Enrico Il giorno mar 9 mag 2023 alle ore 08:10 Yunze Xu ha scritto: > > +1 (binding) > > The separated TopicBundleAssignmentStrategy and bundleSplitListener LGTM. > > Typo: > * TopicBunldeAssignmentFactory -> TopicBundleAssignmentFactory > * TopicBunldeAssignmentStrategy -> TopicBun

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

Makes sense to me. Thanks for your contribution Enrico Il giorno gio 11 mag 2023 alle ore 18:01 lifepuzzlefun ha scritto: > > Dear Pulsar community, > > > I create a pip aim to add configuration on size based metadata compresssion. > > > https://github.com/apache/pulsar/issues/20307 > > > We wel

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

Hello lifepuzzlefun, thanks for your proposal I believe that it is too early to start a VOTE as the discussion has not happened yet. Side note: this change is small and it doesn't introduce breaking API changes, I am not sure that we need a PIP for it. Enrico Il giorno gio 11 mag 2023 alle ore

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

I understand the need for this PIP and I support it, but I have some questions/open points. I wonder if we should define a smaller subset of the stats/internal stats to serve to the clients using this new Request/Response. Maybe it is better to serve only the minimal amount of data that is useful.

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

Asaf, thanks for contributing in this area. Metrics are a fundamental feature of Pulsar. Currently I find it very awkward to maintain metrics, and also I see it as a problem to support only Prometheus. Regarding your proposal, IIRC in the past someone else proposed to support other metrics system

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

+1 (binding) The proposal makes sense to me. Let's try Thanks for carrying on with this initative Enrico Il giorno lun 15 mag 2023 alle ore 05:23 Max Xu ha scritto: > > +1 (non-binding) > > Thanks for driving this helpful proposal! > > Best, > Max Xu > > > On Wed, May 10, 2023 at 6:52 PM Asaf M

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

Dave, I don't think that we are dropping the discussion on the mailing list. In that case I would cast a -1. Enrico Il giorno mar 16 mag 2023 alle ore 06:27 Dave Fisher ha scritto: > > -0 (binding) having discussions on the mailing list makes it much easier to > understand decisions years in th

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

people gravitate towards and what’s more convenient and consider >refining that. > > > On Tue, May 16, 2023 at 8:55 AM Enrico Olivelli wrote: > > > Dave, > > I don't think that we are dropping the discussion on the mailing list. > > In that case I would

Re: [DISCUSS] PIP-271: Add broker health check status into prometheus metrics #20147

Vineeth, Il Mer 24 Mag 2023, 21:57 vineeth p ha scritto: > Hello, > > Broker metrics don't have anything to indicate the health of the broker (to > indicate if the broker is active). In Prometheus broker metrics which are > used for monitoring, it will be useful if metrics also show the broker >

Re: Question about Apache Foundation content policies on Pusar website

Kiryl, Il Gio 25 Mag 2023, 13:00 Kiryl Valkovich ha scritto: > Hi, > I’d like to add information about available trainings, courses, and > service providers to the Pulsar website. https://pulsar.apache.org/ > > Like what Kubernetes do at Linux Foundation: > https://kubernetes.io/training/ > http

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

Looks good +1 Enrico Il Lun 29 Mag 2023, 04:47 Pengcheng Jiang ha scritto: > Dear Pulsar community, > > I created a pip to make pulsar functions' `StateStoreProvider` configurable > with custom configurations: https://github.com/apache/pulsar/issues/20419 > > Any feedback and suggestions are w

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

I am really worried about the process. When we ran the VOTE and we provided the docker images, were they already broken ? In any case we cannot overwrite those images, they have been cached all over the world now. It is safer to cut a new 3.0.1 release and run a VOTE. Maybe we can remove the o

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

Yubiao, I understand your problem: DLQ and retry topic don't play well with automatic topic creation. We are introducing wire protocol changes and also starting to add topic properties for every new topic (they come with a cost on metadata). I am not sure that adding the purposeOfAutoCreatedTopi

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

-1 I had missed the discussion thread. Please follow up there Enrico Il giorno mer 31 mag 2023 alle ore 09:07 Yubiao Feng ha scritto: > > Hi Pulsar Community > > This thread is to start the vote for PIP 263. > I'm starting the voting process for PIP-263. > > DISCUSS: https://lists.apache.org/thr

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

-1 I had missed the discussion thread. Please follow up there Enrico Il giorno ven 5 mag 2023 alle ore 17:04 Yubiao Feng ha scritto: > > Hi Pulsar Community > > This thread is to start the vote for PIP 259. > > Discussion: *https://lists.apache.org/thread/tp25lom2ggztljlo76krsldo270f293j >

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

/ \ > > > -DskipTests \ > > > -Pdocker -Pdocker-push \ > > > -Ddocker.platforms=linux/amd64,linux/arm64 \ > > > -Ddocker.organization=snzkyang \ > > > -pl docker/pulsar,docker/pulsar-all > > > ``` >

Re: [VOTE] PIP-273: Enable hostname verification by default

+1 (binding) Enrico Il Mar 6 Giu 2023, 10:32 Yunze Xu ha scritto: > +1 (binding) > > Thanks, > Yunze > > On Tue, Jun 6, 2023 at 2:09 PM Michael Marshall > wrote: > > > > +1 (binding) > > > > - Michael > > > > On Tue, Jun 6, 2023 at 1:08 AM Michael Marshall > wrote: > > > > > > Hello, > > > >

Re: [DISCUSS] PIP-275: Introduce numWorkerThreadsForPersistentTopic to deprecate numWorkerThreadsForNonPersistentTopic in configuration

I would call it numWorkersTopicOrderedExecutor and remove "persistent/non-persistent" from the name. Or alternatively we could introduce a topicOrderedExecutor for persistent topics. Unfortunately the topicOrderedExecutor is now used for many things (I also used it the wrong way when I introduced

Re: [DISCUSS] which versions are EOL?

Micheal, Il giorno ven 9 giu 2023 alle ore 07:54 Michael Marshall ha scritto: > > Hi Pulsar Community, > > I recently noticed this page on our website: > https://pulsar.apache.org/contribute/release-policy/#supported-versions > > It shows that only 2.11 and 3.0 are active and security support. >

Re: [DISCUSS] Release Pulsar 3.0.1

I have reported a few problems about ExtensibleLoadManagerImpl (PIP-192) on k8s. I would lile to see the related patches merged, this way it will be easier for users to test this new feature. BTW it is not a blocker. There are already enough fixes to motivate a release +1 Enrico Il Sab

Re: [DISCUSS] Release Pulsar 3.0.1

Il Lun 12 Giu 2023, 02:23 PengHui Li ha scritto: > Do we need to have https://github.com/apache/bookkeeper/pull/3979 > in the 3.0.1 release? since it's a critical issue for BookKeeper. > Yes we do Enrico > > Thanks, > Penghui > > On Sun, Jun 11, 2023 at 12:0

Re: Pulsar roadmap

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? > 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, o

Re: [June 30th] Apache Pulsar Meetup Japan #5 is coming!

Great news! Thanks for sharing Enrico Il Ven 2 Giu 2023, 05:09 tison ha scritto: > Thanks for sharing this information! Looking forward to the event :D > > Best, > tison. > > > Nozomi Kurihara 于2023年6月2日周五 11:04写道： > >> Dear Pulsar Enthusiasts, >> >> We are thrilled to announce the upcoming A

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

> > destination. > > --- > > > > OTel supports two kinds of exporter: Prometheus (HTTP) and OTLP (push). > > We'll just configure to use them. > > > > > > > > On Mon, May 15, 2023 at 10:35 AM Enrico Olivelli > > wrote: > > > > >

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

+1 (binding) Enrico Il giorno lun 19 giu 2023 alle ore 14:48 Asaf Mesika ha scritto: > > +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 sta

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

Lari, Il giorno mar 20 giu 2023 alle ore 09:33 Lari Hotari ha scritto: > > Dear Pulsar Community Members, > > I would like to initiate a discussion on making the Pulsar Functions > runtime "pluggable". In doing so, we can ensure that the addition of new > runtime types becomes more straightforwar

Re: [DISCUSS] Apache Pulsar 2.11.2 release

Jiwei, Il giorno lun 26 giu 2023 alle ore 08:09 guo jiwei ha scritto: > > Hello, community: >It has been more than 2 months since the release of 2.11.1. During this > period, we have more than 80 fixes. > https://github.com/apache/pulsar/compare/v2.11.1...branch-2.11 >I suggest releasing

Re: [DISCUSS] PIP-279: Reformat property in generateResponseWithEntry

+1 (binding) Enrico Il giorno lun 26 giu 2023 alle ore 07:53 guo jiwei ha scritto: > > +1 (binding) > > This is a bug and we need this fix. > > > > > Regards > Jiwei Guo (Tboy) > > > On Wed, Jun 21, 2023 at 11:23 AM steven lu wrote: > > > # Motivation > > > > reformat property,for a http header

Re: Improving the usability of the bookie Isolation feature

Il giorno lun 26 giu 2023 alle ore 09:21 Yubiao Feng ha scritto: > > Hi Yan,Asaf > > > 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. > > I agree with Asaf +1 Enrico > > T

Re: [DISCUSS] About cherry-picking `Use Ubuntu 22.04 for Pulsar images (#20475)`

My understanding is that Ubuntu 20 is EOL. I agree that we should cherry-pick that change (without upgrading the Python client) to 2.10, 2.11 and also to 3.0 Enrico Il giorno lun 26 giu 2023 alle ore 11:10 guo jiwei ha scritto: > > Hello community: >For this patch Use Ubuntu 22.04 for Pulsa

Re: [DISCUSS] Apache Pulsar 2.10.5 release

Xiangying, Il giorno lun 26 giu 2023 alle ore 11:47 Xiangying Meng ha scritto: > > Hello, community: >It has been more than 2 months since the release of 2.10.4. During this > period, we have 64 fixes. > https://github.com/apache/pulsar/compare/v2.10.4...branch-2.10 >I suggest releasing

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

Yes we can. It was a tentative goal of creating a new workflow to build releases, especially for the pulsar-all docker image, that depends both on pulsar main repo code and on Pulsar SQL, that we wanted to remove from the base repository. Enrico Il giorno mar 27 giu 2023 alle ore 08:27 Asaf Mesi

Re: Pulsar doesn't support cgroup v2 which became the default in Kubernetes v1.25+ (AKS v1.25, GKE v1.26, EKS v1.26)

Il giorno mar 27 giu 2023 alle ore 12:58 Lari Hotari ha scritto: > > I take my words back about branch-2.9 . It's also using Java 11 at runtime, > so it should be possible to apply https://github.com/apache/pulsar/pull/20659 > to branch-2.9 too so that we get cgroup v2 support for Pulsar 2.9.x.

Re: [VOTE] PIP-279: Reformat property in generateResponseWithEntry

+1 binding Thank you Enrico Il giorno mer 28 giu 2023 alle ore 08:57 Haiting Jiang ha scritto: > > +1 binding > > Thanks, > Haiting > > On Wed, Jun 28, 2023 at 10:17 AM houxiaoyu wrote: > > > > +1 (non-binding) > > > > Xiaoyu Hou > > > > steven lu 于2023年6月28日周三 09:40写道： > > > > > Hi, community

Re: [DISCUSS] Cherry-pick PR-16059 to 2.10 to prevent infinite unloading

+1 Enrico Il Dom 2 Lug 2023, 06:19 Hang Chen ha scritto: > +1 for cherry-picking it to branch-2.10. We have a flag to control > whether to enable or disable it. > > `removeMostServicingBrokersForNamespace ` is introduced by [1] to > solve the problem that when all bundles in a particular namesp

Re: [DISCUSS] Release Pulsar 3.0.1

Il giorno ven 14 lug 2023 alle ore 13:22 Yunze Xu ha scritto: > > -1 (binding) > > Many public interfaces are modified. I second Yunze -1 (binding) from myself as well Enrico > > https://github.com/apache/pulsar/pull/20666 > org.apache.pulsar.broker.loadbalance.extensions.filter.BrokerFilter#

Re: [DISCUSS] Make the API compatibility guarantee clear

Yunze, I agree overall with the proposal, I added some comments inline below Enrico Il giorno ven 14 lug 2023 alle ore 13:25 Yunze Xu ha scritto: > > Good suggestion. We can try that. > > Thanks, > Yunze > > On Fri, Jul 14, 2023 at 7:03 PM Lari Hotari wrote: > > > > Makes sense. We should use t

Re: [DISCUSS] Apache Pulsar 3.1.0 release

+1 Enrico Il giorno lun 31 lug 2023 alle ore 04:35 guo jiwei ha scritto: > > The next two weeks will be code freeze time, and I will release rc on > August 11 if everything goes well > > Regards > Jiwei Guo (Tboy) > > > On Mon, Jul 31, 2023 at 10:17 AM guo jiwei wrote: > > > I have cut the 3.1

Re: [DISCUSS] Proposal for donating pulsar-admin-go to the Apache Pulsar project

+1 Thanks Enrico Il giorno lun 31 lug 2023 alle ore 17:59 Zixuan Liu ha scritto: > > This is a good idea for the Pulsar community. > > > The first one is hosting code in three repos: pulsar-admin-go, > pulsar-client-go, pulsar-auth-go. Then factor out the shared auth logics > into pulsar-auth-go

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

I support this proposal. I can't understand if this is still a VOTE thread. If it is a VOTE thread then this is my +1 (binding) Sorry for late reply Enrico Il Gio 3 Ago 2023, 21:43 Rajan Dhabalia ha scritto: > Hi Penghui. > > I think I tried to answer most of the questions and have enough use

Re: [RESULT][VOTE] Accept pulsar-admin-go as part of the Apache Pulsar project

+1 (binding) (Late on the train) Enrico Il Gio 10 Ago 2023, 05:39 tison ha scritto: > Hi, > > The vote for "Accept pulsar-admin-go as part of the Apache Pulsar project" > has PASSED and closed now. > > The result is as follows: > > 4 +1 binding Votes > - Yunze Xu > - tison > - mattisonchao > -

Re: [ANNOUNCE] Apache Pulsar 3.1.0 released

Congratulations! Enrico Il Lun 14 Ago 2023, 11:16 guo jiwei ha scritto: > The Apache Pulsar team is proud to announce Apache Pulsar version 3.1.0. > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. It provides simple pub-sub semantics over topics, >

Re: [VOTE] PIP 289: Secure Pulsar Connector Configuration

+1 (binding) Thanks Enrico Il Gio 10 Ago 2023, 18:46 Michael Marshall ha scritto: > +1 (binding) > > - Michael > > On Thu, Aug 10, 2023 at 11:43 AM Michael Marshall > wrote: > > > > Hi Pulsar Community, > > > > This is the vote thread for PIP 289: > > https://github.com/apache/pulsar/pull/2090

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

Tison, Il Mar 15 Ago 2023, 16:56 tison ha scritto: > A demostration for change set - > https://github.com/apache/pulsar/pull/20974 While I think it is great to start with Spotless for little projects or when you start from scratch, appling a patch that changes 3.000+ files will make it very h

Re: [Discuss] Release Pulsar Python Client 3.3.0

+1 Enrico Il Mar 15 Ago 2023, 14:04 Zike Yang ha scritto: > +1 > > BR, > Zike Yang > > On Tue, Aug 15, 2023 at 7:19 PM Baodi Shi wrote: > > > > Hi all, > > > > I would like to propose releasing the Pulsar Python Client 3.3.0. > > > > It has been over 2 months since the last release (3.2.0). Th

Re: [DISCUSS] Expediting Pulsar releases 3.0.7 and 3.3.2 due to critical RCE vulnerability in Avro Java SDK <1.11.4, CVE-2024-47561

Il giorno gio 3 ott 2024 alle ore 22:59 Lari Hotari ha scritto: > Dear Pulsar Community, > > There's a critical 9.3/10 level RCE vulnerability in Avro Java SDK > <1.11.4, CVE-2024-47561. > More details can be found in these resources: > - https://github.com/advisories/GHSA-r7pg-v2c8-mfg3 > - http

Re: [VOTE] PIP-385 Add rate limit semantics to pulsar protocol and Java Client

+1 (binding) Enrico Il giorno mer 13 nov 2024 alle ore 03:37 Apurva Telang < apurvatelan...@gmail.com> ha scritto: > +1 (non-binding) > > On Tue, Nov 12, 2024 at 12:26 AM Zixuan Liu wrote: > > > +1(non-binding) > > > > Thanks, > > Zixuan > > > > Girish Sharma 于2024年11月11日周一 15:02写道： > > > > >

Re: [DISCUSS] PCIP-1 Add the development process for pulsar-java-contrib project

+1 It is clear that maintaining the repository is under the responsibility of the Pulsar PMC and only Pulsar committers are able to commit patches to the repository. Committers must apply the usual diligence in committing the patches, and enforce the usual rules: at least 2 +1s from committers (o

Re: [DISCUSS] PIP-381: Handle large PositionInfo state

Il Sab 21 Set 2024, 01:51 Rajan Dhabalia ha scritto: > Hi Andrey, > > Thanks for submitting the PR as we have been facing this issue for a long > time now and we also have PR which solves this issue in a simple and a > fundamental way with proven perf results as well. > > PR: https://github.com/a

Re: [VOTE] PIP-381: Handle large PositionInfo state

+1 (binding) Enrico Il Lun 23 Set 2024, 19:41 Andrey Yegorov ha scritto: > Hi, > > I'd like to start the voting thread for PIP-381: Handle large PositionInfo > state. > > Proposal PR: https://github.com/apache/pulsar/pull/23328 > Discussion thread: > https://lists.apache.org/thread/8sm0h804v591

Re: [DISCUSS] Revisit PIP voting max time

Il giorno mar 24 set 2024 alle ore 17:31 Dave Fisher ha scritto: > > > > On Sep 23, 2024, at 8:07 PM, Yunze Xu wrote: > > > > I have similar concerns for it. Some PIPs might not get enough > > attention. Generally I agree with the proposal that a PIP should be > > treated as "approved" if > > -

Re: [VOTE] PIP-384: ManagedLedger interface decoupling

+1 (binding) Enrico Il Mer 2 Ott 2024, 03:21 Matteo Merli ha scritto: > +1 > -- > Matteo Merli > > > > On Tue, Oct 1, 2024 at 5:03 PM Rajan Dhabalia > wrote: > > > +1 (binding) > > > > Thanks, > > Rajan > > > > On Tue, Oct 1, 2024 at 9:36 AM Lari Hotari wrote: > > > > > Hi, > > > > > > I'd l

Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering

+1 (binding) Enrico Il Mer 2 Ott 2024, 03:21 Matteo Merli ha scritto: > +1 > -- > Matteo Merli > > > > On Tue, Oct 1, 2024 at 4:53 PM Lari Hotari wrote: > > > Hi, > > > > I'd like to start the voting thread for PIP-379: Key_Shared Draining > > Hashes for Improved Message Ordering > > > > Pro

Re: [DISCUSS] PIP-391: Enable batch index ACK by default

+1 Thanks Enrico Il giorno ven 8 nov 2024 alle ore 12:40 Zike Yang ha scritto: > +1 > > Thanks, > Zike Yang > > On Fri, Nov 8, 2024 at 2:51 PM Zixuan Liu wrote: > > > > +1 > > > > Thanks, > > Zixuan > > > > Yunze Xu 于2024年11月6日周三 20:45写道： > > > > > Hi all, > > > > > > I wrote a PIP (https://

Re: [VOTE] PIP-393: Improve performance of Negative Acknowledgement.

+1 (binding) Enrico Il Gio 28 Nov 2024, 12:22 Lari Hotari ha scritto: > +1 (binding) > > -Lari > > On 2024/11/28 03:27:05 thetumbled wrote: > > Hi, Pulsar Community. > > I would like to start the voting thread for PIP-393: Improve > performance of Negative Acknowledgement. > > Proposal PR:

Re: [VOTE] PCIP-1 Add the development process for pulsar-java-contrib project

+1 (binding) Enrico Il giorno mar 12 nov 2024 alle ore 15:16 Jia Zhai ha scritto: > +1 (binding) > > > > > On Tue, Nov 12, 2024 at 9:11 PM Haiting Jiang > wrote: > > > +1 (binding) > > > > Thanks, > > Haiting > > > > > > On 2024/11/12 12:18:11 xiangying meng wrote: > > > +1(non-binding) > > >

Re: [DISCUSS] PIP-393: Improve performance of Negative Acknowledgement

This is a very nice improvement and well described No comments. I will be +1 on VOTE Enrico Il giorno mar 26 nov 2024 alle ore 05:12 WenZhi Feng ha scritto: > Hello, Pulsar Community. > I add the space complexity analysis of the new data structure in the PIP: > https://github.com/apache/pulsar/

Re: [VOTE] PIP-395: Add Proxy configuration to support configurable response headers for http reverse-proxy

+1 (binding) Enrico Il Lun 10 Feb 2025, 11:11 Lari Hotari ha scritto: > +1 (binding) > > -Lari > > On 2025/02/06 20:59:32 Rajan Dhabalia wrote: > > Hi, > > > > I would like to start voting thread for PIP-395 to add support for > > configurable response headers in http reverse-proxy > > > > PIP

Re: [VOTE] PIP-404： Introduce per-ledger properties

Tao, I think that the proposal is valuable. We have to clarify which datatypes are supported both for the keys and for the values. Are keys and values only raw arrays of bytes? It would be better to have a way to detect the types, so that automatic tools, like CLIs and UIs can represent the value

Re: [VOTE] Release Apache Pulsar 0.5.0

I have imported the KEYS file https://downloads.apache.org/pulsar/KEYS but I cannot validate the release: for i in *asc; do gpg --verify $i; done; gpg: assuming signed data in 'apache-pulsar-manager-0.5.0-bin.tar.gz' gpg: Signature made Wed 15 Jan 2025 04:25:48 PM CET gpg:using

Re: [VOTE] PIP-412: Support setting messagePayloadProcessor in Pulsar Functions and Sinks

+1 (binding) Enrico Il Sab 5 Apr 2025, 06:17 Lari Hotari ha scritto: > +1 (binding) > > -Lari > > On 2025/04/01 09:08:53 Pengcheng Jiang wrote: > > Hi, All. > > > > I would like to start the voting thread for PIP-412: Support setting > > messagePayloadProcessor in Pulsar Functions and Sinks >

Re: [VOTE] Release Apache Pulsar 0.5.0

idation steps as outlined in the link below and > > compiled the binary tarball. The package has been running well on my > > computer, and I was able to log in without any issues: > > > > [Apache Pulsar Manager Release Candidate > > Validation]( > https://github.com/a

Re: [VOTE] Release Apache Pulsar 0.5.0

i 268239360 Jan 12 15:49 pulsar-manager.tar enricoolivelli@enrico-5570:~/dev/release_validation/pulsar-manager-0.5.0/apache-pulsar-manager-0.5.0-bin$ cd dist/ enricoolivelli@enrico-5570:~/dev/release_validation/pulsar-manager-0.5.0/apache-pulsar-manager-0.5.0-bin/dist$ ls -la total 36 drwxr-xr-x 3 en

Re: [DISCUSS] Doubt about the widely used Netty Recycler in Pulsar

Yunze, I support your doubts. Recycling objects is useful only under certain conditions and it adds lot of complexity. It is a tool that we can use but we should do it only when needed. And 'when needed' can only be measured with running workloads that exercise the code paths that you are changing

Re: [DISCUSS] Upcoming Pulsar releases 3.0.10, 3.3.5, 4.0.3 addressing CVE-2025-24970

Il Mer 26 Feb 2025, 22:00 Lari Hotari ha scritto: > The releases continue to be blocked by a lack of binding votes. > > Regarding the semi-automated validation with > https://github.com/lhotari/pulsar-release-validation in a Docker > container, the solution now uses a persistent Docker volume to

Re: [DISCUSS] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats

Very useful +1 Enrico

[jira] [Commented] (PULSAR-12) Expose the broker level message metadata to the client.

[ https://issues.apache.org/jira/browse/PULSAR-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1731#comment-1731 ] Enrico Olivelli commented on PULSAR-12: --- [~libw] can you please subscribe to

<    5   6   7   8   9   10