Re: [DISCUSSION] PIP-120: Enable client memory limit by default

+1 On Fri, 17 Dec 2021 at 13:56, 陳智弘 wrote: > +1 > > Sijie Guo 於 2021年12月17日 週五 12:38 寫道： > > > +1 > > > > On Tue, Dec 14, 2021 at 11:20 AM Matteo Merli wrote: > > > > > https://github.com/apache/pulsar/issues/13306 > > > > > > > > > Pasted below for quoting convenience. > > > > > > > > >

Re: [DISCUSSION] PIP-117: Change Pulsar standalone defaults

+1 On Mon, 20 Dec 2021 at 13:42, Lan Liang wrote: > My two cents +1 , In my case, i sometimes need to run pulsar standalone in > some server with limited resources. > > > > Proposed changes > > The other point i can think of is maybe schema storage also need to change > from using BK to usin

Re: [DISCUSSION] PIP-119: Enable consistent hashing by default on KeyShared dispatcher

+1 On Tue, 21 Dec 2021 at 06:30, Michael Marshall wrote: > +1 > > On Thu, Dec 16, 2021 at 10:37 PM Sijie Guo wrote: > > > > +1 > > > > On Tue, Dec 14, 2021 at 10:15 AM Matteo Merli wrote: > > > > > Pasted below for quoting convenience. > > > > > > > > > > > > > > > ## Motivation > > >

Re: [VOTE] PIP-123: Introduce Pulsar metadata CLI tool

+1 On Wed, 22 Dec 2021 at 07:59, Matteo Merli wrote: > This is the voting thread for PIP-123. It will stay open for at least 48h. > > https://github.com/apache/pulsar/issues/13346 > > > - > ## Motivation > > For a very long time, we have included a CLI command to start the ZooKeeper > sh

Re: [VOTE] PIP-120: Enable client memory limit by default

+1 On Wed, 22 Dec 2021 at 07:46, Matteo Merli wrote: > This is the voting thread for PIP-120. It will stay open for at least 48h. > > https://github.com/apache/pulsar/issues/13306 > > > > ## Motivation > > In Pulsar 2.8, we have introduced a setting to control the amount of memory > use

[ VOTE ] PIP-127: Support Consul metadata.

This is the voting thread for PIP-127,It will stay open for at least 48h. the original issue here : https://github.com/apache/pulsar/issues/13474 ## Motivation In many companies today, Consul is used in microservices to achieve related business requirements. If we can support Consul me

Re: [ANNOUNCE] Apache Pulsar 2.9.1 released

great work! On Fri, 24 Dec 2021 at 19:23, 陳智弘 wrote: > I am really appreciate those contributors and volunteers to make this > release happen! > > Dianjin Wang 於 2021年12月24日 週五 16:43 寫道： > > > Great! Thanks to all the contributors that made this release happen. > > > > Best, > > Dianjin Wang >

Re: [DISCUSSION] PIP-131: Include message header size when check maxMessageSize of non-batch message on the client side.

Hi, @Jason918 I think we can deprecate maxMessageSize to maxPayloadSize, and add maxHeaderSize to limit header size. after then, we can use maxPayloadSize + maxHeaderSize to get maxMessageSize at internal. What do you think about it? > On Dec 31, 2021, at 8:05 PM,

[DISCUSSION] PIP-132: Support Pulsar system event.

Original PIP : https://github.com/apache/pulsar/issues/13628 Pasted bellow for quoting convenience. —— ## Motivation In some case or for better observability. We can support Pulsar event notification mechanism, that can let user subscribe this system topic to receive some **"we need notice t

Re: [DISCUSS] Apache Pulsar 2.9.2 release

+1 regards, Mattisonchao On Wed, 5 Jan 2022 at 23:04, Lan Liang wrote: > +1,Thanks for your work. > > > > > > > Best Regards, > Lan Liang > On 1/5/2022 23:01，Hang Chen wrote： > +1 > > Best, > Hang > > 陳智弘 于2022年1月5日周三 21:30写道： > > +1 > > Lari Hotari 於 2022年1月5日 週三 20:56 寫道： > > +1 > > On Wed,

Re: [DISCUSSION] PIP-132: Support Pulsar system event.

