Re: [VOTE] Pulsar Release 2.9.0 Candidate 2

The non-persistent partitioned topic with geo-replicated enabled is not working in 2.9.0 rc2, I have tested on 2.8.1, it works. But for 2.9.0 when I create a non-persistent partitioned topic, I will get a timeout exception ``` bin/pulsar-admin topics create-partitioned-topic non-persistent://publi

Re: [VOTE] Pulsar Release 2.9.0 Candidate 2

Thanks, I'm working on a fix. -Penghui On Tue, Nov 2, 2021 at 2:21 PM Enrico Olivelli wrote: > Penghui, > Thanks > > > > Il Mar 2 Nov 2021, 04:31 PengHui Li ha scritto: > > > The non-persistent partitioned topic with geo-replicated enabled is not > > wor

Re: [VOTE] Pulsar Release 2.9.0 Candidate 2

works. Another one is related to the partitioned topic creation, Ran Gao is working on this part. Thanks, Penghui On Tue, Nov 2, 2021 at 5:15 PM PengHui Li wrote: > Thanks, I'm working on a fix. > > -Penghui > > On Tue, Nov 2, 2021 at 2:21 PM Enrico Olivelli > wrote:

Re: [Vote] PIP 109: Introduce Bot to Improve Efficiency of Developing Docs

+1 Penghui On Wed, Nov 3, 2021 at 12:33 PM Anonymitaet _ wrote: > Hi Pulsar Community, > > I’m starting a thread to vote on Pulsar Doc Bot (PIP 109). > > The issue for this PIP 109 is here > https://github.com/apache/pulsar/issues/12595. > It documents the design proposal, solution, implementat

Re: [VOTE] Pulsar Client Go Release 0.7.0 Candidate 1

+1 (binding) Validated * Build from source * publish messages and consume messages Thanks, -Penghui On Tue, Nov 2, 2021 at 6:20 PM Oguni Hideaki wrote: > +1 (non-binding) > > - verified checksum and signature > - verified pub/sub > > I used > https://dist.apache.org/repos/dist/dev/pulsar/KE

Re: Size of Asf-site branch in Pulsar repo

+1 -Penghui On Mon, Nov 1, 2021 at 5:53 PM Guangning E wrote: > +1 > > Enrico Olivelli 于2021年10月30日周六 下午6:16写道： > > > Il Ven 29 Ott 2021, 21:27 Dave Fisher ha scritto: > > > > > Hi - > > > > > > > On Oct 29, 2021, at 12:02 PM, Matteo Merli > wrote: > > > > > > > > The Pulsar website is getti

Re: [VOTE] PIP 107: Introduce the chunk message ID

+1 Thanks for the great work. -Penghui On Mon, Nov 1, 2021 at 10:25 AM Zike Yang wrote: > Hi Pulsar Community, > > I would like to start a VOTE for PIP 107: Introduce the chunk message ID. > > The issue for this PIP is here: > https://github.com/apache/pulsar/issues/12402 > > Please VOTE withi

Re: [DISCUSSION] PIP-108: Add method to help user judge if consumer queue has message

rk flow is 1) check if has message > > 2) apply for flow quota 3) receive messages. I can not put the mssage > back > > to the queue, can't use the `receive(0)`. > > And `apply for flow quota` is a costly action. > > And discussed with PengHui Li a

[DISCUSS] Consumer not able to connect to topic that have active producer with AUTO_PRODUCE_BYTES schema

Dear all, PIP-43 https://github.com/apache/pulsar/wiki/PIP-43%3A-producer-send-message-with-different-schema introduced AUTO_PRODUCE_BYTES schema which allows the producer creates the schema while publishing messages. But there is a case that the producer with AUTO_PRODUCE_BYTES schema connects t

Re: [DISCUSS] Consumer not able to connect to topic that have active producer with AUTO_PRODUCE_BYTES schema

51", "local":"/127.0.0.1:52482"}` ``` Thanks, Penghui On Wed, Nov 10, 2021 at 7:20 PM Enrico Olivelli wrote: > Penghui, > > Il giorno mer 10 nov 2021 alle ore 11:36 PengHui Li > ha > scritto: > > > Dear all, > > > > PI

Re: [DISCUSS] Add remove-clusters command for namespace in pulsar-admin

+1, Penghui On Nov 16, 2021, 9:27 AM +0800, Ruguo Yu , wrote: > Hi Community, > > The tool ` pulsar-admin` supports `set-clusters` and `get-clusters` command > so that we can `set` / `get` replication clusters for a namespace. But it > lacks corresponding `remove-clusters` command to restore to

[ANNOUNCE] New Committer: Jiwei Guo

months, and he is a PMC member of Apache dolphinscheduler https://dolphinscheduler.apache.org/en-us/community/team.html Welcome and Congratulations, Jiwei! Please join us in congratulating and welcoming Jiwei onboard! Best Regards, Penghui Li on behalf of the Pulsar PMC

Re: Stop cherry-picking patches to released branch

Hi Enrico, I think we should cherry-pick the bug fixes, enhancements and test improvements? Only the new features and document should not cherry-pick release branch. And, do you see any issues introduced in release branch from the cherry-picking? Thanks, Penghui On Nov 22, 2021, 5:38 PM +0800, E

RE: [DISCUSS] The processing of residual scheam and the convergence of schema operation auth

+1 Penghui On Nov 19, 2021, 2:29 AM +0800, Neng Lu , wrote: > +1 for dropping the schema when a topic is deleted by default. > > I previously met a strange error that after creating a topic with the same > name as previous deleted topic, the "ghost" schema is associated with the new > topic agai

Re: [VOTE] Apache Pulsar 2.9.0 candidate 4

+1 (binding) Follow the "Release Candidate Validation": - start standalone - create tenants and namespaces - publish and consume messages - cassandra connector - function and stateful function Done the performance test, no performance degradation. Best regards Penghui On Mon, Nov 22, 2021 at

RE: [Discuss] Apache pulsar-manager 0.3.0 release

+1 Penghui On Dec 1, 2021, 11:56 AM +0800, Ruguo Yu , wrote: > +1 > > Ruguo Yu > > On 2021/11/25 05:59:45 Guangning E wrote: > > > Hello everyone: > > > > > > It has been a long time since the release of the previous version's major > > > release (0.2.0). I am planning to start the 0.3.0 release s

Re: New committer: Michael Marshal

Congrats Micheal! Penghui On Fri, Dec 3, 2021 at 3:32 PM Enrico Olivelli wrote: > The Project Management Committee (PMC) for Apache Pulsar > has invited Michael Marshal to become a committer and we are pleased to > announce that he has accepted. > > Michael contributed a lot of interesting add

Re: Welcome Dave Duggins to Pulsar community!

Welcome, Dave. Regards, Penghui On Sat, Dec 4, 2021 at 8:36 PM Dianjin Wang wrote: > Welcome, Dave! > > Best, > Dianjin Wang > > > On Fri, Dec 3, 2021 at 7:55 PM Anonymitaet _ > wrote: > > > Hi Pulsarerers, > > > > > > > > Today is a great plus one news day. Our community is growing since Dave

Re: [ANNOUCEMENT] Welcome to our newest PMC Member - Yu Liu!

Welcome yu. Penghui On Tue, Dec 7, 2021 at 10:23 AM Yu wrote: > Thank you for recognizing my efforts in making Pulsar better and believing > I was ready to take more responsibilities. > > I’m grateful for all of the amazing people in the Pulsar community and > thanks for your great support. > >

Re: [Vote] PIP 104: Add new consumer type: TableView

+1 Penghui On Tue, Dec 7, 2021 at 12:57 PM Guangning E wrote: > +1 > > Jerry Peng 于2021年12月7日周二 05:17写道： > > > +1 > > > > On Mon, Dec 6, 2021 at 1:01 PM Enrico Olivelli > > wrote: > > > > > +1 (binding) > > > > > > > > > Enrico > > > > > > Il Lun 6 Dic 2021, 19:27 Matteo Merli ha scritto: >

Re: [PIP] Broker extensions to provide operators of enterprise-wide clusters better control and flexibility

+1 on this proposal. For the details, I think we should consider avoiding the breaking change for the existing broker interceptor(make sure the old interceptor can still work), Penghui On Wed, Dec 8, 2021 at 12:56 PM Sijie Guo wrote: > Agree with Matteo. > > +1 on this proposal. > > On Tue, De

Re: [Vote] PIP 106: Pulsar Broker extensions for operators of enterprise-wide clusters

+1 Penghui Narayanan, Madhavan 于2021年12月9日 周四22:27写道： > Hi Pulsar Community, > > > > I would like to start a VOTE on the Pulsar Broker extensions for operators > (PIP 106). > > > > The issue for PIP 106 is here: > https://github.com/apache/pulsar/issues/12858 > > And the prototype implementatio

Re: [VOTE] Pulsar Release 2.2.0 Candidate 1

https://github.com/apache/pulsar//2759 please include this PR. Joe F 于2018年10月11日 周四08:16写道： > This is the first release candidate for Apache Pulsar, version 2.2.0 > > It adds new features and also fixes for various issues from 2.1.1 > > * Pulsar Java Client Interceptors > * Integration of fun

Re: [CANCEL] [VOTE] Pulsar Release 2.2.0 Candidate 1

> I think 2759 is merged after Joe started the release process. We can > consider adding it to 2.2.1 @Sijie:Ok, Thanks. Joe F 于2018年10月12日周五 上午6:56写道： > Given the issue identified, this vote is cancelled until > https://github.com/apache/pulsar/issues/2778 is fixed > > Candidate-2 up will be pu

Re: [CANCEL] [VOTE] Pulsar Release 2.2.0 Candidate 1

> FYI. the issue that Matteo mentioned here is related to the issue you reported yesterday when using 2.2.0-SNAPSHOT artifact. Yes, problem is when i use `java -cp` to run the application. but when i debug by idea, we can’t get the problem. Joe F 于2018年10月12日周五 上午6:56写道： > Given the issue ident

Re: [DISCUSSION] Delayed message delivery

If consumer control the delayed message specific execution time we must trust clock of consumer, this can cause delayed message process ahead of time, some applications cannot tolerate this condition. > My concern of this category of approaches is "bandwidth" usage. It is > basically trading bandw

Re: [DISCUSSION] Delayed message delivery

> So rather than specifying the absolute timestamp that the message > should appear to the user, the dispatcher can specify the relative > delay after dispatch that it should appear to the user. As matteo said the worst case would be that the applied delay to be higher for some of the messages, if

Re: [DISCUSSION] Delayed message delivery

don't think is complex I believe > there > > > > > are others serious advantages: > > > > > > > > > > 1. Simplicity at client side, we don't need to add any code which > is > > > > > less error prone. > > >

Re: Release Manager for 2.3.1 and 2.4.0

I volunteer to help releasing 2.4.0 On 2019/03/06 09:55:59, Sijie Guo wrote: > Hi all committers,> > > There are a few important bug fixes for 2.3.0. It might be worth cutting a> > 2.3.1 release in a week or so.> > > 2.4.0 is also in the pipeline to push forward.> > > Any committers are i

Re: [DISCUSS] PIP 34: Add new subscribe type -- Key_Failover

Hi jia, Is it better by a separate attribute to indicate the order? If i am not mistaken the compaction topic is depends on the message key, does this mean that it is not easy for users to use both of these features at the same time? Jia Zhai 于2019年4月3日 周三17:09写道： > Hi all, > > I would like

Re: [DISCUSS] PIP 34: Add new subscribe type -- Key_Failover

@Sijie Guo Sorry, I may not have described my point in the previous email. I try to describe it again. :) User can use key to achieve business logic(e.g. use user_id as message key) At the same time, want to use another identifier as the basis for the order. As the message key has many uses, av

Release 2.4.0 - Feature Freeze

Hi all, There are already a lot of great features in 2.4.0. It is time to release 2.4.0 now. I am calling a feature freeze for 2.4.0. We are not going to accept any new features from now. People still have time to complete the ongoing features and any bug fixes. The code change will be freeze in

Re: Release 2.4.0 - Feature Freeze

; > > So that he can have a better estimation on when to cut the > > 2.4.0 > > > > > > release. > > > > > > > > “Feature Freeze” is probably not the right word here, but it > > is a > > > > > > common > > > > > > > > c

Re: Pulsar 2.3.2 Release Discussion

+1 Shivji Kumar Jha 于2019年5月20日周一 下午12:12写道： > HI Jerry, > > Can we include this in 2.3.2 please? > https://github.com/apache/pulsar/pull/4136 > > This is critical because prometheus output is not parsed by some monitoring > tools (telegraf for instance). > > Regards, > Shivji Kumar Jha > http:/

Re: [DISCUSS] PIP 34: Add new subscribe type -- Key_Failover

>> >> >> Jia Zhai >> >> Beijing, China >> >> Mobile: +86 15810491983 >> >> >> >> >> On Fri, Apr 5, 2019 at 1:04 AM Sijie Guo wrote: >> >> > Penguin, >> > >> > Thank you for your clarification!

Pulsar 2.4.0 Release Discussion

Hi all I am planning to start the 2.4.0 release soon (probably next week). I would like to check the current status for the in-progress features, to see what need to be merged and included in 2.4.0. Here is the list of items still in progress. Can the owner confirm if we should include them in 2.4

Re: Pulsar 2.4.0 Release Discussion

Sijie Guo > > 送信日時: 2019年6月11日 13:18 > > 宛先: Dev > > 件名: Re: Pulsar 2.4.0 Release Discussion > > > > Penghui, > > > > I tried to ping those issues to see if they can be moved to 2.5.0. Please > > check those issues. > > > > Also since w

[VOTE] Pulsar Release 2.4.0 Candidate 1

This is the first release candidate for Apache Pulsar, version 2.4.0. It fixes the following issues: https://github.com/apache/pulsar/milestone/20?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 sour

Re: Was [VOTE] Pulsar Release 2.4.0 Candidate 1

n > > Thank you > > Enrico > > > -- Forwarded message - > Da: PengHui Li > Date: dom 23 giu 2019, 07:16 > Subject: [VOTE] Pulsar Release 2.4.0 Candidate 1 > To: Dev > > > This is the first release candidate for Apache Pulsar, version 2.4.0

Re: Was [VOTE] Pulsar Release 2.4.0 Candidate 1

Hi Enrico, I have added the 2.4.0 release notes pull request, please help review. https://github.com/apache/pulsar/pull/4590 -PengHui PengHui Li 于2019年6月24日周一 下午4:42写道： > Hi Enrico, > > I am working on the release notes. Will send a pull request soon. > > -Penghui > > En

Re: [VOTE] Pulsar Release 2.4.0 Candidate 1

; 2. Create tenant and namespace > 3. Create function > 4. Publish and consume message > 5. Stateful Functions > > > Best regard! > > Yong > > > On Sun, 23 Jun 2019 at 13:16, PengHui Li wrote: > > > This is the first release candidate for Apache Pulsar, vers

[VOTE] Pulsar Release 2.4.0 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.4.0. It fixes the following issues: https://github.com/apache/pulsar/milestone/20?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

[RESULT] [VOTE] Pulsar Release 2.4.0 Candidate 2

The vote is now closed for Pulsar Release 2.4.0 Release Candidate 2 with 11 +1 (4 +1 binding votes) votes, 0 +0/-0 votes, 0 -1 votes. 4 +1 bindings are: Jerry Peng Jia Zhai Rajan Dhabalia Sijie Guo 7 +1 non-bindings are: Eren Avsarogullari Fangbin Sun Guangning E Penghui Li Xiaolong

PIP 38: Batch Receiving Messages

Dear all This is a PIP to add feature of batch receiving messages https://github.com/apache/pulsar/wiki/PIP-38%3A-Batch-Receiving-Messages Please take a look. — Regards, Penghui Li

[ANNOUNCE] Apache Pulsar 2.4.0 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.4.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

Re: PIP 38: Batch Receiving Messages

nt API only allows the user to retrieve a > message one at a time. > > Best, > > Jerry > > On Wed, Jul 3, 2019 at 11:18 PM PengHui Li > wrote: > > > > Dear all > > > > This is a PIP to add feature of batch receiving messages > > >

Re: [VOTE] Pulsar Release 2.4.1 Candidate 1

+1 (non-binding) - check signatures/checksums - compile the source - standalone/producer/consumer worked - stateful function worked - cassandra-connector worked - can build go client using rpm/deb packages Thank you for driving the release. Regards, Penghui Nozomi Kurihara 于2019年8月30日周五 下午5:53

Re: [DISCUSS] PIP: Producer Send Message with Different Schema

👍 Looks good to me +1. Sijie Guo 于2019年9月3日周二 下午2:12写道： > Thank you Yi. > > I have copied your gist to PIP-43 > > https://github.com/apache/pulsar/wiki/PIP-43%3A-producer-send-message-with-different-schema > . > > Thanks, > Sijie > > On Mon, Sep 2, 2019 at 10:35 PM 唐谊 wrote: > > > Here are som

Re: [VOTE] Accept pulsar-manager as part of Apache Pulsar project

+1 Guangning E 于2019年9月4日周三 上午10:32写道： > +1 > > > Yijie Shen 于2019年9月4日周三 上午9:14写道： > > > +1 > > > > Thanks for the great UI! > > > > Best, > > Yijie > > > > On Wed, Sep 4, 2019 at 8:07 AM Nozomi Kurihara > > wrote: > > > > > > +1 > > > > > > Thank you for your great works! > > > > > > Regards

[DISCUSS] PIP-44: Separate schema compatibility checker for producer and consumer

Hi all; Bo Cong and i are drafting a proposal to separate schema compatibility checker for producer and consumer Here is the link of PIP-44 Looking forward feedbacks. Thanks, Penghu

Re: [DISCUSS] PIP-44: Separate schema compatibility checker for producer and consumer

eed that the compatibility > check > > strategy is different between producers and consumers. > > We should separate them and make it more clearly. The proposal overall > > looks good. +1 > > > > Thank you and your team for driving this! > > > > -Sijie

Re: [ANNOUNCE] Penghui Li joins the Apache Pulsar PMC.

pleased to announce that Penghui > > Li has already accepted our invitation to become a PMC member on the > > Apache Pulsar project. > > > > Penghui has been actively contributing to Apache Pulsar for a long time. > > Penghui has contributed large features like Interc

Re: [ANNOUNCE] Guangning E becomes a Pulsar committer

Congratulations to Guangning 👍 yp 于2019年10月10日 周四20:21写道： > Congrats Guangning ! > > > - lan.liang > On 10/10/2019 18:41，xiaolong ran > wrote： > > Congratulations to Guangning! > 🥰 > > Best Regards, > Xiaolong.ran > >

Re: [Community Weekly Update] 2019-10-07 ~ 2019-10-18

👍 anonymitaet _ 于2019年10月19日 周六13:36写道： > Dear Pulsar enthusiast, > > This is the first weekly community update, which helps you quickly capture > Pulsar's highlights and spot trends over last week, meanwhile strengthen > the communication and connection within the Pulsar family. > >

Re: [VOTE] PIP-47: Time Based Release Plan

+1 binding Guangning E 于2019年11月7日周四 上午10:54写道： > +1 non binding > > Thanks, > Guangning > > Yuva raj 于2019年11月6日周三 下午6:37写道： > > > +1 non binding > > > > On Wed, 6 Nov 2019 at 11:18, xiaolong ran > > wrote: > > > > > > Hi everyone > > > > > > Please review and vote on the PIP-47 propose, > >

Re: [REVOTE] PIP-47: Time Based Release Plan

+1 (binding) -Penghui Sijie Guo 于2019年11月12日周二 下午2:37写道： > +1 (binding) > > - Sijie > > On Mon, Nov 11, 2019 at 10:16 AM xiaolong ran > wrote: > > > Hello everyone: > > > > Please review and vote on the PIP-47 propose: > > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan

Re: [VOTE] Pulsar Manager release 0.1.0 Candidate 4

+1 (binding) - checksum and signature - environment, tenant, namespace, topic are works well. Yong Zhang 于2019年11月22日周五 下午1:14写道： > +1 (non-binding) > > - check signatures and checksum > - validate show tenant and namespace and topic I created > > > > Regards, > > Yong > > On Tue, 19 Nov 2019 a

Re: [VOTE] Pulsar Release 2.4.2 Candidate 2

+1 (binding) - validate checksums of the binary, source code and connector tarball. - validate the pub and sub - validate the state function - validate the connector - validate the auto create topic is non-partitioned topic - validate list non-persistent topics (only shows the non persistent topic

Re: [VOTE] Pulsar Release 2.4.2 Candidate 3

x27; and client > > produce/consume runs well. > > > > - bin package, 'bin/pulsar standalone' and client produce/consume runs > > well. > > > > > > On Fri, Nov 29, 2019 at 3:49 PM xiaolong ran > > wrote: > > > > > Thanks Yo

[ANNOUNCE] new committer: Yu Liu

conferences to promote community growth. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Congratulations Yu Liu! - Penghui Li (on behalf of the Pulsar PMC)

Re: [ANNOUNCE] Apache Pulsar 2.4.2 released

Congrats! Considering you have gained a lot of experience by release 2.4.2, expect you to share these experiences to us, you can update the release process documentation or share a blog about the 2.4.2 release. This may be of great help to release managers. Thanks, Penghui Guangning E 于2019年12月

Re: [VOTE] PIP-290 Support WSS E2E encryption and not need to expose the private key to the WebSocket Proxy

+1(binding) - The motivation looks good to me. The proposal will provide a real e2e encryption solution for the WebSocket proxy - The solution looks good to me. It will not introduce break changes and will use public APIs as much as possible. And it will not introduce any extra configuration. The

Re: [DISCUSS] New label type: category/*

update the label strategy page simultaneously - > > https://pulsar.apache.org/contribute/develop-labels/ > > > > Best, > > tison. > > > > > > PengHui Li 于2023年8月21日周一 23:41写道： > > > > > I will add the labels, and if there are any objections, I wil

Re: [DISCUSS] PIP-281: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager

ohn wrote: > Hi Penghui, > > I added one comment below. > > On Mon, Aug 21, 2023 at 6:12 AM PengHui Li wrote: > > > > However, with this optional field approach, we don't need to introduce > a > > new protocol version, which could be arguably beneficial. &g

Re: [DISCUSS] PIP-281: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager

system topic > with its state info. > Upon receiving the Owned state via ownership transfer or recovery commands, > the source broker will close the topics in the bundle(disconnect clients), > if any. > > > > On Mon, Aug 21, 2023 at 10:25 PM PengHui Li wrote: > >

Re: [VOTE] PIP 296: Introduce the `getLastMessageIds` API to Reader

+1 (binding) Thanks, Penghui On Fri, Aug 25, 2023 at 8:09 PM Yubiao Feng wrote: > +1 (non-binding) > > Thanks > Yubiao Feng > > On Fri, Aug 25, 2023 at 2:53 PM Xiangying Meng > wrote: > > > Hi Pulsar Community, > > > > This is the vote thread for PIP 296: > > https://github.com/apache/pulsar/p

Re: [VOTE] Pulsar Client Python Release 3.3.0 Candidate 1

OS: macOS Ventura Version 13.4.1 (c) (22F770820d) Python: 3.11.4 +1 (binding) - Checked the signature - Build wheel from source - Run examples Regards, Penghui On Mon, Aug 21, 2023 at 10:24 PM Yunze Xu wrote: > +1 (binding) > > - Verified signature and checksums > - Build the wheel from sour

Re: [DISCUSS] Release DotPulsar 3.0.0

+1 Thanks for driving the release. Penghui On Fri, Aug 25, 2023 at 9:48 PM David Jensen wrote: > Dear Apache PMC and Committers > > Me and Daniel Blankensteiner (blankensteiner) would like to announce we are > soon ready to release DotPulsar 3.0.0. > > The release contains breaking changes, th

Re: [DISCUSS] PIP-286: Add findNewestPosition method in the TopicCompactionService API

Hi Cong, Thanks for driving the proposal. Is it better to use `readNewestCompactedEntry(@Nonnull Predicate condition)` So that you don't need to introduce a new interface, RawEntryMetadata And it's a more general solution for the TopicCompactionService. WDYT? Regards, Penghui On Tue, Jul 25, 2

Re: [DISCUSS]PIP-295: Fixing Chunk Message Duplication Issue

Hi Xiangying, Thanks for driving the proposal. >From my understanding. The message deduplication should only check the last chunk of the message. It doesn't need to care about whether each chunk is duplicated. The client side should handle issues like duplicated chunks. For the example that you h

Re: [VOTE] PIP-297: Support terminating Function & Connector with the fatal exception

+1 (binding) Thanks, Penghui On Tue, Sep 5, 2023 at 8:40 AM Baodi Shi wrote: > +1(non-binding) > > > Thanks, > Baodi Shi > > > On Sep 5, 2023 at 05:23:38, Enrico Olivelli wrote: > > > +1 (binding) > > > > Enrico > > > > Il giorno lun 4 set 2023 alle ore 12:32 Zike Yang ha > > scritto: > > > >

Re: [Discuss] Release RPM packages with cxx11 ABI

+1 And if we can have a README file under the cpp client distribution directory. It should be great. Users can find the explanation of what legacy means. Regards, Penghui On Mon, Sep 4, 2023 at 7:54 PM Yunze Xu wrote: > Hi all, > > Currently the official released pre-built binaries for Linux i

Re: [DISCUSS] PIP-299: A limitation for the max size of cursor metadata to persist

Hi Yubiao, Thank you for spearheading the proposal. I believe it would bring about a substantial enhancement in user experience. Additionally, we should contemplate adopting the new approach as the default behavior of Pulsar. The existing configuration has the potential to result in extensive red

Re: [DISCUSS] Cherry-pick #18518 into branch-2.10 and branch-2.11

+1 Thanks, Penghui On Fri, Sep 1, 2023 at 3:04 AM Yubiao Feng wrote: > Cherry-picked. > > Since the method `isPartitionedTopicBeingDeletedAsync` only exists in > `branch-3.0`, the change > > https://github.com/apache/pulsar/pull/18518/files#diff-38fac527320b93f0e9ea2459420f56638299627f7f29c0148

Re: [DISCUSS] Replace Customized Map with ConcurrentHashMap

I also support the idea. For the execution. I think we can have a branch to apply the changes and then we can built a distribution for the benchmark. After we get the result, then we can decide if it's fine to go to the new solution. The change should also be applied to bookkeeper. And I can help

Re: [DISCUSS] Replace Customized Map with ConcurrentHashMap

but I > think other contributors would love it If we can get some comparison of two > different data structure. > > Best, > Mattison > On 6 Sep 2023 at 22:00 +0800, PengHui Li , wrote: > > I also support the idea. > > > > For the execution. I think we can have a bra

Re: [VOTE] PIP-277: Add `current` option in the Clusters list cmd

+1 (binding) The proposal just added a new option to show which cluster is the current cluster accessed. It will not break any existing behavior. Regards, Penghui On Wed, Sep 6, 2023 at 4:21 PM guo jiwei wrote: > Hi dev, >This thread is to start a vote for PIP-277: Add `current` option in

Re: [DISCUSS] PIP-296: Support storing broker internal client certificates in metadata store

Great discussion. I support making it pluggable for now, while I previously held the belief that storing within metadata was feasible. Regardless of the storage location, users always require a means to upload the cert files. This can be accomplished either by directly using the pulsar-admin CLI

Re: [VOTE] PIP-286: Make the TopicCompactionService to support find entry based on publishTime or index

+1 (binding) Thanks, Penghui On Thu, Sep 14, 2023 at 11:23 AM Cong Zhao wrote: > Hi, all > > Since there are no other concerns in the discussion, I'm delighted to > start the voting process for the PIP-286. > > Here is the link to the PIP: https://github.com/apache/pulsar/pull/20867 > > Thanks,

Re: [VOTE] PIP-301: Introduce LoadBalanceResources to unify the load-date CRUD

+1 (binding) Thanks, Penghui On Tue, Sep 19, 2023 at 8:31 PM guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Mon, Sep 18, 2023 at 8:57 PM houxiaoyu wrote: > > > Hi dev, > >This thread is to start a vote for PIP-301: Introduce > > LoadBalanceResources to unify the

Re: [Vote] PIP-281: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager

There are a lot of discussions that happened in the DISCUSS thread. The proposal looks good to me. +1 (binding) Regards, Penghui On Wed, Sep 6, 2023 at 1:51 PM Heesung Sohn wrote: > Yes, this was my last comment in the PIP. > https://github.com/apache/pulsar/pull/20748#discussion_r1300733232 >

Re: [DISCUSS] Release Pulsar 3.1.1

+1 Thanks, Penghui On Mon, Sep 18, 2023 at 1:32 PM guo jiwei wrote: > Hi all, > > I would like to propose releasing the Pulsar 3.1.1. > > It's over one month since the release of 3.1.0 and there are 56 new commits > in branch-3.1: > https://github.com/apache/pulsar/compare/v3.1.0...branch-3.1 >

Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView

+1 Thanks, Penghui On Wed, Sep 27, 2023 at 3:09 PM Zike Yang wrote: > +1 > > BR, > Zike Yang > > On Wed, Sep 27, 2023 at 3:05 PM Xiangying Meng > wrote: > > > > Hi dev, > >This thread is to start a vote for PIP-302 Add new API > > refreshAsync for TableView. > > Discuss thread: > https://l

Re: [VOTE] PIP-299: Stop dispatch messages if the individual acks will be lost in the persistent storage

+1 (binding) Left to minor comments on the proposal, PTAL. Thanks, Penghui On Thu, Sep 21, 2023 at 2:53 PM Yubiao Feng wrote: > Sorry. The last email was sent by mistake. Just correct it by this one. > > I'd like to start a vote thread for the PIP-299. > https://github.com/apache/pulsar/pull/

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

+1 (binding) Regards, Penghui On Thu, Oct 19, 2023 at 10:45 AM guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Thu, Oct 19, 2023 at 10:11 AM Zili Chen wrote: > > > +1 binding > > > > On 2023/10/17 07:23:29 Diego Salvi wrote: > > > Hi Community, > > > > > > This thread

Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks, Penghui On Mon, Oct 16, 2023 at 9:13 PM Baodi Shi wrote: > Hi all > > I would like to propose releasing the Pulsar 2.11.3 > > It's over one month since the release of 2.11.3, and there are 87 new > commits. > > in branch-2.11: > https://github.com/apache/pulsar/compare/v2.11.2...bran

Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket

+1 (binding) It's a straightforward change for WebSocket Proxy to catch up on features. Thanks, Penghui On Fri, Oct 20, 2023 at 12:55 PM Yunze Xu wrote: > +1 (binding) > > Thanks, > Yunze > > On Fri, Oct 20, 2023 at 10:59 AM mattison chao > wrote: > > > > +1(binding) > > > > Best, > > Mattiso

Re: [VOTE] PIP-304: Make PublishContext provide the message metadata

Hi, kecona, I have left some comments on the GitHub PR. Thanks, Penghui On Fri, Oct 20, 2023 at 9:44 AM kecona wrote: > Hi all, > > This thread is to start a vote for PIP-304. > > PIP: https://github.com/apache/pulsar/pull/21311 > Discussion thread: > https://lists.apache.org/thread/72szlzc0rw

Re: [VOTE] PIP-298 Consumer supports specifying consumption isolation level

+1 (binding) Regards, Penghui On Mon, Oct 23, 2023 at 10:37 AM hzh0425 wrote: > Dave previously mentioned in the discussion thread that he will continue > to support this pip if the documentation is supplemented and improved. Due > to inability to contact him, we apply to cancel his -1 binding.

Re: [Discuss] Release Pulsar C++ Client 3.4.0

Thanks for driving the release, +1 Penghui On Mon, Oct 23, 2023 at 11:00 AM Yunze Xu wrote: > I would like to propose releasing the Pulsar C++ Client 3.4.0. It has > been about 3 months since the last release. There have been many new > features and bug fixes since then. > > Besides, from my o

Re: [VOTE] Pulsar Release 3.1.1 Candidate 1

+1 (binding) - Checked the signatures - Built from source tarball - Run standalone and check the produce, consume - Verified Cassandra connector - Verified stateful function Regards, Penghui On Tue, Oct 24, 2023 at 12:34 PM Yunze Xu wrote: > +1 (binding) > > - Verified checksum and signatures

Re: [VOTE] Pulsar Client Go Release 0.11.1 Candidate 1

+1 (binding) - Verified the signatures - Build from the source - Run the test on Pulsar 3.1.1 (make test PULSAR_VERSION=3.1.1) - Run the test on Pulsar 3.0.1 (make test PULSAR_VERSION=3.0.1) Regards, Penghui On Fri, Oct 20, 2023 at 4:46 PM Yunze Xu wrote: > +1 (binding) > > - Verified checksum

Re: [DISCUSS] PIP-313 Support force unsubscribe using consumer api

Hi Rajan, The proposal looks good to me. The context and the goal are clear. I have 2 comments here 1. The change will not only affect the shared subscription, but it will also affect the Failover and Key_Shared subscriptions. 2. We should also mention the behavior of other consumers when one co

Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2

Hi Yunze, I got an error when running the pulsar-tests (I tried multiple times, same error) ``` 2023-11-08 22:56:43.676 INFO [0x16db63000] ProducerImpl:216 | [persistent://public/default/testPartitionedConsumerUnexpectedAckTimeout1699455403-partition-1, ] Created producer on broker [[::1]:58479

Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2

gt; These tests seem flaky so I reran them individually by: > > ``` > ./tests/pulsar-tests --gtest_filter='CustomLoggerTest.*' > ./tests/pulsar-tests --gtest_filter='*testMultiAddresses' > ``` > > `LookupServiceTest.testMultiAddresses` still failed. I will t

Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2

+1 (binding) - Checked the signature - Build from source and run the tests Regards, Penghui On Thu, Nov 9, 2023 at 5:15 PM Yunze Xu wrote: > +1 (binding) > > - Verified checksum and signatures > - Built from source and run unit tests against the test standalone on > macOS Ventura 13.4 and Appl

Re: [ANNOUNCE] Yubiao Feng as new PMC member in Apache Pulsar

Congrats! Yubiao. - Penghui On Mon, Nov 13, 2023 at 3:36 PM mattison chao wrote: > Dear Community, > > We are thrilled to announce that Yubiao Feng > https://github.com/poorbarcode has been invited and has accepted the role > of a member of the Apache Pulsar Project Management Committee (PMC).

Re: [VOTE] PIP-318: Don't retain null-key messages during topic compaction

+1 (binding) Regards, Penghui On Mon, Nov 13, 2023 at 3:42 PM Yunze Xu wrote: > +1 (binding) > > Thanks, > Yunze > > On Mon, Nov 13, 2023 at 3:28 PM mattison chao > wrote: > > > > +1(binding) > > > > Best, > > Mattison > > > > > On Nov 10, 2023, at 12:12, Cong Zhao wrote: > > > > > > Hi Commu

Re: [DISCUSS] Introducing Apache Pulsar Office Hour Meetings

Hi Mattison, It's better to share the information on the Pulsar Slack channel and user mailing list since the meeting is focused on users. Thanks, Penghui On Mon, Nov 20, 2023 at 11:18 PM Asaf Mesika wrote: > I think it's a wonderful idea. > > Since community engagement in the community meetin

Re: [VOTE] Pulsar Client C++ Release 3.4.1 Candidate 2

+1 (binding) - Checked the signature - Verified the MacOS arm64 pre-build binaries for produce and consume Thanks, Penghui On Wed, Nov 22, 2023 at 10:32 AM Baodi Shi wrote: > +1(non-binding) > > > >- Checked the signature >- Verify for MacOS arm64 pre-built binaries and run producer an

<    1   2   3   4   5   6   7   8   9   10   >