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

Sounds greate that migrating to jersey 3.x from jersey 2.x. Thanks, Zixuan ZhangJian He 于2023年2月25日周六 11:01写道： > Hello, community. I want to know Which jakartaEE version we plan for pulsar > 3.0.0. Now we use jersey 2.x, which uses Jakarta EE8. > > Maybe we will need to update the jersey. > Ecl

Re: Introducer Pulsar admin api to pulsar-client-go

> I would like to suggest creating a new repository called "pulsar-admin-go" +1, I agreed with you. Thanks, Zixuan ZhangJian He 于2023年2月25日周六 11:05写道： > Following our previous discussions via email, I would like to suggest > creating a new repository called "pulsar-admin-go". This repository w

Re: Introducer Pulsar admin api to pulsar-client-go

Following our previous discussions via email, I would like to suggest creating a new repository called "pulsar-admin-go". This repository will serve as a platform for all of us to contribute our code. Pulsarctl[0] go first. Please let me know your thoughts on this matter. [0] - https://github.com

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

Hello, community. I want to know Which jakartaEE version we plan for pulsar 3.0.0. Now we use jersey 2.x, which uses Jakarta EE8. Maybe we will need to update the jersey. Eclipse Jersey (eclipse-ee4j.github.io) 2.x is for Jakarta EE8. 3.0.x is for Jakarta E

Re: [DISCUSSION] Mark Unused/Abandoned Pulsar Git Repositories Read Only

This is a good initiative. > (1) GitHub.com/apache/pulsar-client-ruby/ - There is only an initial commit > of a README. I think that it should be deleted. That has two PRs. That makes me think we should move the repo to read only, instead. > (2) GitHub.com/apache/pulsar-connectors/ - This was a

Re: [DISCUSSION] Mark Unused/Abandoned Pulsar Git Repositories Read Only

> Hi - > > We have several unmaintained or abandoned repositories. We should retire > these by either marking them read-only after leaving a README or we should > delete them. > > (1) GitHub.com/apache/pulsar-client-ruby/ - There is only an initial commit > of a README. I think that it should

[DISCUSSION] Mark Unused/Abandoned Pulsar Git Repositories Read Only

Hi - We have several unmaintained or abandoned repositories. We should retire these by either marking them read-only after leaving a README or we should delete them. (1) GitHub.com/apache/pulsar-client-ruby/ - There is only an initial commit of a README. I think that it should be deleted. (2)

Re: [DISCUSS] Apache Pulsar Adapters 2.11.0 release

There is a pulsar-connectors repository, but it was last changed in Nov 2020. I think that Sijie intended to move out the connectors to there … that effort should be either restarted or it should be made read only after leaving a README. There is a pulsar-presto repository which was abandoned a

Re: [DISCUSS] Apache Pulsar Adapters 2.11.0 release

+1 thanks I wonder if there are other sub-projects that we should release together with 2.10.0 Enrico Il giorno ven 24 feb 2023 alle ore 17:33 Christophe Bornet ha scritto: > > Hi everyone, > > The last release of the Pulsar Adapters was 2.8.0 in July 2021. > Even though there is not much activ

Re: [DISCUSS] PIP-247: Notifications for partitions update

> Just the way to implements partitioned-topic metadata > notification mechanism is much like notifications on regex sub changes Why do we need a separate notification implementation? The regex subscription feature is about discovering topics (not subscriptions) that match a regular expression. As

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

Great suggestions, Enrico. > It would be interesting to reject connections on the Proxy if the > client tries to set that field. I support making the proxy reject invalid input. We could also have the client reject connections where the client connect command includes `original_principal`, `origi

Re: [DISCUSS] PIP-249: Pulsar website redesign

You are correct - we did start with what content we wanted to show, then designed it to fit that content. We are releasing it for discussion, iteration and approval, piece by piece, as I said before since it's easier for everyone reviewing it do it in small pieces (just like in code). The “Homepag

[DISCUSS] Apache Pulsar Adapters 2.11.0 release

Hi everyone, The last release of the Pulsar Adapters was 2.8.0 in July 2021. Even though there is not much activity on this repo, there has been some bug fixes since then including one for the famous Log4Shell CVE. So I'd like to propose myself as a release manager for a Pulsar Adapters 2.11.0 rel

Re: [DISCUSS] PIP-249: Pulsar website redesign

On Fri, Feb 24, 2023 at 5:31 PM Dave Fisher wrote: > Hi - > > While I like this design effort so far - > > 1. The design needs to show how the site looks on smaller @media like > iPhones. > The PIP is mainly about the design concepts as displayed in the PIP, before proceeding with the heavy lift

Re: [DISCUSS] PIP-249: Pulsar website redesign

Hi - While I like this design effort so far - 1. The design needs to show how the site looks on smaller @media like iPhones. 2. The horizontal carousel at the bottom looks a little awkward. Will it automatically shift? 3. The website design was refreshed in 2021-2022. It was a difficult and l

Re: [DISCUSS] PIP-249: Pulsar website redesign

Asaf, okay. I see you have some plan. I’m just a bit confused with the steps ordering. Usually, such work starts with “What content do we want to show?” That implies content changes. Then “How can we display this content in the best way?”. That implies the work on visual design and content adjus

Re: [DISCUSS] PIP-249: Pulsar website redesign

I totally agree with your point Kyril, and as I wrote in the welcome email - I want to do all you wrote, but it has to be in bite size pieces. This piece is about theme and general look and feel. We "force" ourselves, by design, to avoid any content change - just like in code in this proposal - so

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

Makes sense. It would be interesting to reject connections on the Proxy if the client tries to set that field. On the broker there is no way to distinguish a proxy from a client, that's fair. But on the proxy it is not expected to see a connection from another proxy. +1 Enrico Il giorno ven 24

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

Hi, Michael Thanks for initiating this PIP. +1 BR, Zike Yang Zike Yang On Fri, Feb 24, 2023 at 12:16 PM Michael Marshall wrote: > > Hi Pulsar Community, > > In talking with Zike Yang on > https://github.com/apache/pulsar/pull/19540, we identified that it > would be helpful for the proxy to f

Re: [DISCUSS] PIP-249: Pulsar website redesign

While I find the proposed visual changes okay, I'm unsure about the homepage structure. I'd add one obvious point to the Goal section that can be formulated differently, but eventually is: - **The goal is to get more companies to start using Pulsar.** In other words, the landing page should **s