d deserialization if the value type is > Object? > >> - [ ] Producer publish >> - [ ] Message delivered >> - [ ] Message acked > > I think we don't need to record normal message producing and consuming event? > That would make the system topic st

Re: [DISCUSSION] PIP-132: Support Pulsar system event.

onsuming >> event? >> That would make the system topic store too much data. > > These bother me too. Producer and consumers can accomplish the same use cases > in their application logic. > > Any notification mechanism must be very lightweight. What is the implantat

Re: [DISCUSSION] PIP-135: Include MetadataStore backend for Etcd

+1 On Wed, 12 Jan 2022 at 08:09, Matteo Merli wrote: > https://github.com/apache/pulsar/issues/13717 > > - > > ## Motivation > > Since all the pieces that composed the proposal in PIP-45 were finally > merged > and are currently ready for 2.10 release, it is now possible to add other > metad

Re: [VOTE] PIP-121: Pulsar cluster level auto failover on client side

+1 On Wed, 12 Jan 2022 at 09:52, Haiting Jiang wrote: > +1 > > On 2022/01/12 00:09:26 Matteo Merli wrote: > > +1 > > -- > > Matteo Merli > > > > > > On Tue, Jan 11, 2022 at 12:07 PM Neng Lu wrote: > > > > > > +1 (non-binding) > > > > > > On Mon, Jan 10, 2022 at 12:40 AM PengHui Li > wrote: >

Re: [VOTE] PIP-132: Include message header size when check maxMessageSize of non-batch message on the client side.

+1 (non-binding) On Wed, 12 Jan 2022 at 09:59, Zike Yang wrote: > +1 (non-binding) > > On Wed, Jan 12, 2022 at 9:58 AM Haiting Jiang > wrote: > > > > This is the voting thread for PIP-132. It will stay open for at least 48 > hours. > > > > https://github.com/apache/pulsar/issues/13591 > > > >

Re: [Discuss] Create new issues to SDKs in different languages

+1. I agree with Haiting Jiang. The automatic process is a better way to solve this problem. Thanks, Mattison chao

Re: [VOTE] PIP-129: Introduce intermediate state for ledger deletion

+1 (non-binding) Best, Mattison On Fri, 14 Jan 2022 at 11:19, Hang Chen wrote: > +1 (binding) > > Best, > Hang > > Zhanpeng Wu 于2022年1月14日周五 10:37写道： > > > > This is the voting thread for PIP-129. It will stay open for at least 48 > > hours. Pasted below for quoting convenience. > > > >

[DISCUSSION] PIP-137: Add SystemTopicNameManager to manage system topic names.

Original issue : https://github.com/apache/pulsar/issues/13794 Original pull request : https://github.com/apache/pulsar/pull/13813 Pasted below for quoting convenience. --- ## Motivation - The current system topic names are scattered and difficult to maintain and dynamically configure.

Re: [DISCUSS] [Transaction] Clear namespace backlog can't clear system topic and system sub backlog.

HI, Michael Marshall > I am concerned that this design will not scale and that it will be very expensive on installations with many topics. I very much agree with your concern, but currently we already have some topic names to use ``endWith()`` and ``startWith()`` to determine. > It would also i

Re: [VOTE] PIP-124: Create init subscription before sending message to DLQ

+1 (non-binding) > On Jan 25, 2022, at 5:34 PM, Zike Yang wrote: > > Hi Pulsar Community, > > This is the voting thread for PIP-124. It will stay open for at least > 48 hours. Pasted below for quoting convenience. > > Here is the issue for this PIP: https://github.com/apache/pulsar/issues/1340

[DISCUSS] PIP-138: Use NarClassLoaderManager to manage all NarClassLoader.

Hello everyone, I want to start a discussion about PIP-138: Use NarClassLoaderManager to manage all NarClassLoader. This is the PIP document https://github.com/apache/pulsar/issues/13979 Please check it out and feel free to share your thoughts. Best, Mattison

[DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

Hello everyone, I want to start a discussion about PIP-139 : Support Broker send command to real close producer/consumer. This is the PIP document https://github.com/apache/pulsar/issues/13989 Please check it out and feel free to share your thou

Re: [DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

uf exceptions for this feature. > > Thanks, > Michael > > > On Sat, Jan 29, 2022 at 7:25 PM Zike Yang > wrote: >> >> +1 >> >> >> Thanks, >> Zike >> >> On Sat, Jan 29, 2022 at 12:30 PM guo jiwei wrote: >>> &g

Re: [ANNOUNCE] New Committer: Aloys Zhang

Congratulations, Aloys Zhang Best, Mattison > On Feb 10, 2022, at 5:26 PM, Lari Hotari wrote: > > Congratulations Aloys Zhang! > > On Thu, Feb 10, 2022 at 4:46 AM linlin wrote: > >> The Apache Pulsar Project Management Committee (PMC) has invited Aloys >> Zhang >> >> (https://github.com/al

Re: [VOTE] [PIP-143] Support split bundle by specified boundaries

+1 Best Mattison > On Mar 3, 2022, at 11:08 AM, r...@apache.org wrote: > > +1 > > Thanks > Xiaolong Ran > > PengHui Li 于2022年2月27日周日 13:04写道： > >> +1 >> >> Thanks, >> Penghui >> >> On Sat, Feb 26, 2022 at 11:59 AM Haiting Jiang >> wrote: >> >>> +1 >>> >>> Thanks, >>> Haiting >>> >>>

Re: [DISCUSSION][PIP-146] ManagedCursorInfo compression

Great work! I have no other comments other than the compatibility everybody mentioned. Best, Mattison > On Mar 6, 2022, at 4:55 AM, Enrico Olivelli wrote: > > Good proposal. > It is important that this is disabled by default otherwise we cannot easily > support the rollback > > Apart from t

Re: [DISCUSSION][PIP-146] ManagedCursorInfo compression

the ledger, if the user set another configuration ``xxxCompressionType `` we will compress the ledger and cursor. It’s just a question or suggestion. You can feel free to go ahead. Best, Mattison > On Mar 6, 2022, at 8:22 AM, mattison chao wrote: > > > Great work! >

Re: [DISCUSS][Reader] readNext reset message position automatically when enable inclusive

Hi, Zixuan, Very glad you can notice this problem. I am preparing to submit a PIP to resolve this issue. This pip is to add a new field to the CommandSubscribe to let the broker know how to set the cursor position. Feel free to give me more good advice and let me know what you think. Best, Ma

Re: [DISCUSS] PIP-143 : Standardize Admin REST API

+1 Best, Mattison > On Mar 22, 2022, at 9:55 AM, PengHui Li wrote: > > +1 > > Penghui > > On Fri, Mar 18, 2022 at 11:00 AM guo jiwei wrote: > >> Ok, I have updated the proposal number to 149. >> https://github.com/apache/pulsar/issues/14365. >> >> Regards >> Jiwei Guo (Tboy) >> >> >> On

[VOTE] PIP-149: Making the REST Admin API fully async

This is the voting thread for PIP-149. It will stay open for at least 48 hours. https://github.com/apache/pulsar/issues/14365 Pasted below for quoting convenience. - Motivation The Rest API was originally designed to be implemented asynchronously, but with the iteration of functions, some

Re: [VOTE] PIP-149: Making the REST Admin API fully async

nding) > > > > > > > > Enrico > > > > > > > > Il giorno mar 29 mar 2022 alle ore 09:55 PengHui Li > > > > ha scritto: > > > > > > > > > > +1, > > > > > > > > > > Penghui > >

Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

+1(unbinding) Thanks, Mattison On Mon, 11 Apr 2022 at 13:06, Haiting Jiang wrote: > +1 > > Thanks, > Haiting > > On 2022/04/06 08:54:05 Zixuan Liu wrote: > > Hi Pulsar community, > > > > Start voting for PIP-150: https://github.com/apache/pulsar/issues/14883 > > > > Thanks, > > Zixuan > > > > -

Re: [DISCUSS] [PIP-152] Support subscription level dispatch rate limiter setting.

+1 Looks like a very useful feature. Thank you. Best, Mattison On Mon, 11 Apr 2022 at 08:55, PengHui Li wrote: > +1 > > Penghui > > On Sat, Apr 9, 2022 at 4:24 PM Haiting Jiang > wrote: > > > Hi Pulsar community, > > > > I created a PIP to add support for subscription level dispatch rate > >

Re: [DISCUSS] PIP-157: Bucketing topic metadata to allow more topics per namespace

+1 Best, Mattison On Tue, 3 May 2022 at 22:38, Andras Beni wrote: > Hi Enrico, > > I updated the proposal with my answers: > > [The translation from user-visible name to actual storage path] will > happen by supplying the bucket number to > TopicName.getPersistenceNamingEncoding and calculatin

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1 (non-binding) Best, Mattison On Tue, 10 May 2022 at 19:00, Yunze Xu wrote: > +1 (non-binding) > > Thanks, > Yunze >

Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 Best, Mattison On Wed, 11 May 2022 at 13:49, Qiang Zhao wrote: > > > On 2022/04/26 12:07:32 guo jiwei wrote: > > Hi community: > >In PIP-39 > > >, > > we have introduced namespace event to support topic level poli

Re: [VOTE] [PIP-153] Optimize metadataPositions in MLPendingAckStore

+1 (non-binding) Best, Mattison On Thu, 12 May 2022 at 12:15, Ran Gao wrote: > +1 (non-binding) > > Best, > Ran > > On 2022/04/25 06:54:58 一苇以航 wrote: > > Hi Pulsar Community. > > > > This is the voting thread for PIP-153. It will stay open for at least 48 > hours. > > > > The proposal can be f

Re: [VOTE] PIP-157: Bucketing topic metadata to allow more topics per namespace

+1 (non-binding) Best, Mattison On Wed, 18 May 2022 at 15:20, Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il giorno mer 18 mag 2022 alle ore 08:54 Matteo Merli > ha scritto: > > > > +1 > > > > -- > > Matteo Merli > > > > > > On Mon, May 2, 2022 at 6:40 PM Matteo Merli > wrote: > > >

[DISCUSS] Apache Pulsar 2.9.3 release

Hello, Pulsar community: I'd like to propose to release Apache Pulsar 2.9.3 Currently, we have 192 commits [0] and there are many transaction fixes, security fixes. And there are 22 open PRs [1], I will follow them to make sure that the important fixes could be contained in 2.9.3 If you have an

Re: [DISCUSS] [PIP-165] Auto release client useless connections

+1 Best, Mattison On Thu, 26 May 2022 at 15:25, Gavin Gao wrote: > +1 > > > On 2022/05/26 06:31:37 Yubiao Feng wrote: > > I open a pip to discuss Auto release client useless connections, could > you > > help me review > > > > > > ## Motivation > > Currently, the Pulsar client keeps the connecti

Re: [DISCUSS] Apache Pulsar 2.9.3 release

ks, > > Dave > > > > > > > On May 23, 2022, at 4:29 AM, PengHui Li wrote: > > > > > > +1 > > > > > > Thanks > > > Penghui > > > > > > On Mon, May 23, 2022 at 3:31 PM mattison chao < > mattisonc...@apache.org

[DISCUSS] Implementation for HTTP endpoint producer/consumer

Hi, Pulsar Community, We have the PIP-64 that introduces HTTP Rest API for producing/consuming messages( https://github.com/apache/pulsar/wiki/PIP-64%3A-Introduce-REST-endpoints-for-producing%2C-consuming-and-reading-messages ). But this proposal does not define the implementation. However, we al

Re: [DISCUSS] Apache Pulsar 2.9.3 release

Thanks for your update. I will continue to release 2.9.3 Best, Mattison On Sat, 4 Jun 2022 at 04:04, Dave Fisher wrote: > > > On Jun 2, 2022, at 11:55 PM, mattison chao > wrote: > > > > Hi Dave Fisher, > > > >> There are some PRs that are coming in t

Re: [DISCUSS] Implementation for HTTP endpoint producer/consumer

> > I think building a separate HTTP server to serve REST produce/consume > requests might be a good idea, like FunctionWorkerService, users can choose > to run with broker for simplicity or run as a separate component if user > wants isolation and scale independently. Yes, it's a great suggestio

Re: [DISCUSS] Implementation for HTTP endpoint producer/consumer

> > If this is a REST endpoint then call it REST. It is very likely that users > will want to use HTTPS to use it. Calling it HTTP is a misnomer. Very thanks for your correction. Best, Mattison On Thu, 9 Jun 2022 at 15:37, mattison chao wrote: > I think building a separate HT

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

I think it's an addition to the previously missing feature. It makes sense to me. Best, Mattison On Thu, 9 Jun 2022 at 22:24, PengHui Li wrote: > Hi Dave, > > This is a BUG fix. > > The binary protocol allows the produce/consume permission to get the > schema. > But the REST API is not allowed

[DISCUSS] Reject partitioned topic creation when the topic name contains the `partition` keyword.

Hello, everyone. I want to start a discussion about *Reject partitioned topic creation when the topic name contains the `-partition-` keyword.* Please feel free to express your opinion. *Background* We first found this problem two months ago. When the user sets the *allowAutoTopicCreation* polic

Re: [DISCUSS] Reject partitioned topic creation when the topic name contains the `partition` keyword.

I pushed a pull request[1]. That can avoid creating partitioned metadata when the topic local name includes `-partition-` keywords. [1] https://github.com/apache/pulsar/pull/16104

[VOTE] Pulsar Release 2.9.3 Candidate 1

This is the first release candidate for Apache Pulsar, version 2.9.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+ *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note t

Re: [VOTE] PIP-160 Make transactions work more efficiently by aggregation operation for transaction log and pending ack store

+1 (non-binding) Best, Mattison On Thu, 23 Jun 2022 at 09:49, Jia Zhai wrote: > +1 > > On Mon, Jun 20, 2022 at 9:31 AM PengHui Li wrote: > > > +1 (binding) > > > > Left a minor comment here about the field name > > https://github.com/apache/pulsar/issues/15370#issuecomment-1159870170 > > Pleas

Re: [VOTE] Pulsar Release 2.9.3 Candidate 1

9. We can exclude the `io.grpc:grpc-core` in one dependency > > to fix this issue. > > > > Thanks, > > Hang > > > > PengHui Li 于2022年6月27日周一 09:51写道： > > > > > > +1 (binding) > > > > > > - verify gpg signatures > > &

Re: [VOTE] Pulsar Release 2.9.3 Candidate 1

olved and won't block the release. Right? Best, Mattison On Tue, 28 Jun 2022 at 20:21, mattison chao wrote: > @mattison It's better to upload the image under your org first so that we >> can verify the image > > > Sure, I will do it later. > > Best, > Mattis

Re: [DISCUSS] Reject partitioned topic creation when the topic name contains the `partition` keyword.

I hope everyone can express their views. :) Best, Mattison

Re: [DISCUSS] Releasing Pulsar-client-go 0.9.0

+1 On Wed, 29 Jun 2022 at 15:44, PengHui Li wrote: > +1 > On Jun 29, 2022, 14:08 +0800, Zixuan Liu , wrote: > > +1 > > > > On 2022/06/29 06:06:01 Rui Fu wrote: > > > Hello Everyone: > > > > > > I hope you’ve all been doing well. In the past couple of months, we > have fixed many bugs and added s

Re: [VOTE] Pulsar Release 2.9.3 Candidate 1

-79132930a35ec093ac428567bcbaf406baac9daa84009699ed00e7968bc84e48?context=repo On Tue, 28 Jun 2022 at 20:23, mattison chao wrote: > I found one problem with this candidate. >> - When I import `pulsar-broker` and `managed-ledger` into my >> project, I found the project build failed with the following >>

Re: [VOTE] [PIP-179] Support the admin API to check unknown request parameters

+1(non-binding) Best, Mattison On Thu, 30 Jun 2022 at 12:35, Michael Marshall wrote: > +1 > > - Michael > > On Wed, Jun 29, 2022 at 9:29 PM Qiang Huang > wrote: > > > > +1 > > > > Yubiao Feng 于2022年6月30日周四 00:40写道： > > > > > Hi Pulsar Community > > > > > > I would like to start a VOTE on "Sup

Re: [VOTE] PIP-181: Pulsar Shell

+1(non-binding) > On Jul 4, 2022, at 10:45 PM, Nicolò Boschi wrote: > > Dear Community, > > I would like to start a VOTE on "PIP-181: Pulsar Shell" > > The proposal can be read at [0] and the discussion thread is available at > [1]. > Voting will stay open for at least 48h. > > [0] https://gi

Re: [VOTE] Pulsar Release 2.9.3 Candidate 1

gt; >> Mattison, >> There are bad files, pom.xml.versionsBackup, inside the source tarball >> >> I believe that this is a problem >> How did you build the release candidate ? >> >> the source tarball should not contain temporary Maven files >> >

[VOTE] Pulsar Release 2.9.3 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.9.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+ *** Please download

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

gt; docker image to verify the integration of many components using the > DataStax Pulsar Helm Chart > > Thank you for managing the release Mattison Chao! > > Thanks, > Michael > > > > > > On Wed, Jul 13, 2022 at 10:12 PM guo jiwei wrote: > > > > +1 (n

Re: PIP-187 Add API to analyse a subscription backlog and provide a accurate value

+1, This feature is very useful for users. Best, Mattison On Mon, 18 Jul 2022 at 18:11, Nicolò Boschi wrote: > +1, good work, I think it's very valuable for users for monitoring > purposes. > > Nicolò Boschi > > > Il giorno lun 18 lug 2022 alle ore 11:47 Lothruin Mirwen < > lothruin.mir...@gmai

[ANNOUNCE] Apache Pulsar 2.9.3 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.3. 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: [DISCUSS] Apache Pulsar 2.8.4 release

Thanks for your work! Best, Mattison On Fri, 22 Jul 2022 at 11:34, Yunze Xu wrote: > > Sure, I will take it carefully for those PRs not cherry-picked to branch-2.8 > but labeled > as `release/2.8.4`. > > Thanks, > Yunze > > > > > > 2022年7月22日 00:09，Dave Fisher 写道： > > > > Thank you for volunte

Re: [VOTE]PIP-189: No batching if only one message in batch.

+1(non-binding) Best, Mattison On Mon, 25 Jul 2022 at 10:35, Haiting Jiang wrote: > > +1 > Thanks, > Haiting > > On 2022/07/25 02:23:20 Anon Hxy wrote: > > Dear Community, > > > > I would like to start a VOTE on "PIP-189: No batching if only one message > > in batch." > > > > The proposal can be

Re: [VOTE] PIP-187 Add API to analyze a subscription backlog and provide a accurate value

+1 Best, Mattison On Sun, 24 Jul 2022 at 14:51, Haiting Jiang wrote: > > +1 > > Thanks, > Haiting > > On 2022/07/23 02:00:32 PengHui Li wrote: > > +1 > > > > Penghui > > > > On Wed, Jul 20, 2022 at 9:41 PM Asaf Mesika wrote: > > > > > Sorry to barge in the vote - I forgot to send my reply on th

Re: [VOTE] PIP-184: Topic specific consumer priorityLevel

+1(non-binding) Best, Mattison On Mon, 25 Jul 2022 at 13:19, guo jiwei wrote: > > +1 > > Regards > Jiwei Guo (Tboy) > > > On Mon, Jul 18, 2022 at 10:54 AM PengHui Li wrote: > > > +1 > > > > Penghui > > > > On Mon, Jul 18, 2022 at 10:15 AM Zike Yang wrote: > > > > > +1 > > > > > > Thanks > > >

Re: [VOTE] PIP-193 : Sink preprocessing Function

+1 (non-binding) Best, Mattison On Tue, 2 Aug 2022 at 01:56, Dave Fisher wrote: > > +1 (binding) > > On 2022/07/28 10:39:35 Christophe Bornet wrote: > > Hi, Pulsar community, > > > > I'd like to start a vote on PIP-193 : Sink preprocessing Function > > > > You can find the proposal at https://gi

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

+1(non-binding) Best, Mattison On Thu, 4 Aug 2022 at 22:11, Lin Lin wrote: > > +1 (binding) >

Re: [Vote] PIP-192 New Pulsar Broker Load Balancer

+1 (non-binding) Best, Mattison On Wed, 3 Aug 2022 at 15:18, PengHui Li wrote: > > +1 > > Penghui > > On Tue, Aug 2, 2022 at 8:50 AM Heesung Sohn > wrote: > > > Dear Pulsar Community, > > > > Please review and vote on this PIP. > > > > PIP link: https://github.com/apache/pulsar/issues/16691 > >

[DISCUSS] Support `brokerMaxConnectionsPerIp` on Pulsar proxy

Hi, All Pulsar has the `brokerMaxConnectionsPerIp` configuration at the broker, we can use it to limit the maximum connections per IP. The original motivation and PR here: https://github.com/apache/pulsar/pull/10754 IMO, we can also apply it to pulsar-proxy, because when a large number of proxy

Re: [DISCUSS] Skip unnecessary tests when there are only cpp/python related changes

I support it. +1 Best, Mattison On Tue, 16 Aug 2022 at 17:33, Enrico Olivelli wrote: > > +1 > > Enrico > > Il giorno mar 16 ago 2022 alle ore 11:32 Nicolò Boschi > ha scritto: > > > > A big +1 for this! > > > > Nicolò Boschi > > > > > > Il giorno dom 14 ago 2022 alle ore 06:20 Qiang Huang < > >

Re: [DISCUSS] Pulsar 3.0 brainstorming: Going beyond PIP-45 Pluggable metadata interface

Hi, Lari Thanks for you start this discussion. 1) Metadata consistency from user's point of view > - Summarized well in this great analysis and comment [1] by Zac Bentley >"Ideally, the resolution of all of these issues would be the same: a > management API operation--any operation--should n

Re: [ANNOUNCE] Jiwei Guo as a new PMC member in Pulsar

Congratulations! Best, Mattison On Thu, 18 Aug 2022 at 21:03, tison wrote: > Congratulations! > > Best, > tison. > > > Nicolò Boschi 于2022年8月18日周四 20:36写道： > > > Congratulations! > > > > Nicolò Boschi > > > > > > Il giorno gio 18 ago 2022 alle ore 14:15 Anon Hxy > ha > > scritto: > > > > > Co

Re: Enable "Update branch" Github button in pull requests

+1, I think it's useful. Best, Mattison On Thu, 18 Aug 2022 at 14:12, Nicolò Boschi wrote: > Any comments? > Nicolò Boschi > > > Il giorno mar 12 lug 2022 alle ore 18:06 Nicolò Boschi < > boschi1...@gmail.com> > ha scritto: > > > Hi all, > > > > I'd like to propose to enable the Github button "

Re: [DISCUSS] Enable message deduplication for replicator by default

+1 Best, Mattison On Fri, 19 Aug 2022 at 01:40, Enrico Olivelli wrote: > I agree > > Enrico > > Il Gio 18 Ago 2022, 18:23 PengHui Li ha scritto: > > > Hi all, > > > > When I tried to fix a problem related to replicator > > https://github.com/apache/pulsar/pull/17154 > > It surprised me that th

[DISCUSS] Make `Pulsar CI / CI - Unit - Brokers - Flaky` test group to be required

Hi all Recently, some tests in the `broker-flaky` test group always failed, but since it doesn't block CI, no one cared for a long time. This behaviour causes some test scenarios to go unchecked and risk introducing some regressions, and I think we need to make this test group set required. e.g.

Re: [DISCUSS] Use Github project to track the multi clients development

+1 Best, Mattison On Mon, 22 Aug 2022 at 15:52, Baodi Shi wrote: > Nice idea! > > Thanks, > Baodi Shi > > > On Aug 22, 2022, at 12:4250, Zike Yang wrote: > > > > Hi, all > > > > Currently, many features or bug fixes of some clients like the C++ > > client and Python client have not caught up w

Re: Revote: Pulsar website concepts

+1 for Option 1, but I think we need to increase the background colour contrast.

Re: [DISCUSS] Replace Customized Map with ConcurrentHashMap

Hi, Guys. IMO, It's a data structure difference. We can give the benchmark of two structures in different situations (pulsar using situations). > 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

Re: [DISCUSS] Replace Customized Map with ConcurrentHashMap

> Moreover, this process should not consume excessive time. Simply initiate > the script, await the deployment, and execute the test. I have personally > performed this procedure numerous times with success. :) That will be cool. Looking forward to it. btw, I am not sure if I remember correctly. D

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

+1 (binding) Best, Mattison On 6 Sep 2023 at 22:37 +0800, PengHui Li , wrote: > +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 jiwe

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

Hello, folks. I hope this email finds you well. I would like to start a discussion about PIP-296 Support storing broker internal client certificates in metadata store[1]. Please don't hesitate to leave any concerns or questions. Best, Mattison [1] https://github.com/apache/pulsar/pull/21044/

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

gt; if we can provide interface and API to make it pluggable and let users > manage their own implementation without introducing such critical > complexities in Pulsar. > > Thanks, > Rajan > > On Fri, Sep 8, 2023 at 1:21 AM mattison chao wrote: > > > > > Hello, f

Re: [VOTE] Pulsar DotPulsar Release 3.0.0 Candidate 1

+1 (binding) • Checked signature and checksums • Built the client from the source • Ran basic example. Best, Mattison On 8 Sep 2023 at 17:57 +0800, tison , wrote: > +1 (binding) > > I checked > > - Signature and checksums match > - Build the client from the source > - Run examples > > Best, > ti

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

+1 (binding) Best, Mattison On 18 Sep 2023 at 09:19 +0800, PengHui Li , wrote: > +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 th

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

HI, Zixuan Thanks for your discussion. It's a great feature.  But I've got several questions I want to discuss here. 1. When you want to cherry-pick a PR, it should be cherry-picked for all branches after the target branch. Isn't it? 2. I've got a slight concern about cherry-picking. Do you hav

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

+1 (binding) Best, Mattison On 19 Sep 2023 at 20:48 +0800, PengHui Li , wrote: > +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: > > >

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

+1 (binding) Best, Mattison On 20 Sep 2023 at 08:40 +0800, PengHui Li , wrote: > 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 wa

Re: [DISCUSS] Release Pulsar 3.1.1

+1 Best, Matt On 24 Sep 2023 at 21:05 +0800, PengHui Li , wrote: > +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 co

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

ncern about cherry-picking. Do you have any issue or > > feature request in the community that can demonstrate this feature is > > required to cherry-pick? > > This is a feature I need. If cherry-pick is not allowed, then it will > only be kept in 3.2+. > >

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

+1(binding) Best, Mattison On 26 Sep 2023 at 10:54 +0800, Zixuan Liu , wrote: > 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: [VOTE] PIP-302 Introduce refreshAsync API for TableView

+1(binding) Best, Mattison On 8 Oct 2023 at 14:49 +0800, Yunze Xu , wrote: > Totally I'm +0 at the moment. I'm still wondering which issue you > really want to resolve. I left a comment > https://github.com/apache/pulsar/pull/21271#issuecomment-1751899833. > Generally you can get latest value unle

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

+1(binding) Best, Mattison On 11 Oct 2023 at 10:45 +0800, guo jiwei , wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Mon, Oct 9, 2023 at 8:14 AM PengHui Li wrote: > > > +1 (binding) > > > > Left to minor comments on the proposal, PTAL. > > > > Thanks, > > Penghui > > > > On Thu,

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

Hi, Lari > Do you think we can target the switch from Java 17 to Java 21 for the Pulsar > 3.2 release? I think we should consider some things: 1. What are the significant benefits of upgrading? 2. We should define some rules for using the new feature by JDK21 before upgrading. Especially for

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

Pulsar server side > components > > I hope we could continue the discussion and come up with some consensus about > the coarse timelines. The time horizon could be in multiple years if that's > what makes sense. > Oracle's Java 17 LTS premier support ends in Sep 2026,

Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks for your contribution. Best, Mattison > On 19 Oct 2023, at 11:23, PengHui Li wrote: > > +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 releas

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

+1 Best, Mattison > On 19 Oct 2023, at 11:38, Yubiao Feng > wrote: > > Hi @Jiwei > > +1 > It is a good feature, I think it will help users. > > Thanks > Yubiao Feng > > > On Wed, Oct 18, 2023 at 8:45 PM guo jiwei wrote: > >> Hi dev, >> Currently WebSocket only supports the consumption

Re: [VOTE] Pulsar Release 3.1.1 Candidate 1

+1 (binding) - Built from source code. (Java version: 17.0.8.1, Apache Maven 3.9.4, OS name: "mac os x", version: "13.4.1", arch: "x86_64") - Checked binary license - Started Standalone - Ran a round of publish and consume Best, Mattison > On 7 Oct 2023, at 09:09, guo jiwei wrote: > > This i

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

+1(binding) Best, Mattison > On 19 Oct 2023, at 20:47, guo jiwei wrote: > > 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 patter

Re: [DISSCUSS] Don't retain null-key messages during topic compaction

Hi, Cong IMO, Please do not break the previous directly. We can migrate it smoothly. We can add a configuration and give the Timeline of making this configuration default and removing it in the next release version. For example: - Add configuration: `compactionRemainNullKey=true` by default (

  1   2   >