Re: Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas

+1 (binding) Thanks, Zixuan yubiao 于2025年7月18日周五 17:46写道： > Hi Zixuan > > > Regarding the first argument: attempts to bypass schema checks, you left > the following comment > > > > -1, I don't suggest we ignore the replicator check. Once the schema is > incompatible, we should disconnect the re

Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas

-1 This pip attempts to bypass schema checks and also performs unnecessary policy checks. I left my comments, please check. Thanks, Zixuan Yubiao Feng 于2025年7月10日周四 11:02写道： > Hi all > > I want to start a vote on PIP-433: Optimize the conflicts of the > replication and automatic creation mech

Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli

+1 (binding) Thanks, Zixuan guo jiwei 于2025年7月18日周五 13:54写道： > Hi all, > I'd like to start the vote for PIP-435: Add startTimestamp and > endTimestamp for consuming messages in client cli > > - Discussion thread: >https://lists.apache.org/thread/4xl3goqozrq6bogm0rysytcmfxqbsnwl

Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext

+1 binding Thanks, Zixuan PengHui Li 于2025年7月10日周四 22:45写道： > Hi Team, > > This is the official VOTE thread for PIP-432. > - Discuss thread: > https://lists.apache.org/thread/sfcc902hwlgwg21ttwkrsyx3ogt8hzon > - Proposal link: > > https://github.com/apache/pulsar/blob/b212cb3ea93c98f179e19e6aef

Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service

