Re: [VOTE] Apache Pulsar 2.8.2 candidate 1

repos/dist/dev/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > Lin Lin > -- Nicolò Boschi

Re: [VOTE] Apache Pulsar 2.9.1 candidate 2

andidate-2 > > Link to the release notes: > https://github.com/apache/pulsar/pull/13357 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > > Enrico Olivelli > -- Nicolò Boschi

Re: WebSite build CI job does work - blocker for announcing release !

gt; Can anyone help ? > we are stuck and if we do not update the website we cannot announce the > releases with the security fixes > > > Enrico > -- Nicolò Boschi

Re: [VOTE] Apache Pulsar 2.8.2 candidate 2

ker with control over Thread Context Map data to cause a > > > denial of service when a crafted string is interpreted. This issue was > > > fixed in Log4j 2.17.0 and 2.12.3. > > > Already included > -- Nicolò Boschi

OWASP dependencies check on active branches

cking dependency upgrades. Also the check doesn't exist at all in that branch. Let me know what you think. Thanks, Nicolò Boschi [0] https://github.com/apache/pulsar/pull/13455 [1] https://github.com/apache/pulsar/pull/13451 [2] https://github.com/apache/pulsar/pull/13366 [3] https://github.com/apa

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

https://github.com/apache/pulsar/releases/tag/v2.9.2-candidate-2 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > Please download the source package, and follow the README to build > > and run the Pulsar standalone service. > -- Nicolò Boschi

Blocker issues on 'master' and 'branch-2.9' branches

better to include it in the next 2.9.x release 3. https://github.com/apache/pulsar/pull/14097 BR, Nicolò Boschi

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

eb 10, 2022 at 7:37 PM Lin Lin wrote: > > > > > > > +1(binding) > > > > 1. Checked the signature > > 2. Start standalone > > 3. Publish and consume successfully > > 4. Checked function > > > -- Nicolò Boschi

Re: [DISCUSS] Releasing Pulsar-client-go 0.8.0

om/apache/pulsar-client-go/milestone/9 > > >>> <https://github.com/apache/pulsar-client-go/milestone/7?closed=1> > > >>> > > >>> > > >>> For that reason, I think we should be releasing a 0.8.0 version with > > >>> > > >>> what we have today. > > >>> > > >>> > > >>> -- > > >>> > > >>> > > >>> Thanks > > >>> > > >>> Xiaolong Ran > > >> > > > > > > > > > -- > > > Best Regards, > > > Neng > > > > > -- Nicolò Boschi

Re: [VOTE] Pulsar Release 2.7.5 Candidate 1

x27;s KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > -- Nicolò Boschi

JDK 17 runtime compatibility

oving the CI to JDK17 after the branch-2.10 has been cut and targeting JDK17 runtime support for Pulsar 2.11 WDYT? BR, Nicolò Boschi

Re: [DISCUSS] PIP 141 : Pulsar BOM

t; > > The CI will have to build `pulsar-bom` before building Pulsar. > > ## Reject Alternatives > > The BOM could be part of a distinct Git project. This would be harder to > handle for contributions that modify both the BOM and Pulsar. > > > Thanks a lot for your feedback ! > > Christophe > -- Nicolò Boschi

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

b3727ffee67cdf035e8ea471b) > > https://github.com/apache/pulsar/releases/tag/v2.8.3-candidate-2 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > Please download the source package, and follow the README to build > > and run the Pulsar standalone service. > > > -- Nicolò Boschi

Re: [VOTE] Pulsar Release 2.8.3 Candidate 3

be voted upon: > > v2.8.3-candidate-3 (eba2671080341728f80435a82d2966726168e9da) > > https://github.com/apache/pulsar/releases/tag/v2.8.3-candidate-3 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > Please download the source package, and follow the README to build > > and run the Pulsar standalone service. > > -- Nicolò Boschi

Jacoco and Codecov.io integration for Code Coverage reports

com/marketplace/codecov). BR, Nicolò Boschi

Github actions - OWASP check status

them in order to fix the CI status BR, Nicolò Boschi

Re: Jacoco and Codecov.io integration for Code Coverage reports

Thanks Enrico for the feedback. I would like to merge the PR to complete the setup and reach more feedback for other contributors. Once we complete the setup, the Codecov bot will add a comment on every new pull request Nicolò Boschi Il giorno mar 22 mar 2022 alle ore 18:32 Enrico Olivelli

RocksDB upgrade - wait for BookKeeper 4.15.0 ?

atibility. I think we could push to the BookKeeper ML to not include the RocksDB upgrade in 4.14.5 Nicolò Boschi

Re: [VOTE] Pulsar Release 2.10.0 Candidate 5

