Re: [VOTE] PIP-218: Consumer batchReceive() single partition every receive

Hi all: Thank you all for voting. I am closing the vote with 3 binding +1 votes (PengHui, Enrico, Haiting) and 1 non-binding +1 vote (Yunze). The implementation pr is : https://github.com/apache/pulsar/pull/18316 Thanks, Bo Enrico Olivelli 于2022年10月28日周五 17:58写道： > > +1 (binding) > > Enrico > >

[GitHub] [pulsar] liuhuagui added a comment to the discussion: Does pulsar delay message support rebooking?

GitHub user liuhuagui added a comment to the discussion: Does pulsar delay message support rebooking? @coderzc Please help to answer🙏 GitHub link: https://github.com/apache/pulsar/discussions/18317#discussioncomment-4044813 This is an automatically sent email for dev@pulsar.apache.org.

[GitHub] [pulsar] liuhuagui edited a discussion: Does pulsar delay message support rebooking?

GitHub user liuhuagui edited a discussion: Does pulsar delay message support rebooking? For example, the previous delay time was changed from 5m to 30m or even 0, even deleted. If not, is there a plan? GitHub link: https://github.com/apache/pulsar/discussions/18317 This is an automat

Re: [DISCUSS] PIP-218: Consumer batchReceive() single partition every receive

Regarding the implementation suggested in the PIP: It said that you will read the messages from all partitions assigned, and once you see a message from a different partition you halt and supply the batch. My question is: Why can't we simply read the messages from one partition (say 10 messages) a

[GitHub] [pulsar] tisonkun added a comment to the discussion: Publish On official page

GitHub user tisonkun added a comment to the discussion: Publish On official page @vinayppsharma I answered the corresponding email. And for this specific question, you may refer to https://pulsar.apache.org/contribute/documentation/contribution GitHub link: https://github.com/apache/pulsar/d

[GitHub] [pulsar] coderzc added a comment to the discussion: Does pulsar delay message support rebooking?

GitHub user coderzc added a comment to the discussion: Does pulsar delay message support rebooking? Pulsar does not support changing the scheduled time of the message that has been sent. No plan for the time being. GitHub link: https://github.com/apache/pulsar/discussions/18317#discussioncom

[GitHub] [pulsar] liuhuagui added a comment to the discussion: Does pulsar delay message support rebooking?

GitHub user liuhuagui added a comment to the discussion: Does pulsar delay message support rebooking? Thanks！ GitHub link: https://github.com/apache/pulsar/discussions/18317#discussioncomment-4045310 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please s

Re: [DISCUSS] PIP-218: Consumer batchReceive() single partition every receive

Good question! It is a scene for our subsequent optimization, and we are implementing it with minimal changes. Asaf Mesika 于2022年11月3日周四 16:49写道： > > Regarding the implementation suggested in the PIP: > > It said that you will read the messages from all partitions assigned, and > once you see a m

[DISCUSS] PIP-222: Add CommandPartitionedTopicMetadata metrics

Hi pulsar community, I’ve opened a PIP to discuss: PIP-222: Add CommandPartitionedTopicMetadata metrics The PIP link: https://github.com/apache/pulsar/issues/18319 Thanks, Tao Jiuming

Re: Releasing current master as Pulsar 2.11.0 ?