+1 binding ran leon 于2025年7月7日 周一10:52写道： > [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with > third-party schema registry service > Hi Team, > > This is the official VOTE thread for PIP-420. > - Proposal link: https://github.com/apache/pulsar/pull/24328 > > The vote will stay

Re: [ANNOUNCE] New Committer: Mingze Han

Congratulations Haiting Jiang 于2025年7月8日周二 11:54写道： > The Project Management Committee(PMC) for Apache Pulsar has invited > Mingze Han (https://github.com/hanmz) to become a committer and we are > pleased to announce that he has accepted. > > Welcome and Congratulations, Mingze Han! > > Please j

Re: [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls

+1 (binding) Thanks, Zixuan Aurora Twinkle 于2025年6月24日周二 11:57写道： > Hi, Pulsar Community. I open a new PIP for support connecting with next > available endpoint for multi-endpoint serviceUrls. PIP: > https://github.com/apache/pulsar/pull/24394 > DISCUSS: https://lists.apache.org/thread/44ztyhgm

Re: ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3.

I submitted https://github.com/apache/pulsar/pull/24451 to fix this. Thanks, Zixuan Lari Hotari 于2025年6月20日周五 05:12写道： > Hi all, > > ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3. > > Example build failures: > > pulsar-ci.yaml for branch-3.0 (ExtensibleLoadManagerImplTest

Re: ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3.

Thanks for your information! I've noticed that https://github.com/apache/pulsar/pull/24279 is causing CI failures on both the branch-3.0 and branch-3.3 branches. I recommend reverting this PR from those branches to restore CI stability. After that, we can create a new PR to cherry-pick #24279. To

Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK

+1(binding) Thanks, Zixuan Matteo Merli 于2025年6月20日周五 03:38写道： > https://github.com/apache/pulsar/pull/24364 > > --- > > # PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK > > # Context > > Currently, Pulsar requires Java 17 for the server side components and Java > 8 for the

Re: [DISCUSS] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies

This feature looks good to me. Since other policies also require the `--global` flag, it might be worth considering adding this flag under `topicPolicies` as well, to maintain consistency and clarity when applying policies at the global level. Thanks, Zixuan Yubiao Feng 于2025年5月30日周五 17:32写道： >

Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions

This PIP looks good to me overall. However, I'd like to point out a concern regarding exclusive and failover subscriptions. Currently, the unacknowledged message count is always shown as 0 for these types, which can be misleading. > Failover and Exclusive subscriptions don't require a max unacknow

Re: New PMC Member: Chris Bono

Congratulations! Lari Hotari 于2025年6月5日 周四00:27写道： > The Project Management Committee (PMC) for Apache Pulsar > is delighted to announce that Chris Bono has joined the PMC! > > Chris Bono is a key contributor to the Apache Pulsar ecosystem, > serving as author and maintainer of the Spring Pulsar

Re: New PMC member: Xiangying Meng

Congratulations, xiangying! Lari Hotari 于2025年6月4日 周三20:04写道： > The Project Management Committee (PMC) for Apache Pulsar > is delighted to announce that Xiangying Meng has joined the PMC! > > Xiangying Meng has been a contributor to the Apache Pulsar project for > a long time. Beyond his coding c

Re: [VOTE] PIP-414: Enforce topic consistency check

+1 (binding) Thanks, Zixuan Zixuan Liu 于2025年5月26日周一 12:48写道： > Hi all, > > I have created a PIP to document the topic consistency check feature > introduced in #24118. > > DISCUSS: https://lists.apache.org/thread/v7v889qzfjpqznm713wvogmx2bs4pkkb > PIP: https://github.c

Re: [VOTE] Release Apache Pulsar Helm Chart 4.1.0 based on 4.1.0-candidate-1

+1 (binding) - checked the gpg signature gpg --verify pulsar-4.1.0.tgz.asc.txt pulsar-4.1.0.tgz gpg --verify pulsar-chart-4.1.0-source.tar.gz.asc.txt pulsar-chart-4.1.0-source.tar.gz - checked the sha512 sum sha512sum --check pulsar-4.1.0.tgz.sha512.txt sha512sum --check pulsar-chart-4.1.0-s

Re: [DISCUSS] Release Pulsar Node.js client v1.13.2

+1 Baodi Shi 于2025年5月26日 周一18:07写道： > hi, I would start release node.js client v1.13.0, it include some fix, cve > and improve. > > Refer to: > - > https://github.com/apache/pulsar-client-node/compare/v1.13.1...branch-1.13?expand=1 > > Please let me know if you have any fix that need to be includ

[VOTE] PIP-414: Enforce topic consistency check

Hi all, I have created a PIP to document the topic consistency check feature introduced in #24118. DISCUSS: https://lists.apache.org/thread/v7v889qzfjpqznm713wvogmx2bs4pkkb PIP: https://github.com/apache/pulsar/pull/24213 Thanks, Zixuan

Re: [DISCUSS] PIP-414: Enforce topic consistency check

Bump Zixuan Liu 于2025年4月25日周五 18:21写道： > Hi all, > > I have created a PIP to document the topic consistency check feature > introduced in #24118. > > PIP: https://github.com/apache/pulsar/pull/24213 > > Feedback and suggestions are welcome. > > Thanks, > Zixuan >

Re: [VOTE] Release Apache Pulsar 3.3.7 based on 3.3.7-candidate-1

+1 (binding) - Built from source - Checked the signatures of the source and binary release artifacts - Ran pulsar standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Thanks, Zixuan Lari Hotari 于2025年5月20日周二 23:27写道： > Hello

Re: [VOTE] Release Apache Pulsar 4.0.5 based on 4.0.5-candidate-1

+1 (binding) - Built from source - Checked the signatures of the source and binary release artifacts - Ran pulsar standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Thanks Zixuan Lari Hotari 于2025年5月20日周二 21:33写道： > Hello

Re: [VOTE] Release Apache Pulsar 3.0.12 based on 3.0.12-candidate-1

+1(binding) - Checked the sign and sha512sum - Built from the candidate source - Ran the Docker image with standalone Thanks Zixuan Lari Hotari 于2025年5月20日周二 20:45写道： > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version > 3.0.12 based on 3.0.1

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

-1 (binding) This source file should not include the `.git` folder, please check: ``` *$ *tree -a ├── .asf.yaml ├── *.git* │ ├── config │ ├── description │ ├── FETCH_HEAD │ ├── HEAD │ ├── *hooks* ``` Thanks, Zixuan Zike Yang 于2025年5月16日周五 18:07写道： > Hi everyone, > Please rev

Re: [VOTE] PIP-415: Support getting message ID by offset

+1 binding xiangying meng 于2025年5月8日 周四10:59写道： > Hi, all > > I`d like to start a vote on PIP-415: Support getting message ID by offset. > > You can find the proposal at > https://github.com/apache/pulsar/pull/24220 and the discussion thread > at https://lists.apache.org/thread/7kmo3robyx74p81891

Re: [VOTE] PIP-416: Add a new topic method to implement trigger offload by size threshold

+1 (binding) Thanks, Zixuan shoyo0814 于2025年5月11日周日 16:38写道： > Hi all, > > > This is a call for vote to approve PIP-416: Add a new topic method to > implement trigger offload by size threshold > > > The proposal is available at: > https://github.com/apache/pulsar/pull/24276 > and the discussion

Re: [VOTE] Release Apache Pulsar Helm Chart 4.0.1 based on 4.0.1-candidate-1

+1 (binding) # Verify signature gpg --verify pulsar-chart-4.0.1-source.tar.gz.asc.txt pulsar-chart-4.0.1-source.tar.gz gpg --verify pulsar-4.0.1.tgz.asc.txt pulsar-4.0.1.tgz # Verify sha512 sha512sum --check pulsar-chart-4.0.1-source.tar.gz.sha512.txt sha512sum --check pulsar-4.0.1.tgz.sha512.txt

[DISCUSS] PIP-414: Enforce topic consistency check

Hi all, I have created a PIP to document the topic consistency check feature introduced in #24118. PIP: https://github.com/apache/pulsar/pull/24213 Feedback and suggestions are welcome. Thanks, Zixuan

Re: [VOTE] Pulsar Client Go Release 0.15.0 Candidate 2

> Hi, Zixuan, This is not a regression bug. Since there are still some effects needed for this PR. I think we don't need to block the release. +1 Thanks, Zixuan Zike Yang 于2025年3月26日周三 18:46写道： > Hi everyone, > Please review and vote on the release candidate #2 for the version > 0.15.0, as fol

Re: [DISCUSS] Revert PR 24118 [fix][broker] Add topic consistency check for release branches

ing the partitioned topic can clear old data > and avoid new partitions being deleted by deleting the partitioned > topic. > > Thanks, > yunze > > On Wed, Apr 23, 2025 at 11:47 AM Zixuan Liu wrote: > > > > I noticed that the following KoP tests need to be updated: &g

Re: [DISCUSS] Revert PR 24118 [fix][broker] Add topic consistency check for release branches

and then producers will reconnect the partitions to continue > > producing. However, with this change, the producers will fail to > > reconnect due to `NotAllowedException`, Sometimes, users just want to > > discard huge legacy data. Regarding the loss of partition metadata, it

Re: [DISCUSS] Revert PR 24118 [fix][broker] Add topic consistency check for release branches

I'm aware that #24118 breaks some test cases, but I believe those test cases were incorrect. I also flagged this PR as introducing breaking changes in the mailing list, please see https://lists.apache.org/thread/g1jq0vkq0wt28mdnbg63bpw8fpx9ml42 I'd like to better understand the scope of the breaka

[DISCUSS] Cherry-pick #24118 and #24154 to the branch-3.0 and branch-4.0

Hi all, https://github.com/apache/pulsar/pull/24118 https://github.com/apache/pulsar/pull/24154 The two PR is used to improve the user experience and help the user to correctly use the topic name: - For non-partitioned topic: If partition metadata exists (which shouldn't be there), the broker wi

Re: [VOTE] Pulsar Client Go Release 0.15.0 Candidate 2

-1 https://github.com/apache/pulsar-client-go/pull/1345 should be included in the 0.15.0. Thanks, Zixuan Zike Yang 于2025年3月26日周三 18:46写道： > Hi everyone, > Please review and vote on the release candidate #2 for the version > 0.15.0, as follows: > [ ] +1, Approve the release > [ ] -1, Do not a

Re: [VOTE] PIP-409: support producer configuration for retry/dead letter topic producer

+1 (non-binding) Thanks, Zixuan thetumbled 于2025年2月27日周四 12:02写道： > Hi, Pulsar Community. > I would like to start the voting thread for PIP-409: support producer > configuration for retry/dead letter topic producer. > pip link: https://github.com/apache/pulsar/pull/24022 > implementation

Re: [DISCUSS] PIP-408: add maxRetryRequestTimes in ClientConfigurationData and remove duplicate retry logic

+1 (non-binding), I have left one comment. Thanks, Zixuan WenZhi Feng 于2025年2月24日周一 14:36写道： > LGTM, i leave some comments in pr. > > On 2025/02/18 02:05:48 吕泓瑾 wrote: > > Dear Apache Pulsar Community, > > I would like to propose introducing a configuration property in > > ClientConfigurationDa

[VOTE] PIP-398: Subscription replication on the broker, namespace and topic levels

Hi all, I would like to vote for https://github.com/apache/pulsar/pull/23770 Thanks, Zixuan

Re: [DISCUSS] PIP-398: Subscription replication on the namespace and topic levels

This PIP has been updated, and the new design is as compatible with existing designs as possible, and doesn't depend on https://github.com/apache/pulsar/pull/23757. Thanks, Zixuan Zixuan Liu 于2024年12月23日周一 16:08写道： > Hi, Pulsar community, > > Subscription replication is an import

Re: [DISCUSS] Pulsar Manager 0.5. 0 release

+1 xiangying meng 于2025年1月10日周五 10:54写道： > Hi all, > > I would like to release the Pulsar Manager 0.5.0. > > It has been a year since the last release, and there are several new > features and bug fixes in the 0.5.0 milestone. > It's time to release a new version. > > Please let me know if you h

[VOTE] Pulsar Client Go Release 0.15.0 Candidate 1

Hi everyone, Please review and vote on the release candidate 1 for the version 0.15.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This is the first release candidate for Apache Pulsar Go client, version 0.15.0. It fixes the follo

Re: [VOTE] PIP-399: Fix Metric Name for Delayed Queue

+1(non-binding) Thanks, Zixuan thetumbled 于2025年1月3日周五 18:08写道： > Hi, Pulsar Community. > I would like to start the voting thread for PIP-399: Fix Metric Name for > Delayed Queue. > PIP link: https://github.com/apache/pulsar/pull/23789 > Implementation link: https://github.com/apache/puls

Re: [DISCUSS] PIP-399: Fix Metric Name for Delayed Queue

+1 Tao Jiuming 于2024年12月28日周六 17:41写道： > +1 > > thetumbled 于2024年12月27日 周五17:27写道： > > > Hi, Pulsar Community. > > I open a new PIP to fix metric name for delayed queue, which involves > > changing metirc name and a pip is needed. > > pip link: https://github.com/apache/pulsar/pull/2378

Re: [DISCUSS] PIP-398: Subscription replication on the namespace and topic levels

This PIP has been updated to adapt to the consumer-level configuration. Zixuan Liu 于2024年12月23日周一 16:08写道： > Hi, Pulsar community, > > Subscription replication is an important feature in the failover scenario, > I made a PIP to add the subscription replication feature on the nam

[DISCUSS] Release Pulsar Client Go 0.15.0

Hi all, I would like to release the Pulsar Client Go 0.15.0. https://github.com/apache/pulsar-client-go/milestone/17?closed=1 Thanks, Zixuan

[DISCUSS][Cherry-pick] #23757 makes replicateSubscriptionState nullable

Hi all, #23757 makes replicateSubscriptionState nullable, which is important for supporting subscription replication on the namespace and topic levels. So I want to cherry-pick #23757 to the branch-3.0, branch-3.3, branch-4.0. Thanks, Zixuan

Re: [DISCUSS] PIP-398: Subscription replication on the namespace and topic levels

S version. > But for long-term consideration, we should make the Admin API > easy to understand and simple. We should not let users check many > places to understand why the replicateSubscriptionState is enabled or not. > > Regards, > Penghui > > > > On Mon, Dec 23, 20

Re: [DISCUSS] PIP-398: Subscription replication on the namespace and topic levels

-level configuration? > Zixuan, > > would you mind reviewing that PR? > > Since this recent PR #23769 is in the same area, I think it would make > > sense to combine the work in a single PIP to ensure that we achieve > > consistency across the changes. > > > > -

Re: [DISCUSS] PIP-398: Subscription replication on the namespace and topic levels

the changes. > > -Lari > > On Mon, 23 Dec 2024 at 10:08, Zixuan Liu wrote: > > > Hi, Pulsar community, > > > > Subscription replication is an important feature in the failover > scenario, > > I made a PIP to add the subscription replication feature on the namesp

[DISCUSS] PIP-398: Subscription replication on the namespace and topic levels

Hi, Pulsar community, Subscription replication is an important feature in the failover scenario, I made a PIP to add the subscription replication feature on the namespace and topic levels. PIP: https://github.com/apache/pulsar/pull/23770 Thanks, Zixuan

Re: [VOTE] Apache Pulsar Adapters Release 3.0.0 Candidate 2

You also checkout the https://github.com/apache/pulsar-adapters/wiki/Validating-release-candidates document to verify this release. Thanks, Zixuan Zixuan Liu 于2024年12月9日周一 21:09写道： > Hello Apache Pulsar Community, > > This is the second release candidate for Apache Pulsar Adapter

[VOTE] Apache Pulsar Adapters Release 3.0.0 Candidate 2

Hello Apache Pulsar Community, This is the second release candidate for Apache Pulsar Adapters version 3.0.0. It fixes the following issues: https://github.com/apache/pulsar-adapters/milestone/5?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72

Re: [VOTE] Release Apache Pulsar Adapters 3.0.0 based on 3.0.0-candidate-1

Ping. Zixuan Liu 于2024年11月16日周六 02:03写道： > Hello Apache Pulsar Community, > > > This is a call for the vote to release the Apache Pulsar Adapters version > 3.0.0 based on 3.0.0-candidate-1. > > This is the first Apache Pulsar Adapters release to support Pulsar 3.0.7 >

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

+1 (non-binding) 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: https://github.com/apache/pulsar/pull/23601 > Implementation PR: https://github.com/apa

[VOTE] Release Apache Pulsar Adapters 3.0.0 based on 3.0.0-candidate-1

Hello Apache Pulsar Community, This is a call for the vote to release the Apache Pulsar Adapters version 3.0.0 based on 3.0.0-candidate-1. This is the first Apache Pulsar Adapters release to support Pulsar 3.0.7 release. The vote will be open for at least 72 hours. It is adopted by majority ap

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

+1(non-binding) Thanks, Zixuan Girish Sharma 于2024年11月11日周一 15:02写道： > Hi Pulsar dev community, > > I would like to start the voting thread for PIP-385 Add rate limit > semantics to pulsar protocol and Java Client. > > Proposal PR: https://github.com/apache/pulsar/pull/23398 > Rendered PIP - >

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

+1 Thanks, Zixuan Yunze Xu 于2024年11月6日周三 20:45写道： > Hi all, > > I wrote a PIP (https://github.com/apache/pulsar/pull/23567) to enable > batch index ACK by default. > > From my experiences, the default ACK semantics are really confusing > and it's hard to explain the implementation details to us

Re: [VOTE] PIP-386: Add resetIncludeHead in CommandSubscribe for startMessageIdInclusive implementation

Thanks for your driving this idea. > Maybe we can reopen the pip-150？ I think we can reopen the pip-150, and then you can continue to improve that. Thanks, Zixuan Jiawen Wang <15353143...@163.com> 于2024年10月17日周四 11:35写道： > Hi, dev: > > > > > This thread is to start a vote for PIP-386: Add rese

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

Hi lari, I can drive the build system and CI setup, could you assign this task to me? Thanks, Zixuan Lari Hotari 于2024年10月18日周五 13:51写道： > There has been some interest in continuing to use Pulsar SQL in the > future. To facilitate this, I have taken the following actions: > - Extracted the pul

Re: [VOTE] Release Apache Pulsar 4.0.0 based on 4.0.0-candidate-1

+1 (non-binding) - Verified checksum and signature - Built from source - Ran standalone with produce and consume by bin package - Ran standalone with produce and consume by docker Thanks, Zixuan Lari Hotari 于2024年10月15日周二 01:01写道： > Hello Apache Pulsar Community, > > This is a call for the vot

[NOTICE][Regression] PR 23378 was cherry-picked to the branch-3.0

Hi all, I recently encountered an issue with the Pulsar client used in the broker interceptor, which broke the broker’s response command. To address this, I submitted a PR[1], which has now been cherry-picked to the branch-3.0. Since this change affects core functionality, it may introduce regres

Re: [DISCUSS] PIP-386: Add resetIncludeHead in CommandSubscribe for startMessageIdInclusive implementation

Same PIP: https://github.com/apache/pulsar/issues/14883 FYI. Jiawen Wang <15353143...@163.com> 于2024年10月9日周三 23:43写道： > Hi dev, I proposed a PIP: https://github.com/apache/pulsar/pull/23427, > this pip is intended to fix issue > https://github.com/apache/pulsar/issues/23239. > > Please take a lo

Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout

+1 (non-binding) Thanks, Zixuan Baodi Shi 于2024年8月28日周三 16:04写道： > +1(binding) > > Thanks, > Baodi Shi > > ZhangJian He 于2024年8月28日周三 14:41写道： > > > > +1 nonbinding > > > > Thanks > > ZhangJian He > > Twitter: shoothzj > > Wechat: shoothzj > > > > On Wed, Aug 28, 2024 at 2:06 PM Jie crossover

Re: [VOTE] Pulsar Client Go Release 0.13.0 Candidate 2

+1 (non-binding) - Verified the shasum and asc. - `make build` works fine on go1.22.5 Thanks, Zixuan Zike Yang 于2024年7月15日周一 19:14写道： > Hi everyone, > Please review and vote on the release candidate #2 for the version > 0.13.0, as follows: > [ ] +1, Approve the release > [ ] -1, Do not approv

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

-1 We must add https://github.com/apache/pulsar-client-go/pull/1243 to the 0.13.0, which is a regression bug fix. Thanks, Zixuan Zike Yang 于2024年7月12日周五 10:27写道： > Hi everyone, > Please review and vote on the release candidate #1 for the version > 0.13.0, as follows: > [ ] +1, Approve the rele

Re: [DISCUSS] PIP-361: Support URI, DNS, RID, IP based Token building from client's X.509 Certificate SAN Extensions

e you suggesting the pulsar community wont benefit from this and host it > in other git repo as separate plugin ? > > Thanks > Naresh > On Thu, 20 Jun 2024 at 7:54 PM, Zixuan Liu wrote: > > > Hi naresh, > > > > Right now the Pulsar can only get the role from a co

Re: [DISCUSS] PIP-363: Add callback parameters to the method: org.apache.pulsar.client.impl.SendCallback.sendComplete.

+1 Jie crossover 于2024年6月19日周三 16:12写道： > Hi, Pulsar Community. > > I have created a PIP to add an `OpSendMsgStats` parameter to the > `SendCallback` interface. > This will help us implement `messaging.publish.messages` metric. > PIP link: https://github.com/apache/pulsar/pull/22940 > OpenTelem

Re: [DISCUSS] PIP-361: Support URI, DNS, RID, IP based Token building from client's X.509 Certificate SAN Extensions

Hi naresh, Right now the Pulsar can only get the role from a common name, your PIP is an awesome idea that supports URI, DNS, RID, IP based Token as role, and is very helpful for large organizations. In this PIP, you will introduce many configurations of identity mechanisms, which are complex if

Re: [VOTE] PIP-351: Additional options for Pulsar-Test client to support KeyStore based TLS

+1 (non-binding) BTW, a PIP requires 3 binding votes. Thanks, Zixuan Shasank Sekhar Pandey 于2024年5月17日 周五03:21写道： > Hello, > > I would like to start a voting thread for PIP-351: [improve][pip] PIP-351: > Additional options for Pulsar-Test client to support KeyStore based TLS by > shasank112001

Re: [DISCUSS] PIP-351: Additional options for Pulsar-Test client to support KeyStore based TLS

+1, add JKS support to the pulsar-perf client. Thanks, Zixuan Shasank Sekhar Pandey 于2024年5月17日 周五03:06写道： > Hi all, > > I pushed a proposal to add a keystore related options to pulsar > test-client. This will allow users of tools like Pulsar Perf to use > keystores during their testing, as curr

Re: [DISCUSS] Release Apache Pulsar Python Client 3.4.1

Meanwhile, would > you like to start the release for Python client 3.5.1? > > Thanks, > Yunze > > On Sat, May 11, 2024 at 5:54 PM Zixuan Liu wrote: > > > > > Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already > > released. It's too he

Re: [DISCUSS] Cherry-pick topic load failed count metrics to release branches

The master metric name differs because we didn't add a metric with the pulsar prefix. https://github.com/apache/pulsar/pull/20720 fixes that. Another thing is that this cherry-pick broke the branch-2.10 CI: https://github.com/apache/pulsar/pull/13785 upgrades prometheus-client on the branch-2.11

Re: [VOTE] PIP-347: add role field in consumer's stat

+1 (non-binding) Thanks, Zixuan PengHui Li 于2024年5月14日周二 18:08写道： > +1 (binding) > > Regards, > Penghui > > On Tue, May 14, 2024 at 5:50 PM Enrico Olivelli > wrote: > > > +1 (binding) > > > > Enrico > > > > Il giorno mar 14 mag 2024 alle ore 11:31 太上玄元道君 ha > > scritto: > > > > > +1 nonbindin

Re: [DISCUSS] Release Apache Pulsar Python Client 3.4.1

for now. > > > > However, it would be better to remove the `functions` component from > > pulsar-client-python because the Python client itself never uses these > > dependencies. See my discussion [1] before. Since python functions is > > maintained in the Pulsar main

[DISCUSS] Release Apache Pulsar Python Client 3.4.1

Hi all, https://github.com/apache/pulsar-client-python/pull/174 breaks the python-client installation in the pulsar arm image, and then the release manager of pulsar@3.3.0 will take about 2 hours to build the grpcio wheel, please see https://github.com/nodece/pulsar-python-deps-build/actions/runs/

Re: [VOTE] PIP-349: Add systemCursorNames ignore list for TTL check

+1 (non-binding) Thanks, Zixuan Yubiao Feng 于2024年5月8日周三 18:22写道： > +1 (binding) > > Thanks > Yubiao Feng > > On Tue, May 7, 2024 at 11:25 AM Hang Chen wrote: > > > Hi guys, > > I want to start voting for PIP-349. > > > > PIP: https://github.com/apache/pulsar/pull/22651 > > PR: https://gi

Re: [DISCUSS] PIP-349: Add systemCursorNames ignore list for TTL check

It seems that we only need to keep `additionalSystemCursorNames`. `systemCursorNames` is unnecessary, which should be built-in and immutable. Thanks, Zixuan Hang Chen 于2024年5月6日周一 22:22写道： > >We can make this "configurable", but the well known names should be always > handled automatically > >

Re: [DISCUSS] Restore the slf4j version to 1.7.x

ependencies and depend on the slf4j dependency from > `pulsar-*`. So a refactoring of pom.xml is needed for the latest > Pulsar. > > Thanks, > Yunze > > On Sat, Apr 27, 2024 at 12:47 PM Zixuan Liu wrote: > > > > > I don't think so. As a logging facade, there

Re: [DISCUSS] Restore the slf4j version to 1.7.x

${slf4j.version} > > runtime > > > > > > ``` > > > > And then it works, but it also shows how much changes are needed > > caused by such a PR in the upstream. Existing users might already > > depend on the carried slf4j dependency from Puls

Re: [DISCUSS] Restore the slf4j version to 1.7.x

After upgrading to 2.0.13, some issues were exposed, and we will encounter them sooner or later. When upgrading the slf4j in the pulsar, I also encountered the problem you mentioned, so I used the `` to exclude the org.slf4j or org.apache.logging.log4j, and so on. Do you think this approach is fa

Re: [VOTE] PIP-327 Support force topic loading for unrecoverable errors

+1 (non-binding) > Can we please close this VOTE thread as it's been more than 8 days to this > thread and 4 months since we created a PIP. The condition for PIP to pass is 3 bindings. Let's wait a moment. Thanks, Zixuan Rajan Dhabalia 于2024年4月25日周四 02:51写道： > Hi, > > Can we please close this

Re: [DISCUSS] Upgrading to Jetty 12 since Jetty 9.4.x has reached end-of-line in June 2022

> do we first release 3.3.x asap and then tackle this upgrade for Pulsar 3.4.x +1 Lari Hotari 于2024年4月17日周三 21:57写道： > Hi, > > Pulsar Broker and Pulsar Proxy use Jetty 9.4.x. Jetty 9.4.x has reached > end-of-line already in June 2022. Jetty 9.4.x has been receiving security > updates until now a

Re: [DISCUSS] Plan for Pulsar Go Client 1.0.0

client-go/issues/1187 > > > is actually tracking on it. > > > > > > > This will increase our maintenance times. > > > > > > We maintain two versions of the API, but they could share the same > > > internal code. I don't think this wil

Re: [DISCUSS] GEO-replication issues on topic level

> the topic level. That is not a break-changing process that does not > require a proposal or a simple proposal to record this improvement. > > Thanks, > Xiangying > > On Fri, Mar 22, 2024 at 4:44 PM Zixuan Liu wrote: > > > > Hi all, > > > > The GEO-repl

Re: [DISCUSS] Plan for Pulsar Go Client 1.0.0

I don't recommend breaking user APIs. There are many ways we can avoid it. > 1. We should support passing the context to some IO-related methods like `Ack`, `Close`, `Flush`, etc, or any other methods. There is an issue related to this discussion. [2] We can add a method with context, so like: Cl

[DISCUSS] GEO-replication issues on topic level

Hi all, The GEO-replication can be enabled on the Namespace and topic levels. When GEO-replication is enabled on the namespace level, it automatically creates the topic for the remote cluster, but the topic level misses this feature, which can cause unexpected problems. When two clusters use dif

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

Top tison 于2023年6月30日周五 09:58写道： > Hi, > > I'd like to propose applying a consistent code style (especially whitespace > and indent) with an autotool Spotless. > > // Background > > Over and over we argue contributors reformat their patch manually for > checkstyle violations, or even whitespace

Re: [DISCUSSION] Proposal to Replace Pulsar's Homegrown Configuration Framework with Gestalt Config

+1 This is a good idea that using Gestalt config, which supports json, yaml, env and so on. One notice that Gestalt requires Java 11 or higher. Thanks, Zixuan Lari Hotari 于2024年2月21日 周三17:27写道： > Hello everyone, > > I would like to bring up an issue with Pulsar's containers, specifically > reg

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

+1 (non-binding) Thanks, Zixuan PengHui Li 于2024年3月15日周五 09:47写道： > +1 (binding) > > Regards, > Penghui > > On Fri, Mar 15, 2024 at 2:32 AM Asaf Mesika wrote: > > > +1 (non-binding) > > > > On Thu, Mar 14, 2024 at 8:29 PM Apurva Telang > > wrote: > > > > > +1 (non-binding) > > > > > > On Thu,

Re: [VOTE] Pulsar Release 2.10.6 Candidate 2

https://github.com/apache/pulsar/pull/20990 should be cherry-picked to branch-2.10, this is an important fix. Xiangying Meng 于2024年3月8日周五 10:09写道： > This is the first release candidate for Apache Pulsar, version 2.10.6. > > It fixes the following issues: > > https://github.com/apache/pulsar/pull

Re: [VOTE] PIP-343: Use picocli instead of jcommander

Close this vote with 3 +1(binding) and 1 +1(non-binding). Thanks, Zixuan Zixuan Liu 于2024年3月6日周三 23:03写道： > Hello, > > A new proposal to improve the CLI user experience. > > PIP: https://github.com/apache/pulsar/pull/22181 > Discussion thread: > https://li

Re: [DISCUSS] PIP-343: Use picocli instead of jcommander

oschi @Enrico Olivelli Zixuan Liu: This feature has different implementations between pulsar-admin/client and pulsar-shell. pulsar-admin and pulsar-client uses the completion script, which will be installed to you shell(bash, zsh), please https://picocli.info/autocomplete.html pulsar-shell depen

[VOTE] PIP-343: Use picocli instead of jcommander

Hello, A new proposal to improve the CLI user experience. PIP: https://github.com/apache/pulsar/pull/22181 Discussion thread: https://lists.apache.org/thread/ydg1q064cd11pxwz693frtk4by74q32f PR: https://github.com/apache/pulsar/pull/22209 Thanks, Zixuan

Re: [VOTE] Pulsar Release 2.10.6 Candidate 1

t; attention. We appreciate your diligence in adhering to Pulsar's > release policy. > > Best regards, > > Xiangying > > On Wed, Mar 6, 2024 at 4:22 PM Zixuan Liu wrote: > > > > Thank you for releasing 2.10.6. > > > > According to the release poli

Re: [VOTE] Pulsar Release 2.10.6 Candidate 1

Thank you for releasing 2.10.6. According to the release policy defined [0] by Pulsar, this version is EOL and does not require further maintenance. If we need to continue to maintain the 2.10, we must discuss the maintenance lifecycle of the 2.10, and update our doc. - [0] https://pulsar.apache

Re: [DISCUSS] Retire pulsar-all Docker image and spin-off Python Functions runtime

+1 This is a good idea, and then we must provide a document on building the own connector image and python functions runtime image. Thanks, Zixuan Matteo Merli 于2024年3月6日周三 07:04写道： > The docker image `pulsar-all` is a convenience image that is created on top > of the base `pulsar` image, incl

[DISCUSS] PIP-343: Use picocli instead of jcommander

Hello, A new proposal to improve the CLI user experience. PIP: https://github.com/apache/pulsar/pull/22181 Thanks, Zixuan

Re: [ANNOUNCE] New Committer: Kiryl Valkovich

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 Management Committee (PMC) has invited > > Kiryl Valkovich https://github.com/visortelle to become a committer, > and we > > are pleased to

Re: [DISCUSS] Migrate CLI parser from jcommander to picocli

ks based on commands. > > - Ran Gao > > On 2024/02/21 05:07:46 Zixuan Liu wrote: > > Hi Pulsar Community, > > > > The pulsar CLI(pulsar-admin, pulsar-client, pulsar-shell, and so on) uses > > the jcommander [1] as CLI parser, which is an awesome project, but the >

Re: [DISCUSS] Migrate CLI parser from jcommander to picocli

ui Li ha scritto: > > > +1 Great user experience improvement. > > > > Regards, > > Penghui > > > > On Sat, Feb 24, 2024 at 3:15 AM Zixuan Liu wrote: > > > > > > Can you please share some pointers ? > > > > > > Only `org.apach

Re: [DISCUSS] Migrate CLI parser from jcommander to picocli

ome methods. I need to carefully study how to do it. This thread is just a preliminary idea to replace jcommander, and I will write a PIP later. Thanks, Zixuan Enrico Olivelli 于2024年2月23日周五 22:59写道： > Il Ven 23 Feb 2024, 04:34 Zixuan Liu ha scritto: > > > Thanks for the feedback! &

Re: [DISCUSS] Migrate CLI parser from jcommander to picocli

Thanks for the feedback! > Please take into account Pulsar Shell extensions This is a tricky issue, I noticed that it depends on jcommander here, and I need to break this interface, and make it compatible with Pulsar Shell implementation. I will create a draft PR to migrate the CLI parser from j

  1   2   3   4   >