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

Hi Matteo, > On Feb 3, 2024, at 3:25 PM, Matteo Merli wrote: > > Hi Dave, > > Thanks for the feedback, replies inline. > > > On Sat, Feb 3, 2024 at 11:23 AM Dave Fisher wrote: > >> Hi - >> >> What? A cascade of agreement without questions? Se

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

Hi - What? A cascade of agreement without questions? Seems like this has been discussed elsewhere? I have concerns since with this PIP we are making changes to support a third party library. 1. Have people read the PIP text? I see some typos which could be fixed. Simple things nothing

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 6, 2024, at 2:31 AM, Enrico Olivelli wrote: > > Kalwit, > All the committers are invited by the PMC, you can reach out to > priv...@pulsar.apache.org if you have any problems. > > Being a committer is not only about doing code contributions, but also > talking care of the project and

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 6, 2024, at 4:50 AM, Lari Hotari wrote: > > Hi Kalwit, > > In Apache Pulsar, as in any other Apache project, everyone is equal > regardless of their committer or PMC status. All project participants > are free to express their opinions, and, where appropriate, have the > community

[DISCUSS] Community Meeting Notes Are Missing

Hi - I see from the last meeting the following agenda: > 2024/02/29 > Attendees: > Lari Hotari > Jonas > Kevin Lu > Frank Kelly > Asaf Mesika > Chris Bono > David Jensen > > Agenda > PIP-341: Pluggable client metrics tracker interface > 1. Should the OTel implementation be included in the PIP,

Re: [DISCUSS] Community Meeting Notes Are Missing

, really help. Best, Dave > On Mar 6, 2024, at 10:44 AM, Matteo Merli wrote: > > Hi Dave, > > The meeting is being conducted in the same exact way as it was when you > we’re participating in it. > > > -- > Matteo Merli > > > > On Wed, Mar 6, 20

[HOW TO FOLLOW GITHUB] Re: [PR] WIP: PIP-342: OTel client metrics support [pulsar]

For anyone who wishes to watch activity from with a Pulsar GitHub repository please consider subscribing to comm...@pulsar.apache.org by sending an email to commits-subscr...@pulsar.apache.org and replying to a

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 6, 2024, at 10:01 PM, Kalwit S wrote: > > Also, Pulsar may have > numbers of non-SM PMC’s and committers, but if you look at the numbers over > the last 2-3 years, you’ll see that 99% are from SM. If you are saying that this is the proportion of new committers and PMC members in the

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I like the notion of not updating documentation for versions that are out of EOL unless the documentation is incorrect. The only versions that should be on the documentation pop-up on https:/pulsar.apache.org/docs/x,y,z/ should be: - Next - active

Re: [DISCUSS] PIP-345: Optimize finding message by timestamp

What can you say about the time spent to maintain these new ledger fields? I think you are asking to modify the main message logic which is highly optimized., but I’m not sure. Have you tried your code on your own hardware? Do you have performance comparisons of the normal flow? > On Mar 11,

Re: (pulsar-site) branch main updated: Use alternative format for linefeed in markdown

> On Mar 12, 2024, at 3:32 PM, Lari Hotari wrote: > > On 2024/03/12 21:44:52 Dave Fisher wrote: >> Putting a blank line in between should do the same. > > There seem to be differences. > > A blank line in between will create separate paragraphs, example here:

Re: (pulsar-site) branch main updated: Use alternative format for linefeed in markdown

Putting a blank line in between should do the same. Best, Dave > On Mar 12, 2024, at 2:41 PM, lhot...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > lhotari pushed a commit to branch main > in repository

Re: Pulsar website update - GitHub profile links for committers and PMC members

I think this is great. There is one problem however. It is important to highlight our apache ids over our GitHub ids. Both are important, but having an easy to find map of name, apache-id, and GitHub-id will only help us all know each other better. Thanks, Dave > On Mar 19, 2024, at 7:26 AM,

Fwd: Announcing the Community Over Code 2024 Streaming Track

As the other organizer I’m forwarding this notice to the dev list. > Begin forwarded message: > > From: James Hughes > Subject: Announcing the Community Over Code 2024 Streaming Track > Date: March 20, 2024 at 7:23:17 AM PDT > To: us...@pulsar.apache.org > Reply-To: us...@pulsar.apache.org > >

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 7, 2024, at 4:20 AM, Neng Lu wrote: > > BTW, if your team is really tired of managing a stable Pulsar, StreamNative > can help you :) And so can DataStax ;-)

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

What would be the name of the image that contains the functions runtime? Best, Dave > On Mar 5, 2024, at 6:37 PM, Lari Hotari wrote: > > These are very welcome changes! Let's go ahead asap. > > -Lari > > On Wed, 6 Mar 2024 at 01:04, Matteo Merli wrote: >> >> The docker image `pulsar-all`

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

Moderators note. Colin is not subscribed to the mailing list. I’ve added them to the cc: > On Apr 10, 2024, at 9:56 AM, Colin Redmond wrote: > > Hello, > > I am the author of the Gestalt library and I am honored that you are > considering leveraging my library for your project. > > There

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

+1 (binding) I see no risk to this. The admin will know to turn on this feature should it be required. Best, Dave > On Apr 29, 2024, at 3:13 PM, Rajan Dhabalia wrote: > > Let me try again to ping on this thread as it's already been more than 4 > months for discussion and 2 weeks for the VOTE

Re: [apache/pulsar] [Bug] We are leaving old releases in the ASF distribution area. Please cleanup. (Issue #22486)

I’m looking here: https://downloads.apache.org/pulsar/ Where have the ALL of the CURRENT Pulsar releases gone? Instead of old releases ALL server releases were deleted?! Now there are NO official releases of Pulsar. These MUST BE restored by reverting the svn commit that deleted them and then

Re: [apache/pulsar] [Bug] We are leaving old releases in the ASF distribution area. Please cleanup. (Issue #22486)

PM, Dave Fisher wrote: > > I’m looking here: https://downloads.apache.org/pulsar/ > > Where have the ALL of the CURRENT Pulsar releases gone? > > Instead of old releases ALL server releases were deleted?! > > Now there are NO official releases of Pulsar. > > Th

[jira] [Commented] (PULSAR-16) Download page broken links

[ https://issues.apache.org/jira/browse/PULSAR-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365169#comment-17365169 ] Dave Fisher commented on PULSAR-16: --- See: [https://downloads.apache.org/pulsar/pulsar-2.8.0/connectors

<    1   2   3   4