Re: [DISCUSS] How to handle stale PRs

ne that long without attention the situation >>> isn't likely to change. And the submitter can always reopen it if it's >>> still relevant. >>> >>> On Fri, Dec 3, 2021 at 1:17 PM Dave Fisher wrote: >>> >>>> I think that any Pulsar committer

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

his tweet https://twitter.com/streamnativeio/status/1469366308022013953 from today implies SN wants to control the roadmap. In the Apache Way the project roadmap is discussed on the dev list. If it’s not on the dev list it didn’t happen. Dave > > - Sijie > > > > On Thu, De

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

ake. We already caught it. Dianjin is fixing it. > > - Sijie > >> On Wed, Dec 8, 2021 at 11:41 AM Dave Fisher wrote: >> >> This is great news! >> >> However the ending of the blog post [1] does not follow the Apache Way >> >> This bullet poi

Log4Shell Vulnerability

We should provide updates to secur...@apache.org about our status regarding Log4Shell. Here is the current blog post about impacted projects: https://blogs.apache.org/security/entry/cve-2021-44228 Here is a blog post about Log4j exploits;

Re: Voting time period minimum

che.org/thread/m8dr0hz7qn7rkd48bcp430lcq2q3674g [2] https://lists.apache.org/list?dev@pulsar.apache.org:lte=1y:[VOTE] > > For other activities, this project follows the ASF 72 hours rule. > > - Sijie > > On Mon, Jan 3, 2022 at 8:17 PM Dave Fisher wrote: > >> Yes please! I did not notice that

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