+1 (non binding) - Checksum and signatures - Apache Rat check passes - Compile from source w JDK11 - Build docker image from source - Run Pulsar standalone and produce-consume from CLI Nicolò Boschi Il giorno ven 8 apr 2022 alle ore 15:43 Enrico Olivelli ha scritto: > +1 (bind

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

Heesung, thanks for the heads up. I added a comment in the PIP. I believe that the compile compatibility can be addressed with another pull and it does not overlap mine. Nicolò Boschi Il giorno lun 18 apr 2022 alle ore 20:25 Heesung Sohn < heesung.s...@streamnative.io> ha scritto:

Re: [ANNOUNCE] Apache Pulsar 2.10.0 released

Awesome! This is a big milestone for Pulsar! Congrats to everyone Nicolò Boschi Il giorno mer 20 apr 2022 alle ore 15:49 Lan Liang ha scritto: > Thanks for your work !!! > > > > > > > Best Regards, > Lan Liang > On 4/20/2022 17:20，Christophe Bornet wrote： >

Re: RocksDB upgrade - wait for BookKeeper 4.15.0 ?

At the end we'll have Pulsar 2.11 with BookKeeper 4.15.x (Andrey is working on the BK release and the upgrade in Pulsar) and therefore with M1 support. Pulsar 2.8, 2.9, 2.10 lines will have BookKeeper 4.14 (without the M1 support). Nicolò Boschi Il giorno mar 12 apr 2022 alle ore 15:10

[ANNOUNCE] Apache BookKeeper 4.14.5 released

The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.14.5. Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for real-time workloads. It has been used for a fundamental service to build reliable services. It is also the log segment st

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

anguage features but I believe maintaining release branches is more important for the Pulsar community. What do you think? Nicolò Boschi Il giorno lun 16 mag 2022 alle ore 03:53 Jia Zhai ha scritto: > Hi Dezhi, and Teng, > FYI. Here is the thread that discusses JDK 17. > > On Thu, May

Cherry-picking strategy to old branches to avoid JDK incompatibilities

anguage features but I believe maintaining release branches is more important for the Pulsar community. Nicolò Boschi

Re: Discuss about closing Pulsar resource

s not included in this shutdown time. So it is possible that we'd need to set a higher default value. A good plan would be to create an ad-hoc pull request for the "AsyncCloneable" interface where all the work is addressed in one shot. Nicolò Boschi Il giorno gio 26 mag 2022 alle ore

[DISCUSS] PIP-181: Pulsar Shell

ain. - Use another shell library. There are a couple of valid alternatives to JLine3 but it's wide-spread and the autocompletion API is much more flexible than others since it's not done with annotations (the shell needs to translate current JCommander definitions from existing tools) Nicolò Boschi

Re: [DISCUSS] PIP-181: Pulsar Shell

1 BR, Nicolò Boschi Il giorno mar 28 giu 2022 alle ore 10:06 Nicolò Boschi ha scritto: > Hi all, > > I opened a new PIP about Pulsar CLI tools. > Looking forward to seeing comments and suggestions. > > PIP: https://github.com/apache/pulsar/issues/16250 > > I posted a short

Heads up - Pulsar container updates on TestContainers

lenium web browsers, or anything else that can run in a Docker container. Cheers, Nicolò Boschi

Re: [DISCUSS] PIP-181: Pulsar Shell

shell). Nicolò Boschi Il giorno ven 1 lug 2022 alle ore 18:44 tison ha scritto: > Hi Xiaoyu, > > IIUC patch release must not include new features but only bug fixes. > > Best, > tison. > > > Anon Hxy 于2022年7月1日周五 23:59写道： > > > Hi Nicolò Boschi, > > > &g

Re: [DISCUSS] PIP-181: Pulsar Shell

> > Why are there 2 PIPs being discussed as PIP-181? There's another > discussion on dev with Those two PIP are not related, we just had a PIP number conflict. Qiang gently moved it to PIP-182 Nicolò Boschi Il giorno dom 3 lug 2022 alle ore 07:50 Joe F ha scritto: > Why

[VOTE] PIP-181: Pulsar Shell

org/thread/5sdy2yl2djsznhpmf9c67hrmqpvgz0ob Thanks, Nicolò Boschi

Pull requests potentially blocked by the Documentation Bot workflow

Hi all, There are some pull requests blocked by the Doc bot that never ends. I left a comment here https://github.com/apache/pulsar/pull/16368 because I think this pull is the culprit If we don't find a quick solution, I'll push a revert to unblock the master branch Thanks, Nicolò Boschi

Re: [ANNOUNCE] New Committer: Zixuan Liu

Congrats! Nicolò Boschi Il giorno gio 7 lug 2022 alle ore 13:28 Haiting Jiang < jianghait...@apache.org> ha scritto: > Congratulates, Zixuan! > > BR, > Haiting > > On 2022/07/07 10:03:36 Yu wrote: > > Hi team, > > > > The Project Management Com

