Hi, I spent some time bringing the connector up to date to 1.20. Merged most hanging PRs, updated the CI, and also opened a new PR [1] that aims to bump Flink to 1.20.3, and Pulsar client to 3.0.5 (which is the latest version, that uses the current API).
I am not a Pulsar expert, so I would appreciate if someone else could review this. The CI is green now and I did not applied any meaningful logic changes, so it should be straightforward. If this gets merged, there are 1 bugfix PR that I had a question about, but after that gets merged as well, I believe the connector will be in a releasable state. Best, Ferenc [1] https://github.com/apache/flink-connector-pulsar/pull/111 On Friday, September 19th, 2025 at 08:46, Martijn Visser <[email protected]> wrote: > > > Hi Fabrizzio, > > It looks like the original reviewers of the Flink Pulsar connector aren't > involved in the project anymore; that means that there's a lack of > expertise when it comes to reviewing the PRs. Ideally someone volunteers to > review the PRs with expertise, and a committer takes a final look before > merging it. But it looks like the latest PRs haven't gotten any review at > all. > > Thanks, > > Martijn > > On Thu, Sep 18, 2025 at 6:19 AM Fabrizzio Chávez Tejada < > [email protected]> wrote: > > > Hello, I can see this repository > > https://github.com/apache/flink-connector-pulsar is abandoned, there are > > many PRs without any response, there are a merge with a hotfix pending to > > be published in a new release, currently is more difficult to run flink > > 1.17/1.18 in kubernetes cluster using the flink kubernetes operator because > > of kubernetes upgrades, vendor patches, etc. How can we solve the absense > > of reviewers or commiters? I can see multiple comments where the people is > > complaining about this situation. > > If the plan is to not maintain this repository, why is still mentioned in > > the main page as a supported connector? I can see the same scenario for > > rabbitMQ connector. > > > > Regards, > > Fabrizzio