PengHui, Il giorno mar 1 nov 2022 alle ore 07:51 PengHui Li ha scritto: > > > As it is, we already need to discuss EOL for 2.7 and 2.8. > > Agree. We should clarify this one. > I think we can stop to provide new releases for 2.7 > and only security or critical bugs for 2.8 (one more official rele

[DISCUSS] Do not grant permission for each partition to reduce unnecessary zk metadata

Hi All, Now when we grant permission on a partitioned-topic, pulsar broker would try to grant permission on each partition. This would result in generating many unnecessary zk metadata and updating zk node repeatedly when granting permission. This problem is shown in https://github.com/apache

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

+1 (binding) I checked the signatures and checksums of the source and convenience binary packages. I did a license check of both and got reasonable results. The NOTICE is fine as well. I reviewed the release notes. Very important highlights, great job! I notice that on release the index.yaml w

Re: [DISCUSS] PIP-215: Configurable Topic Compaction Strategy

Hi Machel, Here are my additional comments regarding your earlier email. - I updated the PIP title to show that this will impact table view as well. - PIP-192 : https://github.com/apache/pulsar/issues/16691 shows the general idea of the states and their actions, and I defined the actual states h

Re: [DISCUSS] PIP-215: Configurable Topic Compaction Strategy

Oops! Michael, I apologize for the typo in your name. On Thu, Nov 3, 2022 at 9:47 AM Heesung Sohn wrote: > Hi Machel, > > Here are my additional comments regarding your earlier email. > > - I updated the PIP title to show that this will impact table view as well. > > - PIP-192 : https://github.c

Re: [DISCUSS] Release Pulsar 2.9.4

+1 Thanks Yubiao On Thu, Nov 3, 2022 at 2:01 PM 丛搏 wrote: > Hello, Pulsar community: > > I'd like to propose releasing Apache Pulsar 2.9.4. It's been about > three months since 2.9.3 was released. > > There are 123 PRs [0] needed to cherry-pick in branch-2.9. I will > cherry-pick these PRs for

CVE-2022-33684: Apache Pulsar: Disabled Certificate Validation for OAuth Client Credential Requests makes C++/Python Clients vulnerable to MITM attack

Severity: high Description: The Apache Pulsar C++ Client does not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when tlsAllowInsecureConnection is disabled via configuration. This vulnerability allows an attacker to perform a man in the midd

Re: [DISCUSS] Release Pulsar 2.9.4

+1 Enrico Il Gio 3 Nov 2022, 18:36 Yubiao Feng ha scritto: > +1 > > Thanks > Yubiao > > On Thu, Nov 3, 2022 at 2:01 PM 丛搏 wrote: > > > Hello, Pulsar community: > > > > I'd like to propose releasing Apache Pulsar 2.9.4. It's been about > > three months since 2.9.3 was released. > > > > There ar

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

The vote to release Apache Pulsar Helm Chart version 3.0.0 based on 3.0.0-candidate-1 is now closed. The vote PASSED with 3 binding "+1", 0 non-binding "+1" and 0 "-1" votes: "+1" Binding votes: - Enrico - Michael - Dave I'll continue with the release process and the release announcement

Re: [DISCUSS] PIP-215: Configurable Topic Compaction Strategy

Hi, I have a different thought about my previous comment. - Agreed with your point that we should merge CompactionStrategy APIs. I updated the interface proposal in the PIP. I replaced `"isValid", "isMergeEnabled", and "merge"` apis with "compact" api. boolean isValid(T prev, T cur) boolean isMe

Re: [DISCUSS] Release Pulsar 2.9.4

+1 Best, Max Xu On Thu, Nov 3, 2022 at 2:01 PM 丛搏 wrote: > Hello, Pulsar community: > > I'd like to propose releasing Apache Pulsar 2.9.4. It's been about > three months since 2.9.3 was released. > > There are 123 PRs [0] needed to cherry-pick in branch-2.9. I will > cherry-pick these PRs for

[DISCUSS] PIP-221: Make TableView support read the non-persistent topic

Hi, pulsar-dev community, I’ve opened a PIP to discuss : PIP-221: Make TableView support read the non-persistent topic. PIP link: https://github.com/apache/pulsar/issues/18229 Thanks, Kai

Re: [DISCUSS] Release Pulsar 2.9.4

+1 Best, Zike Yang On Fri, Nov 4, 2022 at 10:28 AM Max Xu wrote: > > +1 > > Best, > Max Xu > > > On Thu, Nov 3, 2022 at 2:01 PM 丛搏 wrote: > > > Hello, Pulsar community: > > > > I'd like to propose releasing Apache Pulsar 2.9.4. It's been about > > three months since 2.9.3 was released. > > > >

[ANNOUNCE] Apache Pulsar Helm Chart version 3.0.0 Released

Dear Pulsar community, I am pleased to announce that we have released Apache Pulsar Helm chart 3.0.0. It ships with Apache Puslar version 2.10.2, our latest release. The source release, as well as the "binary" Helm Chart release, are available: Official Sources: https://pulsar.apache.org/downloa

Re: [DISCUSS] Release Pulsar 2.9.4

+1 - sounds good to me. Thanks for volunteering to be the release manager Bo. Thanks, Michael On Thu, Nov 3, 2022 at 11:10 PM Zike Yang wrote: > > +1 > > Best, > Zike Yang > > On Fri, Nov 4, 2022 at 10:28 AM Max Xu wrote: > > > > +1 > > > > Best, > > Max Xu > > > > > > On Thu, Nov 3, 2022 at 2:

Re: CVE-2022-33684: Apache Pulsar: Disabled Certificate Validation for OAuth Client Credential Requests makes C++/Python Clients vulnerable to MITM attack

Hi Michael, Thanks for your explanation. I think now we can mark #16064 [1] as the fix to the CVE. In addition, the Apache Node.js client [2] is also based on the C++ client. I'm not familiar with how to install the Node.js client at the moment. It looks like it requires a pre-installation of the

Re: [DISCUSS] PIP-215: Configurable Topic Compaction Strategy

Thank you for your detailed responses, Heesung. > We are not planning to expose this feature to users > soon unless demanded and proven to be stable. In that case, I think we should move forward with this PIP. I have a different opinion about the trade offs for the two designs, but none of my con

Re: Releasing current master as Pulsar 2.11.0 ?

Inline Sent from my iPhone > On Nov 3, 2022, at 6:55 AM, Enrico Olivelli wrote: > > PengHui, > >> Il giorno mar 1 nov 2022 alle ore 07:51 PengHui Li >> ha scritto: >> >>> As it is, we already need to discuss EOL for 2.7 and 2.8. >> >> Agree. We should clarify this one. >> I think we can st

[GitHub] [pulsar] michaeljmarshall added a comment to the discussion: struggling with pulsar functions in kubernetes

GitHub user michaeljmarshall added a comment to the discussion: struggling with pulsar functions in kubernetes @jesumyip - in your function worker config, do you have `brokerClientTrustCertsFilePath` or `tlsTrustCertsFilePath` set? Based on reading through the code, that configuration is used

Re: [DISCUSS] Release Pulsar 2.9.4

+1 Best, Xiaoyu Hou 丛搏 于2022年11月3日周四 14:01写道： > Hello, Pulsar community: > > I'd like to propose releasing Apache Pulsar 2.9.4. It's been about > three months since 2.9.3 was released. > > There are 123 PRs [0] needed to cherry-pick in branch-2.9. I will > cherry-pick these PRs for branch-2.9.

[GitHub] [pulsar] jesumyip added a comment to the discussion: struggling with pulsar functions in kubernetes

GitHub user jesumyip added a comment to the discussion: struggling with pulsar functions in kubernetes @michaeljmarshall Rellly appreciate the reply, Michael. Thank you! So since this is running in a K8S cluster, I assume the function worker config is a configmap? I assume it is this?

[GitHub] [pulsar] jesumyip added a comment to the discussion: struggling with pulsar functions in kubernetes

GitHub user jesumyip added a comment to the discussion: struggling with pulsar functions in kubernetes The real issue for me seems to be - "How do I tell Pulsar so that when it generates the Kubernetes manifest that will deploy the Stateful set which runs the function, it also mounts / inject

[GitHub] [pulsar] jesumyip edited a comment on the discussion: struggling with pulsar functions in kubernetes

GitHub user jesumyip edited a comment on the discussion: struggling with pulsar functions in kubernetes The real issue for me seems to be - "How do I tell Pulsar so that when it generates the Kubernetes manifest that will deploy the Stateful set which runs the function, it also mounts / injec