Re: [VOTE] PIP-181: Pulsar Shell

The PIP passes with 4 bindings and 6 non-bindings +1. Please note the first pull is already ready for review: https://github.com/apache/pulsar/pull/16251 Thanks everyone, Nicolò Boschi Il giorno mer 6 lug 2022 alle ore 04:48 Michael Marshall < mmarsh...@apache.org> ha scritto: >

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

+1 (non binding) Checks: - Checksum and signatures - Apache Rat check passes - Compile from source w JDK11 - Build docker image from source - Run Pulsar standalone and produce-consume from CLI Thank you! Nicolò Boschi Il giorno ven 8 lug 2022 alle ore 13:47 Qiang Huang < qiang.hua

Re: [DISCUSS] PIP-181: Pulsar Shell

to declare most of the reflection accesses you will do at runtime. And Pulsar does a lot of reflections. Anyway, I don't think it is a different direction but instead a future optimization and we should push to have it after the base Pulsar shell is fully committed to the master branch. BR

CI - remove cmd line test retries?

to blindly restart the failed jobs. This is not the correct behaviour and it will make the CI less stable over time. The plan would be: - Remove the retries (see https://github.com/apache/pulsar/pull/16524) - Create issue for flaky tests - Fix them / move to quarantine WDYT? Thanks, Nicolò Boschi

Enable "Update branch" Github button in pull requests

st-in-sync-with-the-base-branch This is an example where I activated the button in my own Pulsar fork: https://github.com/nicoloboschi/pulsar/pull/4 Thanks, Nicolò Boschi

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

s and agreed to the usefulness of the code freezing. So a plan could be to try to merge the work in progress targeted for 2.11 by the mid of August and then start the code freezing as described in the PIP. Also, I volunteer for driving the release if nobody else is interested Thanks, Nicolò Boschi

Re: PIP-187 Add API to analyse a subscription backlog and provide a accurate value

+1, good work, I think it's very valuable for users for monitoring purposes. Nicolò Boschi Il giorno lun 18 lug 2022 alle ore 11:47 Lothruin Mirwen < lothruin.mir...@gmail.com> ha scritto: > This should be really helpful to monitor real backlog in production > environments. &

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

+1, thanks Nicolò Boschi Il Mar 19 Lug 2022, 22:16 Christophe Bornet ha scritto: > +1 > > Le mar. 19 juil. 2022 à 20:01, Andrey Yegorov > > a écrit : > > > +1 > > > > On Tue, Jul 19, 2022 at 10:51 AM Dave Fisher wrote: > > > > > +1 (binding

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

I understand the need for the Pulsar Summit. In that case I have to step back because I will be offline for the next few weeks Sorry Nicolò Boschi Il Gio 21 Lug 2022, 06:32 PengHui Li ha scritto: > Thanks for volunteering Nicolò. > > > So a plan could be to try to merge the work

Pulsar Flaky test report 2022-07-19 for PR builds in CI

ng a real production code bug. More contributions are welcome! Please keep up the good work! Thanks, Nicolò Boschi

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

Congrats! Very well deserved!! Nicolò Boschi Il Mar 26 Lug 2022, 18:26 Christophe Bornet ha scritto: > Congratulations Michael ! Well deserved ! > > Le mar. 26 juil. 2022 à 17:22, Enrico Olivelli a > écrit : > > > I am glad to announce that the Apache Pulsar PMC invite

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

+1 (non binding) Thanks, Nicolò Boschi Il giorno mer 10 ago 2022 alle ore 01:34 Neng Lu ha scritto: > Hi, > > Not sure if this is too late or not, I replied in the discussion thread > about some thinking. > Whether we tweak the sink connector or we allow a flexible and gen

Re: [DISCUSS] Skip unnecessary tests when there are only cpp/python related changes

A big +1 for this! Nicolò Boschi Il giorno dom 14 ago 2022 alle ore 06:20 Qiang Huang < qiang.huang1...@gmail.com> ha scritto: > +1. It can help reduce a lot of useless duplication of test cases. > > Michael Marshall 于2022年8月11日周四 09:58写道： > > > Great suggestio

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

This is another blocker for 2.11.0 for a regression about streaming dispatch that I found in the 2.11 branch https://github.com/apache/pulsar/pull/17143 Nicolò Boschi Il giorno mer 17 ago 2022 alle ore 11:45 Enrico Olivelli < eolive...@gmail.com> ha scritto: > We have this release b

Re: Enable "Update branch" Github button in pull requests

Any comments? Nicolò Boschi Il giorno mar 12 lug 2022 alle ore 18:06 Nicolò Boschi ha scritto: > Hi all, > > I'd like to propose to enable the Github button "update branch" in the > pull requests. > > The main reason is that it helps when you want to rebase

Re: [ANNOUNCE] Jiwei Guo as a new PMC member in Pulsar

Congratulations! Nicolò Boschi Il giorno gio 18 ago 2022 alle ore 14:15 Anon Hxy ha scritto: > Congratulations! > > Thanks, > Xiaoyu Hou > > PengHui Li 于2022年8月18日周四 19:25写道： > > > Hi, all > > > > I'm glad to announce that the Apache Pulsar PMC i

Re: [DISCUSS] Enable non-mandatory updating PR branches

+1. Actually I suggested the same a month ago https://lists.apache.org/thread/p3c6pb6gfgdb5mmdjky6h7njkt8ggl2v Nicolò Boschi Il giorno gio 18 ago 2022 alle ore 15:54 Yunze Xu ha scritto: > I’m glad to see the “update branch” option enabled for contributors. > > Thanks

Re: [DISCUSS] Enable non-mandatory updating PR branches

Just enabled by INFRA team. Enjoy it! Nicolò Boschi Il giorno ven 19 ago 2022 alle ore 10:36 tison ha scritto: > I can see that Nico has submitted an INFRA ticket > https://issues.apache.org/jira/browse/INFRA-23595 > > Thank you! > > Best, > tison. > > >

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

+1, it will have a great impact to the Pulsar ecosystem Nicolò Boschi Il giorno ven 19 ago 2022 alle ore 09:13 Zixuan Liu ha scritto: > +1 Great idea. > > > Thanks, > Zixuan > > Enrico Olivelli 于2022年8月18日周四 16:24写道： > > > Hello, > > I have drafted a P

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

+1 (non binding) Nicolò Boschi Il giorno mer 24 ago 2022 alle ore 09:11 Enrico Olivelli < eolive...@gmail.com> ha scritto: > Hello, > this is the official thread VOTE for PIP-201 Extensions mechanism for > Pulsar Admin CLI tools > > This is the PIP link https://github.com

Re: [VOTE] PIP-200 Package Pulsar Trino distro and config in a dedicated folder

+1 (non binding) Thanks for taking care of this Nicolò Boschi Il giorno lun 29 ago 2022 alle ore 15:26 tison ha scritto: > Hi devs, > > This is the official thread VOTE for PIP-200 Package Pulsar Trino distro > and config in a dedicated folder. > > Here is the PIP issue:

Re: [VOTE] Pulsar Release 2.7.5 Candidate 3

+1 (non binding) Checks: - Checksum and signatures - Apache Rat check passes - Compile from source - Run Pulsar standalone and produce-consume from CLI Nicolò Boschi Il giorno sab 27 ago 2022 alle ore 17:12 Qiang Huang < qiang.huang1...@gmail.com> ha scritto: > +1(no

Re: [VOTE] Pulsar Release 2.8.4 Candidate 1

+1 (non binding) Checks: - Checksum and signatures - Apache Rat check passes - Compile from source - Run Pulsar standalone and produce-consume from CLI - Tested K8S installation with Datastax Pulsar helm chart and verified TLS, offloads and ElasticSearch sink Nicolò Boschi Il giorno lun

Re: [DISCUSS] PIP-204: Reactive Java client for Apache Pulsar

Absolutely +1, great initiative Nicolò Boschi Il giorno mer 31 ago 2022 alle ore 04:22 guo jiwei ha scritto: > +1 > > > Regards > Jiwei Guo (Tboy) > > > On Wed, Aug 31, 2022 at 10:22 AM Zixuan Liu wrote: > > > +1 > > > > Best regards, &g

Re: [VOTE] PIP-205: Reactive Java client for Apache Pulsar

+1 (non binding) Nicolò Boschi Il giorno mer 31 ago 2022 alle ore 17:00 Christophe Bornet < bornet.ch...@gmail.com> ha scritto: > +1 (non-binding) > > Le mer. 31 août 2022 à 16:06, Lari Hotari a écrit : > > > Hello, > > > > This is the official VOTE thread f

Re: Pulsar CI congested, master branch build broken

ain in .asf.yaml, in the meantime be careful about merging PRs > 10. Fix quarantined flaky tests Nicolò Boschi Il giorno gio 8 set 2022 alle ore 09:27 Lari Hotari ha scritto: > If my assumption of the GitHub usage metrics bug in the GitHub Actions > build job queue fairness algorithm

Re: [VOTE] Pulsar Release 2.9.0 Candidate 2

96f056%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637708596313217418%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jCh35iDBW6JqqsAuiqri3jiY%2BU8bUN5ZXVySuKPUic8%3D&reserved=0 > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > Enrico Olivelli > > -- Nicolò Boschi

Re: Dropping Presto SQL in 2.9.0 - status ?

t case we could open a separate thread to say that > > > Pulsar SQL in 2.9.0 will work only on JDK11. > > > In Pulsar 2.8.0 we added official compatibility with JDK11 (and it is > the > > > preferred version, as it is the version used in the Docker images), so > > > requiring JDK11 for Pulsar SQL 2.9.0 does not sound bad to me. > > > > > > My primary concern is that the version of Presto that we are running is > > > obsolete and there are several security reports against it or its third > > > party dependencies. > > > > > > Thoughts ? > > > > > > Enrico > > > -- Nicolò Boschi

Re: [VOTE] Apache Pulsar 2.9.0 candidate 4

9.0-SNAPSHOT-src.tar.gz > > > > > > > > Maven staging repo: > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1104/ > > > > > > > > The tag to be voted upon: > > > > v2.9.0-candidate-4 (bdd57b21a66b81aab72c4ec39d516ffd2a769c35) > > > > https://github.com/apache/pulsar/releases/tag/v2.9.0-candidate-4 > > > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > > > Please download the source package, and follow the README to build > > > > and run the Pulsar standalone service. > > > > > > > > Enrico Olivelli > > > > > > > > -- Nicolò Boschi

Re: [VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1

+1 binding I followed the instructions from here - https://github.com/apache/pulsar-client-reactive /wiki/Release-process#release-validation . Thanks, Nicolò Boschi Il giorno mer 4 ott 2023 alle ore 12:42 Enrico Olivelli ha scritto: > My command was wrong, you have to use "--verify&

Re: [ANNOUNCE] Yubiao Feng as new PMC member in Apache Pulsar

Congrats!! Nicolò Boschi Il giorno lun 13 nov 2023 alle ore 15:26 Xiangying Meng < xiangy...@apache.org> ha scritto: > Congrats! Yubiao. > > Thanks, > Xiangying > > On Mon, Nov 13, 2023 at 8:15 PM Kai Wang wrote: > > > Congrats! > > > > Thanks, > > Kai > > >

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.0 Candidate 2

+1 binding I followed the instructions from here - https://github.com/apache/pulsar-client-reactive /wiki/Release-process#release-validation . Il giorno gio 16 nov 2023 alle 10:22 Lari Hotari ha scritto: > +1 (binding) > > - verified source package checksum and signature. > - verified staged m

Re: [ANNOUNCE] New Committer: Chris Bono

Congrats! Nicolò Boschi Il giorno mar 21 nov 2023 alle ore 07:56 Horizon <1060026...@qq.com.invalid> ha scritto: > Congrats! > >

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.1 Candidate 1

+1 (binding) - followed instructions here: https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation . - ran unit tests with "gradle test" Tested on jdk17 and M3 MacOS Nicolò Boschi Il giorno gio 14 dic 2023 alle ore 07:18 Lari Hotari ha scritto: >

Re: [VOTE] PIP-326: Create a BOM to ease dependency management

+1 binding Nicolò Boschi Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari ha scritto: > +1 (binding) > > -Lari > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono wrote: > > > > I'm starting the vote for PIP-326, since it has been reviewed by > > severa

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.3 Candidate 1

+1 binding - Validated checksum and signature - Compared source tarballs with the git tag ones - Ran build and tests with JDK21 - all green Thanks, Nicolò Boschi Il giorno lun 19 feb 2024 alle ore 18:06 Enrico Olivelli < eolive...@gmail.com> ha scritto: > +1 (binding) > > Val

Re: [ANNOUNCE] New Committer: Asaf Mesika

Congratulations! Nicolò Boschi Il giorno mer 21 feb 2024 alle 07:29 Zike Yang ha scritto: > Congratulations! > > BR, > Zike Yang > > On Wed, Feb 21, 2024 at 2:22 PM Hang Chen wrote: > > > > Congratulations Asaf! > > > > Best, >

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

+1, great ideas Let's make sure there's a dedicated section in the docs on how to "migrate" from pulsar-all:3.2.0 to "build your own -all image" Nicolò Boschi Il giorno mer 6 mar 2024 alle ore 04:22 Matteo Merli ha scritto: > I was proposing `pulsar-function

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

project if the maintainer just stops working on it. Nicolò Boschi Il giorno ven 15 mar 2024 alle ore 19:00 Zixuan Liu ha scritto: > +1 > > This is a good idea that using Gestalt config, which supports json, yaml, > env and so on. > > One notice that Gestalt requires Java 11 or

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

+1 binding - Verified checksum and signatures - Installed default Pulsar on K3S, test simple produce and consume working well - Verified default image pointing to Pulsar 3.0.3 Thanks, Nicolò Boschi Il giorno mer 20 mar 2024 alle ore 19:15 David Jensen ha scritto: > +1 (bind

Fwd: [ANNOUNCE] Apache BookKeeper 4.16.5 released

Nicolò Boschi -- Forwarded message - Da: Nicolò Boschi Date: gio 11 apr 2024 alle ore 15:51 Subject: [ANNOUNCE] Apache BookKeeper 4.16.5 released To: , , < annou...@apache.org> The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.16.5. Apache Book

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.4 Candidate 1

+1 binding - Validated checksum and signature - Compared source tarballs with the git tag ones - Ran build and tests with JDK21 - all green Thanks, Nicolò Boschi Il giorno dom 14 apr 2024 alle ore 14:16 guo jiwei ha scritto: > > +1 (binding) > > - validate checksum > - val

Re: [DISCUSS] Upgrading to Jetty 12 since Jetty 9.4.x has reached end-of-line in June 2022

I personally agree with NOT including it in 3.3.x Following the release policy, it should be time to start preparing the 3.3.x branch soon. Also I wonder if the release line after 3.3.x will be 4.0, given that 3.0 has been released almost 1y ago and the LTS should be cut every 18 months. Having th

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

+1 binding Nicolò Boschi Il giorno mar 30 apr 2024 alle ore 00:34 Dave Fisher ha scritto: > > +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, Raja

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.5 Candidate 1

+1 binding - Validated checksum and signature - Compared source tarballs with the git tag ones - Ran build and tests with JDK17 - all green Thanks, Nicolò Boschi Il giorno gio 16 mag 2024 alle ore 09:26 guo jiwei ha scritto: > > +1 (binding) > > - checked sha512 checksum > - ch

Re: [VOTE] Release Apache Pulsar 3.0.5 based on 3.0.5-candidate-1

+1 (binding) - Built from source - Checked the signatures of the source and binary release artifacts - Ran pulsar standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Thanks, Nicolò Boschi Il giorno ven 17 mag 2024 alle ore 10:56

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

+1 binding Verified checksum and default Pulsar image to be 3.0.5 Nicolò Boschi Il giorno mar 4 giu 2024 alle ore 13:56 Lari Hotari ha scritto: > > +1 (binding) > > -Lari > > On 2024/05/17 15:00:16 Lari Hotari wrote: > > Hello Apache Pulsar Community, > > >

Re: [VOTE] PIP-352: Event time based topic compactor

+1 binding Nicolò Boschi Il giorno lun 29 lug 2024 alle ore 15:04 guo jiwei ha scritto: > > +1 (binding) > > > > > Regards > Jiwei Guo (Tboy) > > > On Sat, Jul 27, 2024 at 1:41 PM Enrico Olivelli wrote: > > > +1 (binding) > > > > Than

Re: Pulsar CI congested, master branch build broken

t is suggested to run the actions in your own Pulsar fork. Please don’t re-run failed jobs or push any other commits to avoid triggering new actions Nicolò Boschi Il giorno gio 8 set 2022 alle ore 09:42 Nicolò Boschi ha scritto: > Thanks Lari for the detailed explanation. This is

Re: Pulsar CI congested, master branch build broken

; that indicates the Pulsar CI successfully passed There's a slight chance that the CI will be stuck again in the next few days but we will take it monitored. Thanks Lari for the nice work! Regards, Nicolò Boschi Il giorno gio 8 set 2022 alle ore 10:55 Lari Hotari ha scritto: > Than

Re: Enable "Update branch" Github button in pull requests

ll come back to this thread when it's done Regards, Nicolò Boschi Il giorno ven 9 set 2022 alle ore 06:27 Lari Hotari ha scritto: > Good points Hang. Yes, let's remove the "update branch" button since it > seems to lead to unnecessary load for CI. > > -Lari >

Re: Enable "Update branch" Github button in pull requests

Done Nicolò Boschi Il giorno ven 9 set 2022 alle ore 08:32 Nicolò Boschi ha scritto: > That's a good observation. We don't have data so we can't be sure about > that, but I think that it can be a possible cause of the recent congestion. > > I opene

Re: Pulsar CI congested, master branch build broken

this situation. We're waiting for updates from the Github support issue that Lari reported. Nicolò Boschi Il giorno ven 9 set 2022 alle ore 04:09 Michael Marshall < mmarsh...@apache.org> ha scritto: > Fantastic, thank you Lari and Nicolò! > > - Michael > > On Thu, Sep

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

BK 4.15.0 raised by the Pravega team (https://github.com/apache/bookkeeper/issues/3466) but we can't wait for them. We don't know if the same issue applies to Pulsar and the time for: find the issue - fix it - cut a release may be weeks or months. Nicolò Boschi Il giorno lun 5 set 202

Re: [DISCUSS] Apache Pulsar 2.10.2 release

Hi all, I found a regression during the potential upgrade to 2.10.2 (and also 2.11). I created a fix here: https://github.com/apache/pulsar/pull/17690 and set as blocker for the release Please review Thanks, Nicolò Boschi Il giorno mer 7 set 2022 alle ore 16:12 Haiting Jiang < jiangh

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

t. But I found another release blocker here: https://github.com/apache/pulsar/pull/17690 After that, I think we should go forward and continue with the release. Pulsar 2.11 will contain awesome features and we already have held it too much based on the release schedule. Regards, Nicolò Boschi

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

+1 (non binding) Nicolò Boschi Il giorno mar 27 set 2022 alle ore 10:17 Qiang Huang < qiang.huang1...@gmail.com> ha scritto: > +1 (non-binding) > > Yunze Xu 于2022年9月27日周二 11:35写道： > > > +1 (non-binding) > > > > Thanks, > > Yunze > > > &g

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

I've found another release blocker about client compatibility with jdk8/11, please review https://github.com/apache/pulsar/pull/17873 Nicolò Boschi Il giorno ven 16 set 2022 alle ore 10:54 Nicolò Boschi ha scritto: > Actually Yong found the root cause of the issue, see

Re: [VOTE] Pulsar Release 2.10.2 Candidate 1

+1 (non binding) - Checksum and signatures - Apache Rat check passes - Compile from source w JDK11 - Build docker image from source - Run Pulsar standalone and produce-consume from CLI - Tested a couple of connectors (ElasticSink, JDBC sink) in K8S env Nicolò Boschi Il giorno lun 26 set

Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML

Absolutely +1 Thanks Michael Nicolò Boschi Il giorno mer 12 ott 2022 alle ore 08:56 Yu ha scritto: > +1, thank you, Michael! > > > On Wed, Oct 12, 2022 at 1:00 PM Matteo Merli > wrote: > > > +1 Thanks Michael for fixing these! > > > > > > > >

Re: [ANNOUNCE] New Committer: Qiang Huang

Congrats! Nicolò Boschi Il giorno ven 14 ott 2022 alle ore 09:18 Jiaqi Shen ha scritto: > Congratulations! > > (Are you BUPTer?🤔 ) > > Thanks, > Jiaqi Shen > > > Jun Ma 于2022年10月14日周五 14:55写道： > > > Congratulations, Qiang! > > ___

Pulsar Flaky test report 2022-10-17 for PR builds in CI

ugs. Fixing the flaky test might result in fixing a real production code bug. More contributions are welcome! Please keep up the good work! (Also thanks to Lari for all the work done to have these clean reports) Thanks, Nicolò Boschi

Re: [VOTE] PIP-208: HTTP Sink

+1 non binding Nicolò Boschi Il giorno mar 18 ott 2022 alle ore 10:47 Enrico Olivelli < eolive...@gmail.com> ha scritto: > +1 (binding) > > Enrico > > Il giorno gio 13 ott 2022 alle ore 19:35 Christophe Bornet > ha scritto: > > > > Hi folks, > > &g

Re: [ANNOUNCE] Haiting Jiang as a new PMC member in Apache Pulsar

Congrats!! Nicolò Boschi Il giorno mar 18 ott 2022 alle ore 16:55 Michael Marshall < mmarsh...@apache.org> ha scritto: > Congratulations Haiting! > > - Michael > > On Tue, Oct 18, 2022 at 3:06 AM Hang Chen wrote: > > > > Hi all, > > > > The Apache

Re: [ANNOUNCE] New Committer: Zili Chen

Congrats! Nicolò Boschi Il giorno gio 10 nov 2022 alle ore 08:25 Aloys Zhang ha scritto: > Congratulations! tison > > Enrico Olivelli 于2022年11月10日周四 15:09写道： > > > Congratulations! > > > > Enrico > > > > Il Gio 10 Nov 2022, 08:07 Haiting Jiang

Re: Releasing current master as Pulsar 2.11.0 ?

to reproduce the problem > with > > > > > > Pulsar. > > > > > > >>>>>> I believe that it will take at least another week before > having more > > > > > > >>>>>> results about the investigations I am doing on BK. The > problem is > > > > > > >>>>>> reproducible only on a long-running test (more than 4 > hours) of a > > > > > > >>>>>> third party project and only in some private QA > environment. > > > > > > >>>>>> > > > > > > >>>>>> Thoughts ? > > > > > > >>>>>> > > > > > > >>>>>> Enrico > > > > > > >>>>> > > > > > > >>>> > > > > > > >>> > > > > > > >> > > > > > > >> On Tue, Nov 1, 2022 at 2:15 PM Michael Marshall < > mmarsh...@apache.org> > > > > > > >> wrote: > > > > > > >> > > > > > > >>> I am concerned that we have too many active release > branches, and > > > > > > planning > > > > > > >>> to follow 2.11.0 with 3.0.0 soon after feels like it will > make that > > > > > > problem > > > > > > >>> worse. As it is, we already need to discuss EOL for 2.7 and > 2.8. > > > > > > >>> > > > > > > >>> Thanks, > > > > > > >>> Michael > > > > > > >>> > > > > > > >>>> On Mon, Oct 31, 2022 at 7:55 PM PengHui Li < > peng...@apache.org> > > > > > > wrote: > > > > > > >>> > > > > > > >>>> Releasing from the master branch will bring more > uncertainty, no? > > > > > > >>>> We have fixed many regressions that were introduced to > branch-2.11. > > > > > > >>>> If we cut a new branch-2.11 based on the master branch. > Maybe new > > > > > > >>>> regressions > > > > > > >>>> will happen again. This may make us wait another month to > have a > > > > > > 2.11.0 > > > > > > >>>> release. > > > > > > >>>> > > > > > > >>>> IMO, we can start Pulsar 3.0 (follow > > > > > > >>>> https://github.com/apache/pulsar/issues/15966) > > > > > > >>>> after 2.11.0 is released instead of waiting for 3 more > months. > > > > > > >>>> > > > > > > >>>> For https://github.com/apache/bookkeeper/issues/3466 > > > > > > >>>> I don't think it's a blocker for the Pulsar release for now. > > > > > > >>>> Yes, it is worth investigating more. We also tried a chaos > test for > > > > > > that > > > > > > >>>> case. > > > > > > >>>> We haven't reproduced the problem on Pulsar. > > > > > > >>>> > > > > > > >>>> Now, we are just waiting for the new BookKeeper release > 4.15.3 since > > > > > > >>> 4.15.2 > > > > > > >>>> has regressions [1] > > > > > > >>>> > > > > > > >>>> [1] https://github.com/apache/bookkeeper/pull/3523 > > > > > > >>>> > > > > > > >>>> Thanks, > > > > > > >>>> Penghui > > > > > > >>>> > > > > > > >>>> On Tue, Nov 1, 2022 at 3:10 AM Michael Marshall < > mmarsh...@apache.org > > > > > > > > > > > > > >>>> wrote: > > > > > > >>>> > > > > > > >>>>> I have not followed the branch-2.11 work closely, but I > think it > > > > > > makes > > > > > > >>>>> sense to re-create branch-2.11 from the current master. > > > > > > >>>>> > > > > > > >>>>> We created branch-2.11 almost 3 months ago. Re-creating > the branch > > > > > > >>>>> will prevent unnecessary delay on new features added over > the past 3 > > > > > > >>>>> months. > > > > > > >>>>> > > > > > > >>>>> If we follow through with this proposal, we will need to > clean up PR > > > > > > >>>>> tags and milestones to prevent confusion. > > > > > > >>>>> > > > > > > >>>>> Thanks, > > > > > > >>>>> Michael > > > > > > >>>>> > > > > > > >>>>> On Mon, Oct 31, 2022 at 3:31 AM Enrico Olivelli < > eolive...@gmail.com > > > > > > > > > > > > > >>>>> wrote: > > > > > > >>>>>> > > > > > > >>>>>> Hello Pulsar fellows, > > > > > > >>>>>> > > > > > > >>>>>> I think that too much time passed since we wanted to cut > 2.11. > > > > > > >>>>>> > > > > > > >>>>>> The branch-2.11 contains some code used by no one. > > > > > > >>>>>> > > > > > > >>>>>> In the meantime many features went into master branch, > > > > > > >>>>>> > > > > > > >>>>>> I don't think that it is worth it to cut a release from > branch-2.11 > > > > > > >>>>>> and start with something that is already stale. > > > > > > >>>>>> > > > > > > >>>>>> I propose to drop branch-2.11 and create a new branch out > of the > > > > > > >>>>>> current master branch and start the period of hardening > before > > > > > > >>> cutting > > > > > > >>>>>> the release. > > > > > > >>>>>> > > > > > > >>>>>> IIUC we are waiting for this BookKeeper issue to be > confirmed or > > > > > > >>> fixed > > > > > > >>>>>> or closed as "not a problem": > > > > > > >>>>>> https://github.com/apache/bookkeeper/issues/3466 > > > > > > >>>>>> I am personally working on that case together with the > folks you > > > > > > >>>>>> created the issue. > > > > > > >>>>>> Honestly I have never been able to reproduce the problem > with > > > > > > Pulsar. > > > > > > >>>>>> I believe that it will take at least another week before > having more > > > > > > >>>>>> results about the investigations I am doing on BK. The > problem is > > > > > > >>>>>> reproducible only on a long-running test (more than 4 > hours) of a > > > > > > >>>>>> third party project and only in some private QA > environment. > > > > > > >>>>>> > > > > > > >>>>>> Thoughts ? > > > > > > >>>>>> > > > > > > >>>>>> Enrico > > > > > > >>>>> > > > > > > >>>> > > > > > > >>> > > > > > > > > > > > > > -- Nicolò Boschi

  1   2   >