Sent from my iPhone > On Jan 5, 2022, at 8:10 PM, Haiting Jiang wrote: > >  >> CompletableFuture trigger(SystemEventMessage message); > > Maybe `record` make more sense? > >> SystemEventMessageBuilder properties(Map properties); >> >> SystemEventMessageBuilder addProperty(String key,

Re: [DISCUSS] Add icebox label for issues and PRs that have been inactive for more than 4 weeks

> On Jan 12, 2022, at 8:15 AM, PengHui Li wrote: > > Hi Pulsar Community, > > I want to start a discussion about introducing an icebox label that can be > added to > the issue or PR by pulsar bot automatically to help us can focus on the > active PRs > and issue. To avoid missing merge PRs,

[ANNOUNCE] New PMC Member - Lari Hotari

Pulsar PMC Best Regards, Dave Fisher on behalf of the Pulsar PMC

Re: [PR] Update .asf.yaml to protect current release branches

Before the asf-site branch can deleted the people working on the website need to finish the transition of https://github.com/apache/pulsar-site to build the main site and not a staging site. All the best, Dave > On Feb 15, 2022, at 8:55 AM, Michael Marshall wrote: > > Now that

[ANNOUNCE] New Committer: Andrey Yegorov

for CVEs Welcome and Congratulations, Li Li! Please join us in congratulating and welcoming Andrey onboard! Best Regards, Dave Fisher on behalf of the Pulsar PMC

Re: [DISCUSS] Create a nightly docker image

The ASF has a JFrog artifactory instance that could help. Ask on bui...@apache.org! Regards, Dave Sent from my iPhone > On Mar 18, 2022, at 9:53 PM, PengHui Li wrote: > > I think we can use a separate org to maintain the nightly builded snapshot > images? > So that the external repo can

KEYS file update

We have two KEYS files stored on https://dist.apache.org one in the Release directory and one in the Dev directory. Apache Release Distribution Policy (https://infra.apache.org/release-download-pages.html) requires and on the Download page (https://pulsar.apache.org/en/download/) we refer to

Re: [VOTE] Pulsar Release 2.10.0 Candidate 1

Hi - Has anyone else found another breaking issue? Just asking to save Peng Hui time if there is another fix for RC2, All the best, Dave Sent from my iPhone > On Feb 22, 2022, at 8:31 PM, PengHui Li wrote: > > Hi all, > > This PR https://github.com/apache/pulsar/pull/14410 fixes a

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

Hi - I hope I’m understanding what’s being discussed. If we are going to automatically delete tenants and namespaces for not containing topics then we need to make both of these automatic actions configurable with a default to NOT do so. Otherwise we break existing use cases. Automatic

Re: [NOTICE] Pulsar Helm Charts Repo is temporarily down

We can revert the PRs that switched over if necessary and follow with more testing. It’s a trade off. All the best, Dave Sent from my iPhone > On Feb 16, 2022, at 8:54 PM, Sijie Guo wrote: > > Hi everyone, > > Just want to let everyone know that the Pulsar Helm Charts repo is >

Re: Pulsar Helm Chart Repo is broken

Change L74 to pulsar-site Change L76 to asf-site-next All the best, Dave Sent from my iPhone > On Feb 16, 2022, at 9:02 PM, Sijie Guo wrote: > > Yes, we just need to change the CI process in `pulsar-helm-chart` to > publish the index.yaml file to the new website. > > See >

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

While it’s preferred that KEYS are signed it’s not required. The last Apache key signing party was at Apachecon Las Vegas in 2019. Here’s looking forward to the next one. Bring your government ids. Regards, Dave Sent from my iPhone > On Feb 16, 2022, at 6:11 PM, PengHui Li wrote: > > Hi

Re: [VOTE] Pulsar Release 2.8.3 Candidate 1

> On Feb 15, 2022, at 3:59 PM, PengHui Li wrote: > >> I wonder if we should be more willing to share suspicions on the > mailing list when releases are actively being prepared. I would > have appreciated the notice, and I could have possibly helped > confirm the issue. On the other hand, I

Managing Projects Independently

The ASF has a number of resources created from decades of fostering hundreds of software communities in their missions to build amazing software components. One of the committees is the Community Development PMC (ComDev) Please review the following page:

Re: [Guideline] Pulsar PR Naming Convention

Hi - I think that these guidelines are making it hard for new contributors. Our guidelines should make it super easy to make contributions. The guidelines are for contributions. Contributors are the community. Committers will review contributors PRs and can gently fix mistakes for them to show

Fwd: [NOTICE] Introducing GitHub Actions build status notification for git repositories.

Hi - There is a new feature from ASF Infra for GitHub Action notification! ATB, Dave > Begin forwarded message: > > From: Daniel Gruno > Subject: [NOTICE] Introducing GitHub Actions build status notification for > git repositories. > Date: March 26, 2022 at 1:42:54 PM PDT > To:

Fwd: Call for Presentations now open, ApacheCon North America 2022

The Call For Presentations for ApacheCon NA in New Orleans is now open. There will be a Pulsar Event Streaming track. Please consider attending and submitting a talk. This will be an in-person conference only. Further details will come as we get closer to the event. All The Best, Dave >

Re: Pulsar download web page

Please Merge https://github.com/apache/pulsar/pull/14855 and test the website after the build to correct this issue. > On Mar 24, 2022, at 5:10 PM, Private List Moderation > wrote: > > Hi, > > I'm afraid I cannot approve this announcement because the download page has > an issue: > > The

AWS Terraform Deployment - PRs

Hi - I found this PR - https://github.com/apache/pulsar/pull/7887 It does most of the terraform fixes needed to make https://github.com/apache/pulsar/tree/master/deployment/terraform-ansible functional which hasn’t worked since 2.6.0. I would like to merge this PR, but I’m not sure if it

Re: AWS Terraform Deployment - PRs

Sent from my iPhone > On Jan 28, 2022, at 1:26 PM, Dave Fisher wrote: > > Hi - > > I found this PR - https://github.com/apache/pulsar/pull/7887 > > It does most of the terraform fixes needed to make > https://github.com/apache/pulsar/tree/master/deployment/terrafo

Re: [DISCUSS] New repository for website - pulsar-site

Also a new staging branch. From the PR it will be named ‘asf-site-next’ All the best, Dave > > Thanks! > > [1] https://github.com/apache/pulsar-site > [2] > https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#heading=h.n6wibg4w77xk > >> On 2

Re: [DISCUSS] New repository for website - pulsar-site

ithub.com/apache/pulsar-site/blob/ffc2e424a7565584e58c1f5a10bb0b1253497f53/.github/workflows/ci-pulsar-website-next-build.yaml#L78-L79> > > > Thanks, > Li Li > > >> On Jan 21, 2022, at 11:04 AM, Dave Fisher wrote: >> >> Hi Liu Yu, >> >>>> O

Re: [DISCUSS] New repository for website - pulsar-site

Hi Li Li, Please see https://issues.apache.org/jira/browse/INFRA-22778 for further instructions. All the best, Dave > On Jan 20, 2022, at 10:16 PM, Dave Fisher wrote: > > It’s a bit late in my evening. > > You could access the-asf.slack.com #asfinfra and ask about

Re: Voting time period minimum

> On Jan 7, 2022, at 2:59 PM, Matteo Merli wrote: > > On Fri, Jan 7, 2022 at 9:27 AM Dave Fisher wrote: >>> I believe 48 hours vote is only for PIP, which was agreed in the dev@. >> >> I would like to understand why Matteo chose 48 hours for this process. >

Re: [VOTE] Migrate TestNg Assertion to AssertJ

. Changing all the tests is a huge amount of work. All the best, Dave > Thanks,Roc > At 2022-04-07 22:16:40, "Dave Fisher" wrote: >> Hi - >> >>> On Apr 7, 2022, at 6:22 AM, Roc Marshal wrote: >>> >>> Hi Pulsar community, >>> >>

Re: [VOTE] Migrate TestNg Assertion to AssertJ

Hi - > On Apr 7, 2022, at 6:22 AM, Roc Marshal wrote: > > Hi Pulsar community, > > > Start voting for [DISCUSS] Migrate TestNg Assertion to AssertJ . It will > stay open for at least 48 hours. > The discussion thread is >

[NEXT STEPS] Pulsar Release 2.10.0 Candidate 5

Hi Peng Hui, Thank you for taking on the very difficult and tedious role of Release Manager. Please feel free to ask for volunteers to help you complete this release. If anyone notices anything Peng Hui has missed please see if you can help! All the Best, Dave Sent from my iPhone > On Mar

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

There has certainly been a lot of discussion on the pip and also the email thread. It was a substantive debate about potential protocol changes. The result doesn’t look conclusive. Where did you land regarding Michael’s ideas? Best, Dave Sent from my iPhone > On Sep 5, 2023, at 11:56 AM,

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

-0. I think it will introduce too much change. We have classes that are quite large and having to fix code style after making a small correction seems like a waste of volunteer energy. Best, Dave Sent from my iPhone > On Aug 31, 2023, at 9:05 PM, Zixuan Liu wrote: > > This idea looks good

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

potentially over 5000 files tomorrow. > > Thanks, > sinan > > > Dave Fisher 于2023年9月1日周五 12:19写道： > >> -0. I think it will introduce too much change. We have classes that are >> quite large and having to fix code style after making a small correction >> seems like

Re: Question about Pulsar gRPC client(s)

I think that Christophe suggested the protocol handler approach like KoP (also forked as DataStax Starlight for Kafka). Due to the several people on the PMC contributing to that the performance gains were huge and it nearly as performant as Pulsar. Best, Dave Sent from my iPhone > On Oct 31,

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

My concern is that this pip allows consumers to change the processing rules for transactions in ways that a producer might find unexpected. I think if this proceeds then the scope needs to be expanded to producers/admins needing to proactively allow transactions to be consumed uncommitted. I

Re: [DISCUSS] Release Pulsar 3.0.2

Please use the correct name of the project - Apache Pulsar. Thanks, Dave Sent from my iPhone > On Sep 24, 2023, at 7:08 AM, Yubiao Feng > wrote: > > Hi all > > I would like to propose releasing the Pulsar 3.0.2 > > It's over one month since the release of 3.1.0, and there are 82 new >

Re: [DISCUSS] Release Pulsar 3.1.1

Please use the correct name of the project - Apache Pulsar. Thanks, Dave Sent from my iPhone > On Sep 17, 2023, at 10:32 PM, guo jiwei wrote: > > Hi all, > > I would like to propose releasing the Pulsar 3.1.1. > > It's over one month since the release of 3.1.0 and there are 56 new commits

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

found in the following link: > https://github.com/apache/incubator-paimon/issues/765 > > Sincerely, > Xiangying > >> On Mon, Sep 18, 2023 at 10:30 AM Dave Fisher wrote: >> >> My concern is that this pip allows consumers to change the processing rules >> for

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

e cherry picked to current versions. > > Looking forward to your reply. Thank you, Dave > > Thanks, > Xiangying > >> On Tue, Sep 26, 2023 at 4:09 AM Dave Fisher wrote: >> >> >> >>>> On Sep 20, 2023, at 12:50 AM, Xiangying Meng wrote: >

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

> On Sep 20, 2023, at 12:50 AM, Xiangying Meng wrote: > > Hi, all, > > Let's consider another example: > > **System**: Financial Transaction System > > **Operations**: Large volume of deposit and withdrawal operations, a > small number of transfer operations. > > **Roles**: > > -

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

-1 (binding) I’m not convinced that breaking transaction isolation is the proper course of action. Regards, Dave > On Sep 25, 2023, at 6:46 AM, hzh0425 wrote: > > Hi dev, > This thread is to start a vote for PIP-298 Consumer supports specifying > consumption isolation level > Discuss thread:

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

e. > > Sincerely, > Xiangying > >> On Mon, Sep 18, 2023 at 10:58 PM Dave Fisher wrote: >> >> Thanks. So, this is to support exfiltration of uncommitted transaction data? >> This is IMO wrong and a security risk. >> >> Pulsar already supports

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

Please use the correct name.  “DNS Servers” not “DNSes”.What is a DNS server?cloudflare.comBest,DaveSent from my iPhoneOn Oct 12, 2023, at 8:01 AM, Diego Salvi wrote:Hi Pulsar Community,This is a PIP discussion on how support custom DNSes configuration to beused by the Pulsar Client.This is the

Re: Enable GitHub Discussions?

I asked Infra. GitHub Discussions are not synchronized into ASF Infrastructure's GitBox. That means that there is not ability to change the notification scheme to send to a mailing list. Technically we can go down this path only if it is possible to set a notification within GitHub. You would

Re: Enable GitHub Discussions?

scuss that. All The Best, Dave [3] http://theapacheway.com/consensus/ > > Then we can ask Infra to do the needed GitHub Admin tasks if we reach a > consensus on enabling it, thank you! > > [1] http://theapacheway.com/on-list/ > > Anonymitaet > > On Fri, Apr 22, 2

Re: [VOTE] PIP-156: Build and Run Pulsar Server on Java 17

This is close and much work is done. +1. > On Apr 20, 2022, at 9:37 AM, Heesung Sohn > wrote: > > Dear Pulsar Community, > > Please review and vote on this PIP. > > PIP link : https://github.com/apache/pulsar/issues/15207 > > Thank you, > -- > > > > Heesung Sohn

Re: JDK 17 runtime compatibility

Bumping this thread so it’s current. > On Feb 14, 2022, at 6:09 AM, Christophe Bornet wrote: > > Big +1 > > Le lun. 14 févr. 2022 à 14:54, Nicolò Boschi a > écrit : > >> Dear Pulsar community, >> >> >> I would like to start a discussion about having a plan to make Pulsar >>

{CHERRY-PICK concerns] Re: [pulsar] branch master updated: [improve][broker] Tidy up the system topic. (#15252)

I am not saying we need to cherry pick this change. I want to note that this seemingly small change does touch a large number of files with 44 changed. Changing that many files may impact future changes that will need to be cherry picked. Those cherry picks of future PRs to 2.8.4, 2.9.3, and

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

In addition those who don’t like the light blue background have the dark option of a black background. Sent from my iPhone > On May 12, 2022, at 8:33 PM, Dave Fisher wrote: > > Hi - > > The two most important issues are search and translations. I’d like to know > when t

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

Hi - The two most important issues are search and translations. I’d like to know when these will be fixed. Also, I’ve been trying google as an alternative to our broken search and it is giving me ancient docs instead of latest. IMO - These graphical issues are comparatively trivial. That and

About 2.10.1, 2.9.2, 2.8.4 has this been cherry picked yet? [fix][java-client] Fix performance regression with message listener

This is a fix for a severe performance regression and I wanted to be sure that it gets cherry picked. > On May 31, 2022, at 6:48 PM, GitBox wrote: > > > dave2wave commented on PR #15162: > URL: https://github.com/apache/pulsar/pull/15162#issuecomment-1143028123 > > Has this been cherry

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

s/C02Q4JLUB38/p1649233950692869 < >> https://apache-pulsar.slack.com/archives/C02Q4JLUB38/p1649233950692869> >> >> Anyway, May need cckell...@gmail.com to help with this >> >> >>> On May 13, 2022, at 11:33 AM, Dave Fisher wrote: >>> >>> Hi

Re: [DISCUSS] Apache Pulsar 2.10.1 release

There are some PRs that are coming in that must be included. Thanks, Dave > On May 23, 2022, at 9:59 PM, Yunze Xu wrote: > > +1 > > Thanks, > Yunze > > > > >> 2022年5月23日 11:34，Hang Chen 写道： >> >> +1 >> >> There are a lot of transaction fixes. >> >> Thanks, >> Hang >> >> PengHui Li

Re: [DISCUSS] Apache Pulsar 2.9.3 release

There are some PRs that are coming in that must be included. Thanks, 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 > wrote: > >> Hello, Pulsar community: >> >> I'd like to propose to release Apache

Re: Any sign of 2.8.4?

Hi Frank, We need a Pulsar Committer to step up to be the Release Manager. Regards, Dave > On Jun 24, 2022, at 1:05 PM, Frank Kelly wrote: > > Hi All, >Last email I saw of a 2.8.4 release was May 31st is there still a > possibility or are folks working on 2.9.3 and upwards? > > Thanks! >

Re: Trademark listing?

Hi Patrick, Pulsar is a trademark of the ASF.. It is not registered. Please use the ™ as appropriate. All The Best, Dave > On Jul 4, 2022, at 10:24 AM, Patrick McFadin wrote: > > Hi all, > > I was working with my publisher on an upcoming book project I'm working on > and found something I

Re: [VOTE] PIP-181: Pulsar Shell

+1 (binding) Sent from my iPhone > On Jul 4, 2022, at 7:46 AM, 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.

[DISCUSSION] Improvements to Release Process Management

Hi - We need to tighten up our procedures around releases. There are several issues. 1. Maintaining the official KEYS file - https://dist.apache.org/repos/dist/release/pulsar/KEYS During the pulsar-manager-0.3.0 release the KEYS were not updated from

Re: [DISCUSS] Enable GitHub Discussions?

-list-moderation.html I already moderate a large number of mailing lists. Mostly you will simply ignore some regular spammy phishing attacks. Regards, Dave > On Jun 28, 2022, at 9:13 AM, Dave Fisher wrote: > > Hi - > > Now that the ASF has a notifier on GitHub Discussions I ha

Re: [VOTE] Pulsar Release 2.10.1 Candidate 1

Hi - The Release Manager can vote. Shouldn’t you? Best Regards, Dave Sent from my iPhone > On Jun 26, 2022, at 5:51 PM, PengHui Li wrote: > > Hi all, > > Thanks for all your verification for 2.10.1 > > We currently have 2 (+1) bindings and 5 (+1) non-bindings. > We need one more (+1)

Re: [DISCUSS] Enable GitHub Discussions?

Hi - Now that the ASF has a notifier on GitHub Discussions I have no objection to using discussions as long as these are visible on dev@pulsar.apache.org mailing list. > From the previous thread it seems that the Pulsar community has already > multiple channels

Re: Trademark listing?

missing from the ASF trademark page is that just an > email to trademark@ or is that something the PMC needs to do? The Pulsar > homepage should be updated as well. > > Patrick > > On Tue, Jul 5, 2022 at 4:15 PM Dave Fisher wrote: > >> Hi Patrick, >> >> Pulsar

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

On Jun 21, 2022, at 1:00 AM, Haiting Jiang wrote: > > Hi Pulsar community: > > I open a pip to discuss "Shadow Topic, an alternative way to support readonly > topic ownership." > > Proposal Link: https://github.com/apache/pulsar/issues/16153 > > --- > > ## Motivation > > The motivation

Re: [DISCUSS] PIP-175: Extend time based release process

> On Jun 8, 2022, at 11:44 AM, Matteo Merli wrote: > > On Tue, Jun 7, 2022 at 10:14 PM PengHui Li wrote: >> >> I'm not sure I fully understand the LTS release and feature release. >> >>> The LTS releases will be identified by being a `.0` version. For example: >>> * `3.0` -> LTS >>> *

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. All The Best, Dave Sent from my iPhone > On Jun 7, 2022, at 7:25 AM, Zhengxin Cai wrote: > > Thanks for bringing this up. > I think building a separate

Re: [DISCUSS] Apache Pulsar 2.10.1 release

Please proceed with preparing the 2.10.1 release. > On May 24, 2022, at 1:17 PM, Dave Fisher wrote: > > There are some PRs that are coming in that must be included. > > Thanks, > Dave > >> On May 23, 2022, at 9:59 PM, Yunze Xu wrote: >> >> +1 >>

Re: [DISCUSS] Apache Pulsar 2.9.3 release

> On Jun 2, 2022, at 11:55 PM, mattison chao wrote: > > Hi Dave Fisher, > >> There are some PRs that are coming in that must be included. > > How's the progress on these PRs? They are merged. Regards, Dave > > Best, > Mattison > > On Wed, 25

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

Changes to admin permissions are decisions that require some discussion on dev@pulsar. Regards, Dave > On Jun 9, 2022, at 5:11 AM, techno...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > technoboy pushed a commit to branch master > in repository

Re: [DISCUSS] PIP-175: Extend time based release process

Hi - Interesting, some responses inline. > On Jun 7, 2022, at 3:25 PM, Matteo Merli wrote: > > https://github.com/apache/pulsar/issues/15966 > > > > ## Motivation > > In PIP-47 > (https://github.com/apache/pulsar/wiki/PIP-47:-Time-Based-Release-Plan), > we have adopted a

Re: Pulsar Documentation Guides

Hi Yu, I have a request. Please make these guides part of the website and on project managed resources. Thank you, Dave Sent from my iPhone > On Jun 13, 2022, at 9:04 AM, Yu wrote: > >  > Hi team, > > This is a soft reminder: > > If you make contributions to Pulsar documentation, please

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

+1 (binding) I support this enhancement for when a user occasionally requires accurate backlog stats. Once we bring this into service we can see if further guardrails are required. Regards, Dave > On Jul 19, 2022, at 10:02 AM, Enrico Olivelli wrote: > > This is the VOTE thread for PIP-187 >

Re: [RESULT][VOTE] Enable GitHub Discussion for user-facing discussion

Hi - Discussions is now enabled at https://github.com/apache/pulsar/discussions We will see discussions activity on dev@pulsar. Once we begin to see how much activity, etc. then we can discuss if the email should go to users@ or a new discussions@ mailing list. Someone should start a

A note from your list moderator - please subscribe

Hi - Just a note that you will get your emails onto the list much faster if you subscribe to the list by sending an email to dev-suscr...@pulsar.apacche.org and responding to the confirmation email. If you don’t subscribe then you have to wait for a moderator to approve the email and that

Re: [VOTE] Enable GitHub Discussion for user-facing discussion

+1 - thanks. Emails will go to dev@pulsar initially. We should have a separate discussion about notifications since these are set on a repository by repository basis. > On Jul 12, 2022, at 4:04 AM, Yu wrote: > > Hi tison, thanks for creating this vote! > I thought we reached a lay consensus

Re: [DISCUSS] Apache Pulsar 2.8.4 release

Thank you for volunteering! > On Jul 21, 2022, at 12:57 AM, Yunze Xu wrote: > > Hello Pulsar Community, > > It has been several months since the 2.8.3 release and there are many > important fixes after that. For example, there is a performance > regression for message listener that was

Re: [VOTE] PIP-174: Provide new implementation for broker dispatch cache

Sorry I’m late to this discussion. I think that the motivation is correct. There is really quite a bit of activity around this issue. Let’s take extra efforts to engage extra time with commits to confirm performance improvements. Let’s particularly pay attention to threading. +1 Regards,

Re: svn commit: r55993 - /release/pulsar/KEYS

Thank you! Sent from my iPhone > On Jul 27, 2022, at 5:01 AM, peng...@apache.org wrote: > > Author: penghui > Date: Wed Jul 27 09:01:00 2022 > New Revision: 55993 > > Log: > Added gpg key for jianghaiting > > Modified: >release/pulsar/KEYS > > Modified: release/pulsar/KEYS >

Re: [ANNOUNCE] Micheal Marshall as a new PMC member in Pulsar

Congratulations! Well deserved! > On Jul 26, 2022, at 11:21 AM, Enrico Olivelli wrote: > > I am glad to announce that the Apache Pulsar PMC invited Micheal to > join the PMC and he accepted. > > Micheal is doing a great job in stewarding our community > > Please join me and celebrate ! > >

Re: [DISCUSS] PIP-155: Drop support for Python2

+1 Sent from my iPhone > On Apr 16, 2022, at 11:15 AM, Matteo Merli wrote: > > Adding a bit on which Python versions to support, I found this very > helpful: https://endoflife.date/python > > Basically 3.5 and 3.6 releases have already reached end-of-life as > well and there will be no more

Re: New Pulsar Website is Live!

You’re welcome Mellissa! Thanks to everyone who made this change possible! Sent from my iPhone > On May 11, 2022, at 8:33 AM, Melissa Logan wrote: > > Excited to see it go live! Thank you to all collaborators including Yu, > Lili, Paul, Dawn, Dave D, Dave F, Jun, Julia and everyone who

Re: Build Pulsar Server on Java 17- too strict ?

> On May 11, 2022, at 6:39 AM, Matteo Merli wrote: > > On Wed, May 11, 2022 at 1:10 AM Enrico Olivelli wrote: >> I am sorry, I missed this discussion. >> But until we cut a release we are in time to change our minds, if we >> find out that we can do better. > > Yes, but the precise point of

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

+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://github.com/apache/pulsar/issues/16739 and > the discussion thread at >

Re: [DISCUSS] Does stale bot make value for you?

Perhaps 30 days is too quick? 90 days might be better. Also in cases like this one it’s likely that a PR would get more discussion. The other aspect is it would be helpful if many Pulsar committers would spend effort every few weeks reviewing issues and PRs to engage the community. All the

Re: [Discuss][PIP-164] Support split bundle by flow or qps

While not a comment about this proposal I have a comment another split bundle concept. Manually split out a topic into its own bundle. Say a bundle is 0x to 0x0200 with 5 topics. t1 at 0x0010 t2 at 0x0030 t3 at 0x0110 t4 at 0x0123 t5 at 0x01AE Let’s split out

Re: [DISCUSS] Move PIPs to the codebase?

> On Aug 18, 2022, at 8:27 AM, PengHui Li wrote: > > Hi all, > > Currently, the new proposal will be added to the issue list and then shared > link in the email > to request the proposal review. It's really hard to review a long proposal > if you want to comment > in detail. > > Here is an

Re: [Discussion] PIP 78: Replace brodocs with docsify?

y 1, 2023. >> Matteo is being considered to replace it. >> >> [1] https://github.com/apache/pulsar/issues/15664 >> >> Yu and signormercurio >> >> >> >> >> >> >>> On Thu, Aug 18, 2022 at 9:46 PM Dave Fisher wrote: >>> &

Re: [DISCUSS] Move PIPs to the codebase?

> On Aug 23, 2022, at 10:22 AM, Rajan Dhabalia wrote: > > Hi, > I think we can move all the PIPs to the codebase and the new proposal > and proposal without any reviews should happen with a PR first. So that we > can review and comment easily. > > I didn't understand this part. You want

Re: [Discussion] PIP 78: Replace brodocs with docsify?

Sent from my iPhone > On Aug 18, 2022, at 4:55 AM, Yu wrote: > > Hi team, > > To reduce manual work, we’re constantly implementing PIP 78: Generate Docs > from Code Automatically [1]. > > Docs here refer to the following： > - Connector configurations [2] > - Client configurations [3] > -

Re: [VOTE] Pulsar Release 2.7.5 Candidate 3

This is an interesting result. It would be great if the download page after this release is made would indicate JDK versions. Thanks! Dave Sent from my iPhone > On Aug 30, 2022, at 10:46 PM, Michael Marshall wrote: > > Thank you both for verifying it on your end. After debugging this for >

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

Excellent point Rajan! We had a significant decrease in performance with consumption in 2.8.3 which was not fixed until 2.10.1. Let’s take care to solve problems without surprising users and impacting performance. Best, Dave Sent from my iPhone > On Sep 5, 2022, at 5:11 PM, Rajan Dhabalia

Re: Pulsar CI congested, master branch build broken

We are going to need to take actions to fix our problems. See https://issues.apache.org/jira/browse/INFRA-23633?focusedCommentId=17600749=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17600749 Jarek has done a large amount of GitHub Action work with Apache Airflow

Re: [VOTE] [PIP-201] Extensions mechanism for Pulsar Admin CLI tools

+1 (binding) Best, Dave Sent from my iPhone > On Aug 24, 2022, at 12:43 AM, Yunze Xu wrote: > > +1 (non binding) > > Thanks, > Yunze > > > > >> 2022年8月24日 15:38，Nicolò Boschi 写道： >> >> +1 (non binding) >> Nicolò Boschi >> >> >>> Il giorno mer 24 ago 2022 alle ore 09:11 Enrico

Re: [DISCUSS] PIP-209: Separate C++/Python clients to own repositories

+1 (binding) Sent from my iPhone > On Sep 26, 2022, at 2:38 AM, Enrico Olivelli wrote: > > +100 to this ! > > Thanks for this proposal > > Enrico > >> Il giorno lun 26 set 2022 alle ore 10:04 Zike Yang ha >> scritto: >> >> +1. Looks good to me. >> >> Do we need to move the `Apache

Re: [VOTE] PIP-212: Default reppDnsResolverClass to ZkBookieRackAffinityMapping

+1 (binding) > On Oct 20, 2022, at 11:06 PM, Michael Marshall wrote: > > Bump. In my opinion, this is a bug that we need to fix before any new > releases. It is only a PIP because fixing the bug requires updating a > default. > > Thanks, > Michael > > On Fri, Oct 14, 2022 at 1:58 PM Michael

Re: [DISCUSS] PIP-209: Separate C++/Python clients to own repositories

Sent from my iPhone > On Sep 19, 2022, at 7:29 PM, Baodi Shi wrote: > > Hi, @merlimat. Looks good to me. > >> Both C++ and Python clients will continue with their own individual >> versioning. >> >> In order to not break anything or cause more confusion, we would need to use >> a new

Re: [DISCUSS] PIP-209: Separate C++/Python clients to own repositories

Hi - This is great and I agree with the plan except for one missing discussion. The work needs to either include how to create documentation in the new repository and move it to the pulsar-site repository. (This might be better as a new PIP which could also include the go and node clients

Re: [DISCUSS] Archive Crowdin based translation initiative

+1. English only. We need to have multiple volunteers for each language. And we need someone to assure the framework is functional. This should be consider a call to action to those who want translations! Change my mind! Best, Dave Sent from my iPhone > On Sep 22, 2022, at 8:35 PM, tison

Re: [DISCUSS] Planning for Apache Pulsar 3.0

To me the point of this discussion is for the community to discuss both improvement ideas along with current pain points in the broker. Whether or not the ideas and proposed solutions are breaking or incremental is yet to be determined. Let’s not get hung up on versions or nomenclature. All

<    1   2   3   4   >