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

Re: [ANNOUNCE] New Committer: Asaf Mesika

Congratulations Asaf! Lari Hotari 于2024年2月21日周三 00:51写道： > The Apache Pulsar Project Management Committee (PMC) has invited > Asaf Mesika https://github.com/asafm to become a committer and we > are pleased to announce that he has accepted. > > Welcome and Congratulations, Asaf Mesika! > > Please

[DISCUSS] Migrate CLI parser from jcommander to picocli

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 maintainer is not active and cannot keep up with modern CLI features(auto-completion, sub-command, native-images, suggest commands,

Re: [VOTE] PIP-335: Oxia metadata support

+1(non-binding) Thanks, Zixuan Zike Yang 于2024年2月6日周二 19:29写道： > +1 > > Thanks, > Zike Yang > > On Tue, Feb 6, 2024 at 6:58 PM Enrico Olivelli > wrote: > > > > +1 (binding) > > > > Enrico > > > > Il giorno mar 6 feb 2024 alle ore 11:36 houxiaoyu > > ha scritto: > > > > > > +1 nonbinding > > >

Re: [DISCUSS] PIP-335: Oxia metadata support

+1 Thanks, Zixuan Matteo Merli 于2024年2月1日周四 07:58写道： > https://github.com/apache/pulsar/pull/22009 > > === > > # PIP-335: Supporty Oxia metadata store plugin > > # Motivation > > Oxia is a scalable metadata store and coordination system that can be used > as the core infrastructure > to

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

This PIP has been approved by 3 +1 (binding): - Jiwei - Yunze - Penghui Thanks, Zixuan Zixuan Liu 于2024年1月15日周一 17:33写道： > Hi Pulsar Community, > > Voting for PIP-330: getMessagesById gets all messages > > PIP: https://github.com/apache/pulsar/pull/21873 > Discussi

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 2

+1 (non-binding) - Checked the checksums and signatures - Built with Temurin-17.0.6+10 - Run standalone - Checked producer and consumer Thanks, Zixuan guo jiwei 于2024年1月16日周二 15:57写道： > This is the second release candidate for Apache Pulsar version 3.2.0. > > It fixes the following issues: > h

Re: [VOTE] PIP-329: Strategy for maintaining the latest tag to Pulsar docker images

+1(non-binding) Thanks, Zixuan Zike Yang 于2024年1月15日周一 16:14写道： > Hi, all > > I'm starting the vote for PIP-329: Strategy for maintaining the latest > tag to Pulsar docker images > > PIP link: https://github.com/apache/pulsar/pull/21872 > > Thanks, > Zike Yang >

[VOTE] PIP-330: getMessagesById gets all messages

Hi Pulsar Community, Voting for PIP-330: getMessagesById gets all messages PIP: https://github.com/apache/pulsar/pull/21873 Discussion thread: https://lists.apache.org/thread/vqyh3mvtvovd383sd8zxnlzsspdr863z Thanks, Zixuan

[DISCUSS] PIP-330: getMessageById gets all messages

Hi Pulsar Community, I want to add a new method that gets all messages by message id to the pulsar-client-admin module. Please see the PIP: https://github.com/apache/pulsar/pull/21873 Thanks, Zixuan

Re: [DISCUSS] Release Pulsar Go Client 0.12.0

+1 Thanks, Zixuan Zike Yang 于2024年1月4日周四 12:29写道： > Hi everyone, > > I would like to propose releasing the Pulsar Go Client 0.12.0. > > It has been several months since the last release. And there are > several new features and bug fixes in the master branch[0]. We have > also merged the pulsar

Re: [DISCUSS] Return value of org.apache.pulsar.client.admin.Topics#getMessageById

ex" that represents a MessageID instead. If > we're going to replace BK with other storage systems in future (though > I think it's far way from now), we can still reuse this API. > > Thanks, > Yunze > > On Thu, Dec 28, 2023 at 5:21 PM Zixuan Liu wrote: >

[DISCUSS] Return value of org.apache.pulsar.client.admin.Topics#getMessageById

Hi Pulsar Community, I want to discuss the return value of the `org.apache.pulsar.client.admin.Topics#getMessageById`, which returns `Message`. If the message is a batch message, we only get the first message from the batch message. So I want to change this behavior by returning `List`, and in th

Re: [DISCUSS] 2.10 EOL?

Hi Michael, The Pulsar release policy [0] defines the Pulsar 2.10 release line, which has now been EOL. In fact, we still cherry-pick the commit to the branch-2.10 from the master, see [1]. I think the Pulsar 2.10 has been stable in the past few years, and can be run by using the JDK 8(Recommende

Re: [DISCUSS] PIP-324: Alpine Docker images

+1. It is a good idea to use the Alpine image to run the Pulsar, as it is more secure. However, switching images may affect downstream users, and I am wondering if it is possible to provide multiple docker tags: - latest: using the Ubuntu image - alpine: using the Alpine image Thanks, Zixuan

Re: [DISCUSS] Strategy for pushing the latest tag to Pulsar docker images

Hi Zike, > I prefer the 1st way as well. +1 Thanks, Zixuan Yunze Xu 于2023年12月5日周二 20:26写道： > I prefer the 1st way as well. > > Thanks, > Yunze > > On Tue, Dec 5, 2023 at 5:11 PM Zike Yang wrote: > > > > Hi, everyone, > > > > There seems to be a gap in our current release process concerning th

Re: [DISCUSS] Release Pulsar 3.1.2

+1 Thanks, Zixuan guo jiwei 于2023年11月27日周一 11:09写道： > +1 > > > Regards > Jiwei Guo (Tboy) > > > On Mon, Nov 27, 2023 at 9:55 AM Yubiao Feng > wrote: > > > +1 > > > > Thanks > > Yubiao Feng > > > > On Sun, Nov 26, 2023 at 4:10 PM houxiaoyu wrote: > > > > > Hi all, > > > > > > I would like to p

Re: [ANNOUNCE] New Committer: Chris Bono

Congrats! Thanks, Zixuan Lari Hotari 于2023年11月20日周一 18:10写道： > The Apache Pulsar Project Management Committee (PMC) has invited > Chris Bono https://github.com/onobc to become a committer and we > are pleased to announce that he has accepted. > > Welcome and Congratulations, Chris Bono! > > Ple

Re: [VOTE] PIP-303: Add optional parameters for getPartitionedStats

+1(non-binding) Thanks, Zixuan Jie crossover 于2023年11月16日周四 11:01写道： > Hi All, This thread is to start a vote for PIP-303. PIP: > https://github.com/apache/pulsar/pull/21228 Discussion thread: > https://lists.apache.org/thread/c92043zq6lyrsd5z1hnln48mx858n7vj > -- > Best Regards！ > crossoverJie

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

+1 (non-binding) Thanks, Zixuan PengHui Li 于2023年11月13日周一 16:22写道： > +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) >

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

Congrats! Thanks, Zixuan Cong Zhao 于2023年11月13日周一 18:01写道： > Congrats! Yubiao > > Thanks, > Cong > > On 2023/11/13 07:36:27 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 >

Re: [VOTE] PIP-300: Add custom dynamic configuration for plugins

Close this vote with 4 +1(binding) and 1 +1(non-binding). Thanks, Zixuan Liu Zixuan Liu 于2023年9月26日周二 10:54写道： > Zixuan Liu 于2023年9月26日周二 10:54写道： > Hi Pulsar Community, > > Voting for PIP-300: https://github.com/apache/pulsar/pull/21127 > Discussion thread: > https:

Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks, Zixuan Baodi Shi 于2023年10月16日周一 21:13写道： > > 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...branch-2.11 > > We

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

+1 Thanks, Zixuan guo jiwei 于2023年10月18日周三 20:45写道： > > Hi dev, >Currently WebSocket only supports the consumption of a single topic, > which cannot satisfy users' consumption scenarios of multiple topics. So > in order to support consumption of multiple topics or pattern topics, I > start

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

+1 for compatibility with Java 21. Next step: Migrating the Pulsar Server runtime to Java 21 from Java 17 in the Docker image and CI. Pulsar Client/Admin continues to use Java 8. Thanks, Zixuan Lari Hotari 于2023年10月18日周三 06:02写道： > > Dear Pulsar community, > > Java 21 was released on September

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

+1(non-binding) Zili Chen 于2023年10月19日周四 10:10写道： > > +1 binding > > On 2023/10/17 07:23:29 Diego Salvi wrote: > > Hi Community, > > > > This thread is to start a vote for PIP-305. > > > > PIP: https://github.com/apache/pulsar/pull/21352 > > Discussion thread: > > https://lists.apache.org/thread/

Re: [DISCUSS] PIP-305: Customize DNSes to use for Pulsar Client

+1, LGTM When configuring the `dnsServerAddresses`, we can configure the custom DNS Servers for the Pulsar client in the program. Thanks, Zixuan Diego Salvi 于2023年10月12日周四 23:00写道： > > Hi Pulsar Community, > > This is a PIP discussion on how support custom DNSes configuration to be > used by th

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

+1 Thanks, Zixuan Yubiao Feng 于2023年10月7日周六 21:05写道： > > Hi Kecona > > Sorry, I think I did not clear what I wanted to say. And correct it: could > you add more detail to the Motivation, for example: I need the field > `ordering_key` to do something, but I can not get it from Publish Context. >

[VOTE] PIP-300: Add custom dynamic configuration for plugins

Hi Pulsar Community, Voting for PIP-300: https://github.com/apache/pulsar/pull/21127 Discussion thread: https://lists.apache.org/thread/ysnsnollgy1b6w1dsvmx1t1y2rz1tyd6 Thanks, Zixuan

Re: [DISCUSS] PIP-300: Add custom dynamic configuration for plugins

t; > the active branches by the current fact. Because this is a new feature > > > and it's not a bug fix or security issue. > > > > > > We can wait for other contributor's ideas. WDYT? > > > > > > Thanks, > > > Mattison > > >

Re: [DISCUSS] PIP-300: Add custom dynamic configuration for plugins

g. Do you have any issue or > feature request in the community that can demonstrate this feature is > required to cherry-pick? > > > Best, > Mattison > On 12 Sep 2023 at 11:25 +0800, Zixuan Liu , wrote: > > BTW, I think we can cherry-pick this feature to the Pulsar 2.10.

Re: [DISCUSS] PIP-300: Add custom dynamic configuration for plugins

BTW, I think we can cherry-pick this feature to the Pulsar 2.10. As far as I know, the Pulsar 2.10 is a stable/main version, because many users are using it. Thanks, Zixuan Zixuan Liu 于2023年9月5日周二 17:09写道： > > Hi Pulsar Community, > > Discuss for PIP-300: https://github.com/apache

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

+1 (non-binding) Best, Zixuan Zike Yang 于2023年9月6日周三 23:56写道： > > +1 (non-binding) > > BR, > Zike Yang > > On Wed, Sep 6, 2023 at 11:47 PM tison wrote: > > > > +1 (binding) > > > > Trivial with low risk. > > > > Best, > > tison. > > > > > > mattison chao 于2023年9月6日周三 22:50写道： > > > > > +1 (bin

[DISCUSS] PIP-300: Add custom dynamic configuration for plugins

Hi Pulsar Community, Discuss for PIP-300: https://github.com/apache/pulsar/pull/21127 Thanks, Zixuan

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

This idea looks good to me, but we need to format all codebase to avoid conflicts during cherry picking. +1 Asaf Mesika 于2023年8月31日周四 20:39写道： > > Opentelemetry-java employs both spotless for coding style > You run "./gradlew spotlessCheck" and it shows the problems. > You run "./gradlew spotles

Re: [VOTE] PIP-293: Delete config `disableBrokerInterceptors`

+1(non-binding) Thanks, Zixuan guo jiwei 于2023年8月15日周二 16:24写道： > > Hi dev, >There is a config in ServiceConfiguration called > `disableBrokerInterceptors` introduced by #8157 > , it looks to disable the > broker interceptor, but commented for usin

Re: [DISCUSS] About config `disableBrokerInterceptors`

https://github.com/apache/pulsar/pull/8157 introduces the `disableBrokerInterceptors` config and only for the web service, so causes different behaviors between the broker service and the web service. I prefer to delete the `disableBrokerInterceptors` config. If the user uses the broker intercep

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

+1 (non-binding) Thanks, Zixuan 于2023年8月5日周六 21:11写道： > > +1 (binding) > > Best, > Mattison > On 5 Aug 2023 at 20:05 +0800, Yunze Xu , wrote: > > +1 (binding) > > > > Thanks, > > Yunze > > > > On Sat, Aug 5, 2023 at 12:15 PM tison wrote: > > > > > > Hi, > > > > > > I'd like to start a vote thre

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

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 and let pulsar-admin-go and pulsar-client-go depend on it. I prefer this idea. The `go get` d

Re: [ANNOUNCE] Zili Chen (tison) as new PMC member in Apache Pulsar

Congrats, Tison! Best, Zixuan Yan Zhao 于2023年7月22日周六 12:27写道： > > Congrats! > > On 2023/07/21 17:05:04 Michael Marshall wrote: > > Hi Pulsar Community, > > > > The Apache Pulsar Project Management Committee (PMC) has invited Zili Chen > > (https://github.com/tisonkun) as a member of the PMC and

Re: [DISCUSS] Move superuser/tenantAdmin checks to AuthorizationService from AuthorizationProvider

ective of interface implementation, for example, for > `allowTopicOperationAsync`, > we need to determine whether the role is admin or super user in > PulsarAuthorizationProvider, not in AuthorizationService. > > Regards > Jiwei Guo (Tboy) > > > On Fri, Jul 7, 2023 at 5:

[DISCUSS] Move superuser/tenantAdmin checks to AuthorizationService from AuthorizationProvider

Hello everyone, When a role wants to use the resource, the role needs to have resource permissions. The process is to first check whether the role is the superuser or tenant administrator. If yes, operations are allowed. Otherwise, check the policies stored in zk. Right now, we have the Authoriz

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

+1, but we need to remove the pulsar client changes. Thanks, Zixuan Zike Yang 于2023年6月28日周三 16:24写道： > > +1 for cherry-picking the PR. > > Thanks, > Zike Yang > > On Wed, Jun 28, 2023 at 4:22 PM wrote: > > > > Agree with cherry-pick PR. > > > > Best > > Mattison > > On 26 Jun 2023 at 17:10 +080

Re: [DISCUSS] PIP-277: Clusters list API return clusters with local flag

+1, this is a good improvement. In the proposal, I don't suggest you append the `local` to the cluster name: 1. It will be confusing when the original cluster name includes the `local` name 2. In some cases, it is not easy to distinguish between local and remote clusters so I suggest we should a

Re: New pip process reminder

I think we can reference https://www.apache.org/foundation/voting.html > Votes on code modifications follow a different model. In this scenario, a > negative vote constitutes a veto , which the voting group (generally the PMC > of a project) cannot override. Again, this model may be modified by

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

+1 (non-binding) Thanks, Zixuan Enrico Olivelli 于2023年6月6日周二 16:40写道： > > +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) > > > > >

Re: [DISCUSS] Release Pulsar 3.0.1

+1 Thanks, Zixuan Hang Chen 于2023年6月5日周一 09:39写道： > > +1 > > Thanks, > Hang > > PengHui Li 于2023年6月5日周一 09:34写道： > > > > +1 > > > > Thanks for driving the release. > > > > Penghui > > > > On Thu, Jun 1, 2023 at 7:38 PM Zike Yang wrote: > > > > > Hi all, > > > > > > I would like to propose rele

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

+1 Default to enable the TLS hostname verification is important anywhere, which protected our application. Should these changes be released in a minor version? For the Golang client, I think we should introduce a `NewDefaultConfig` method to create the config instead of directly new config. Th

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

> The best solution is to make the build repeatable. IIUC, that will let us build all of the artifacts using CI instead of personal machines, which removes this class of errors. I agree! But I don't know if Apache rules allow this operation, and if so, I recommend using the CI to publish our proje

Re: [ANNOUNCE] Qiang Zhao as new PMC member in Apache Pulsar

Congrats! Thanks, Zixuan 太上玄元道君 于2023年3月30日周四 01:40写道： > Congrats!! > > Thanks, > Tao Jiuming > > > 2023年3月29日 23:51，Devin Bost 写道： > > > > Congrats! > > > > Devin G. Bost > > > > > > On Wed, Mar 29, 2023 at 6:38 AM ZhangJian He wrote: > > > >> Congratulations! > >> > >> Thanks > >> ZhangJian

Re: [VOTE] PIP-250: Add proxyVersion to CommandConnect

+1 (non-binding) Thanks, Zixuan Yunze Xu 于2023年3月13日周一 17:31写道： > +1 (binding) > > Thanks, > Yunze > > On Mon, Mar 13, 2023 at 3:48 PM Zike Yang wrote: > > > > +1 (non-binding) > > > > Thanks > > Zike Yang > > > > On Sat, Mar 11, 2023 at 12:08 PM Yubiao Feng > > wrote: > > > > > > +1 (non-bin

Re: [DISCUSS] PIP-257: Add Open ID Connect Support to Server Components

Hi Michael, +1, Thank you for your PIP! That's important for modern authentication! I have a question: > 2. Implement `KubernetesFunctionAuthProvider` with `KubernetesSecretsAuthProvider`. It looks like we add an authentication provider for the Kubernetes environment. Is the OIDC authentication

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

BC is used for compatibility with old users. Maybe we shouldn't break that. Asaf Mesika 于2023年3月6日周一 20:03写道： > So it means the change is only on the client side, not the broker side? > > > On Fri, Mar 3, 2023 at 11:42 AM Zixuan Liu wrote: > > > Hi all, > >

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

mnative.io> > > > Yu Wei Sung > > Sr. Solutions Engineer > > > streamnative.io > > <http://github.com/streamnative> > <https://www.linkedin.com/company/streamnative/> > <https://twitter.com/streamnativeio/> > > > On Wed

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

> Actually I was expecting that part of the discussion will specify the > difference between using FIPS compared with non-FIPS, in each BouncyCastle > usage: TLS and message encryption. Good catch! I'll check this. Asaf Mesika 于2023年3月1日周三 21:19写道： > On Mon, Feb 27, 2023 at 4

Re: [questions] Which jakartaEE version we plan for pulsar 3.0.0?

IMO, I think we can upgrade to jersey 3.x from jersey 2.x on the `pulsar-admin-client`. Thanks, Zixuan ZhangJian He 于2023年2月28日周二 17:44写道： > ping @Zixuan Liu @Enrico Olivelli > So, I am not sure if we can update to 3.x. Maybe we will need provider two > versions of **pulsar-adm

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

ptions if they don't use specific > algorithms or encryption schemes? > Potentially a breaking change? > You can't switch it off via config? > > On Wed, Feb 22, 2023 at 3:56 PM Zixuan Liu wrote: > > > > 1. What is FIPS? > > > > FIPS (Federal Information P

  1   2   3   >