[DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK

2025-05-29 Thread Matteo Merli
EOL timeline: https://endoflife.date/oracle-jdk * [4] NewRelic report on Java ecosystem https://newrelic.com/resources/report/2024-state-of-the-java-ecosystem -- Matteo Merli

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

2025-02-26 Thread Matteo Merli
+1 binding * Checked signatures * Compiled * Ran standalone and perf client on mac -- Matteo Merli On Wed, Feb 19, 2025 at 1:24 PM Lari Hotari wrote: > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version > 3.0.10 based on 3.0.10

Re: [VOTE] Release Apache Pulsar 3.3.5 based on 3.3.5-candidate-2

2025-02-26 Thread Matteo Merli
+1 binding * Checked signatures * Compiled * Ran standalone and perf client on mac -- Matteo Merli On Tue, Feb 25, 2025 at 6:55 AM Lari Hotari wrote: > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version 3.3.5 > based on 3.3.5

Re: [VOTE] Release Apache Pulsar 4.0.3 based on 4.0.3-candidate-2

2025-02-26 Thread Matteo Merli
+1 binding * Checked signatures * Compiled * Ran standalone and perf client on mac -- Matteo Merli On Tue, Feb 25, 2025 at 6:00 AM Lari Hotari wrote: > Hello Apache Pulsar Community, > > This is a call for the vote to release the Apache Pulsar version 4.0.3 > based on 4.0.3

Re: [VOTE] Pulsar Client C++ Release 3.7.0 Candidate 1

2025-01-02 Thread Matteo Merli
+1 * Checked checksums * Compiled on Mac * Verified perf producer & consumer -- Matteo Merli On Wed, Jan 1, 2025 at 7:15 PM Yunze Xu wrote: > This is the first release candidate for Apache Pulsar Client C++, version > 3.X.0. > > It fixes the following issues: > https:

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

2024-10-04 Thread Matteo Merli
+1 * Checked signatures * Checked standalone and produce/consume -- Matteo Merli On Fri, Oct 4, 2024 at 10:09 AM PengHui Li wrote: > +1 (binding) > > - Checked the signature of the binary release artifacts > - Start Pulsar standalone > - Verified Produce and Consume >

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

2024-10-04 Thread Matteo Merli
+1 * Checked signatures * Checked standalone and produce/consume -- Matteo Merli On Fri, Oct 4, 2024 at 9:12 AM PengHui Li wrote: > +1 (binding) > > - Checked the signature of the binary release artifacts > - Start Pulsar standalone > - Verified Produce and Consume >

Re: [VOTE] PIP-384: ManagedLedger interface decoupling

2024-10-01 Thread Matteo Merli
+1 -- Matteo Merli On Tue, Oct 1, 2024 at 5:03 PM Rajan Dhabalia wrote: > +1 (binding) > > Thanks, > Rajan > > On Tue, Oct 1, 2024 at 9:36 AM Lari Hotari wrote: > > > Hi, > > > > I'd like to start the voting thread for PIP-384: ManagedLedger

Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering

2024-10-01 Thread Matteo Merli
+1 -- Matteo Merli On Tue, Oct 1, 2024 at 4:53 PM Lari Hotari wrote: > Hi, > > I'd like to start the voting thread for PIP-379: Key_Shared Draining > Hashes for Improved Message Ordering > > Proposal PR: https://github.com/apache/pulsar/pull/23309 > Rendered PIP docu

Re: [VOTE] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation

2024-06-29 Thread Matteo Merli
+1 -- Matteo Merli On Fri, Jun 28, 2024 at 11:07 PM Apurva Telang wrote: > Hello All, > > I would like to start the voting thread for PIP-337: SSL Factory Plugin to > customize SSL Context and SSL Engine generation > > PIP link: https://github.com/apache/pulsar/pull/2201

Re: [DISCUSS] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation

2024-06-27 Thread Matteo Merli
Hi Apurva, Thanks for applying the changes to the proposal. It looks good and given the time since it was already created, please feel free to move to a vote at any time. -- Matteo Merli On Wed, Jun 26, 2024 at 8:35 PM Apurva Telang wrote: > Hello All, > > I had submitted PIP-

[DISCUSS] PIP-347 Extend LTS release process to client SDKs

2024-04-24 Thread Matteo Merli
nd brokers running in different major versions will always be guaranteed, when using the lowest common denominator of supported features. --- [1]: PIP-175 https://github.com/apache/pulsar/issues/15966 -- Matteo Merli

Re: [DISCUSS] Plan for Pulsar Go Client 1.0.0

2024-03-29 Thread Matteo Merli
The plan looks great. I’d add one more item for consideration: using WithX() methods instead of a strict for configurations: https://github.com/apache/pulsar-client-go/issues/68 -- Matteo Merli On Fri, Mar 29, 2024 at 5:38 AM Zike Yang wrote: > Hi, everyone > > The Pulsar Go Cli

[RESULT] [VOTE] PIP-342: Support OpenTelemetry metrics in Pulsar client

2024-03-22 Thread Matteo Merli
Closing this vote with 4 binding and 4 non-binding +1s Binding +1s: * Lari * Mattison * PengHui * Matteo Non-Binding +1s: * Dao Jun * Apurva * Asaf * Zixuan Thanks, Matteo -- Matteo Merli On Thu, Mar 14, 2024 at 11:54 PM Zixuan Liu wrote: > +1 (non-binding) > > Thanks,

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

2024-03-15 Thread Matteo Merli
ht up in PIP-346, since we could have a `broker-defaults.conf` file and a `broker.conf` with just few overrides, plus removing the `apply-config-from-env.py` script. We should also do this for BookKeeper though, otherwise it won't be as useful. -- Matteo Merli On Fri, Mar 15, 2024 at 11

[VOTE] PIP-342: Support OpenTelemetry metrics in Pulsar client

2024-03-13 Thread Matteo Merli
PIP: https://github.com/apache/pulsar/pull/22178 WIP PR: https://github.com/apache/pulsar/pull/22179 -- Matteo Merli

Re: [DISCUSS] PIP-342: Support OpenTelemetry metrics in Pulsar client

2024-03-13 Thread Matteo Merli
I have updated the proposal (and the WIP PR) based on the very helpful feedback received. I will start a VOTE thread for this PIP. Thanks. -- Matteo Merli On Sun, Mar 3, 2024 at 5:14 AM 太上玄元道君 wrote: > +1 > > Enrico Olivelli 于2024年3月3日 周日16:58写道: > > > I support the initi

Re: [VOTE] PIP-324: Alpine Docker images

2024-03-08 Thread Matteo Merli
Thanks everyone, closing the vote with 4 binding +1s. +1 votes: * Lari * PengHui * Enrico * Matteo -- Matteo Merli On Tue, Mar 5, 2024 at 11:48 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il Mer 6 Mar 2024, 02:55 PengHui Li ha scritto: > > > +1 (

Re: [VOTE] Pulsar Client Go Release 0.12.1 Candidate 1

2024-03-07 Thread Matteo Merli
+1 Verified checksums and signatures Verified tests and local perf client -- Matteo Merli On Wed, Mar 6, 2024 at 9:23 PM Yunze Xu wrote: > +1 (binding) > > - Verified checksum and signatures > - Run OAuth2 e2e examples with 0.12.1-candidate-1 > - Built from source and run

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

2024-03-07 Thread Matteo Merli
Using the Alpine image (PIP-324 in progress), removing Python I was able to see ~350 MB size for the `pulsar` base image. There could be additional space savings by removing unused JVM modules from the image. -- Matteo Merli On Thu, Mar 7, 2024 at 10:09 AM Girish Sharma wrote: > +1 &

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

2024-03-06 Thread Matteo Merli
On Wed, Mar 6, 2024 at 7:02 PM Kalwit S wrote: > I know I’m not trying to be disrespectful, but it’s not respectful to be > biased and act like an expert during the reviews, while you’ve contributed > just for documentation PRs. When I talk about experience, I’m talking about > reviewers who don’

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

2024-03-06 Thread Matteo Merli
On Wed, Mar 6, 2024 at 12:49 PM Kalwit S wrote: > Thanks for your reply. But I wasn’t going to go after a specific person. I > Though that's precisely what your message was doing, in a very rude way. (1) How many reviewers (less than 1) have been involved in PIP review > outside of the streamna

Re: [DISCUSS] Community Meeting Notes Are Missing

2024-03-06 Thread Matteo Merli
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, 2024 at 6:43 AM Dave Fisher wrote: > Hi - > > I see from the last meeting the following agenda: > > > 2024/02/29 > > At

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

2024-03-05 Thread Matteo Merli
sonal attacks are not OK here 2. I don't think it's good looking when you're reacting to people disagreeing with you by claiming they either are incompetent or have some hidden agenda. Perhaps trying to understand why they disagreed with you would be more helpful. Matteo -- Matteo Me

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

2024-03-05 Thread Matteo Merli
I was proposing `pulsar-functions-python`, though I'm open to any other name -- Matteo Merli On Tue, Mar 5, 2024 at 6:43 PM Dave Fisher wrote: > What would be the name of the image that contains the functions runtime? > > Best, > Dave > > > On Mar 5, 2024, at 6

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

2024-03-05 Thread Matteo Merli
will be very easy for users to select the appropriate image and we wouldn't be carrying a big amount of useless Python dependencies to users who don't need them. What are people's opinions with respect to this? Matteo -- Matteo Merli

[VOTE] PIP-324: Alpine Docker images

2024-03-05 Thread Matteo Merli
Opening the vote thread for PIP-324: Alpine Docker images https://github.com/apache/pulsar/pull/21716 WIP PR: https://github.com/apache/pulsar/pull/22054 Thank you, Matteo -- Matteo Merli

Re: [DISCUSS] PIP-324: Alpine Docker images

2024-03-05 Thread Matteo Merli
Since the discussion has been open for a while now, I will proceed to a vote. Thanks everyone for bringing out all the perspectives here. Matteo -- Matteo Merli On Fri, Mar 1, 2024 at 10:17 AM Alexander Hall wrote: > Matteo, > > Yes, I'm seeing a similar number of vulner

[DISCUSS] PIP-342: Support OpenTelemetry metrics in Pulsar client

2024-03-02 Thread Matteo Merli
ient.lookup{type="list-topics"}` | Histogram | seconds | Counter of namespace list topics operations | Additionally, all the histograms will have a `success=true|false` label to distinguish successful and failed operations. -- Matteo Merli

Re: [DISCUSS] PIP-324: Alpine Docker images

2024-03-01 Thread Matteo Merli
t 9.3) Total: 172 (UNKNOWN: 0, LOW: 144, MEDIUM: 28, HIGH: 0, CRITICAL: 0) Full list: https://gist.github.com/merlimat/a4fcea7336cab83ad64dcf01d9b15a1c -- Matteo Merli On Fri, Mar 1, 2024 at 9:19 AM Alexander Hall wrote: > According to Red Hat their latest tagged release for UBI9.3, 9.3-1

Re: [DISCUSS] Do not create partitioned metadata when calling pulsarClient.getPartitionsForTopic(topicName)

2024-02-29 Thread Matteo Merli
Rather than raise the protocol version, there’s a feature flag mechanism in the connect/connected handshake for this purpose -- Matteo Merli On Thu, Feb 29, 2024 at 6:38 AM PengHui Li wrote: > Yes, it’s better to bump a protocol version to keep the compatibility. > > Regards,

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

2024-02-21 Thread Matteo Merli
Good idea. It would be nice to just have the config library to read the environment variables directly, instead of having to write them down in the file. -- Matteo Merli On Wed, Feb 21, 2024 at 1:28 AM Lari Hotari wrote: > Hello everyone, > > I would like to bring up an issue with

Re: Re: [DISCUSS] PIP-324: Alpine Docker images

2024-02-15 Thread Matteo Merli
Hi Alex, the situation for UBI9 doesn't look much different from Ubuntu: registry.access.redhat.com/ubi9/ubi (redhat 9.3) Total: 166 (UNKNOWN: 0, LOW: 138, MEDIUM: 28, HIGH: 0, CRITICAL: 0) Full list: https://gist.github.com/merlimat/ba96b91ea49709bb218ddc3906bb9e95 -- Matteo Merli O

Re: Re: [DISCUSS] PIP-324: Alpine Docker images

2024-02-14 Thread Matteo Merli
aa269bdf943c8f37aa5430258b7b4018f37ed120abb17a?context=explore Thanks, Matteo -- Matteo Merli On Wed, Dec 20, 2023 at 12:49 PM David Christle wrote: > Are we sure the move to Alpine is worth the extensive performance testing > and the risk of issues? Sticking with a popular glibc image lik

[RESULT] [VOTE] PIP-335: Oxia metadata support

2024-02-07 Thread Matteo Merli
I'm closing this vote after 48h with 4 binding +1s and 7 non-binding +1s Binding +1s: * Haiting * Hang * Enrico * Matteo Non-Binding +1s: * Dao Jun * Xiaoyu * Zike * Zixuan * Apurva * Kai * Dezhi Thanks everyone! Matteo -- Matteo Merli On Tue, Feb 6, 2024 at 7:20 PM Dezh

Re: [Discuss] Release Pulsar C++ Client 3.5.0

2024-02-07 Thread Matteo Merli
Heesung is finalizing the work for adding support for PIP-188, blue-green deployment support. It would be good to include in 1.5.0. -- Matteo Merli On Tue, Feb 6, 2024 at 11:33 PM Zike Yang wrote: > +1 > > Thanks for driving the release. > > BR, > Zike Yang > > On Wed

[VOTE] PIP-335: Oxia metadata support

2024-02-05 Thread Matteo Merli
nks Oxia: https://github.com/streamnative/oxia Oxia Java Client SDK: https://github.com/streamnative/oxia-java -- Matteo Merli

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

2024-02-05 Thread Matteo Merli
Thanks to everyone, moving to VOTE thread. -- Matteo Merli On Mon, Feb 5, 2024 at 11:13 AM Matteo Merli wrote: > > On Sun, Feb 4, 2024 at 11:55 AM Dave Fisher wrote: > >> 2. Other questions. If the base Pulsar will now depend on Oxia and no >> longer use Zookeeper?

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

2024-02-05 Thread Matteo Merli
On Sun, Feb 4, 2024 at 11:55 AM Dave Fisher wrote: > 2. Other questions. If the base Pulsar will now depend on Oxia and no > longer use Zookeeper? Or is Oxia an option? Will Oxia be included as a > Pulsar dependency in Pulsar convenience binaries? > It stated clearly in the proposal that: "It's

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

2024-02-03 Thread Matteo Merli
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? Seems like this has been > discussed elsewhere? > No, Dave, there was no "elsewhere" discussion. Because 12 people agree to the prop

[DISCUSS] PIP-335: Oxia metadata support

2024-01-31 Thread Matteo Merli
nks Oxia: https://github.com/streamnative/oxia Oxia Java Client SDK: https://github.com/streamnative/oxia-java -- Matteo Merli

Re: Status of "Oxia" in Apache ecosystem?

2024-01-22 Thread Matteo Merli
it useful * Once there are multiple "contributors" to the project, we plan to move the governance to ASF Oxia is definitely not a ZooKeeper proxy. It's a totally different technology. More info in the github repo: https://github.com/streamnative/oxia -- Matteo Merli On Mon, Jan 2

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

2023-12-25 Thread Matteo Merli
Since there seems to be agreement here, I'll proceed with the PR for removing the code. If there are volunteers that are willing to continue maintaining the Trino plugin, I'll be happy to help out in setting up the new repository and import the existing code. Thanks, Matteo -- Ma

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

2023-12-22 Thread Matteo Merli
Good point. I have created a PR here: https://github.com/apache/pulsar/pull/21795 We can always cherry-pick changes into the release branch, during the code freeze, with the appropriate precautions :) Matteo -- Matteo Merli On Fri, Dec 22, 2023 at 9:41 AM Lari Hotari wrote: > Do we tar

[DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

2023-12-22 Thread Matteo Merli
code from the last commit. Thoughts? -- Matteo Merli

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

2023-12-21 Thread Matteo Merli
+1 -- Matteo Merli On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi wrote: > +1 binding > > Nicolò Boschi > > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari ha > scritto: > > > +1 (binding) > > > > -Lari > > > > > > On Thu, 21 De

Re: [DISCUSS] PIP-324: Alpine Docker images

2023-12-13 Thread Matteo Merli
the Ubuntu base image can stay on the 3.0 LTS release branch for the entire LTS lifespan I would avoid supporting 2 images at the same time because it would make it very hard to properly test them both. -- Matteo Merli On Tue, Dec 12, 2023 at 8:57 PM Zixuan Liu wrote: > +1. > > It is a

Re: [DISCUSS] PIP-324: Alpine Docker images

2023-12-13 Thread Matteo Merli
-- Matteo Merli On Wed, Dec 13, 2023 at 8:20 AM Christophe Bornet wrote: > Thanks Matteo for bringing this subject. > > I share the concerns of Lari regarding the move from glibc to musl in > terms of security, performance, compatibility with the JVM. Extensive > performance

[DISCUSS] PIP-324: Alpine Docker images

2023-12-12 Thread Matteo Merli
Hello, I've created a new proposal to switch Pulsar base docker images from Ubuntu to Alpine Linux. Details and motivation in the PIP: https://github.com/apache/pulsar/pull/21716 Matteo -- Matteo Merli

Re: [VOTE] PIP-320: OpenTelemetry Scaffolding

2023-12-11 Thread Matteo Merli
+1 -- Matteo Merli On Mon, Dec 11, 2023 at 10:13 AM Apurva Telang wrote: > +1 (non-binding) > > On Mon, Dec 11, 2023 at 4:50 AM Lari Hotari wrote: > > > +1 (binding) > > > > -Lari > > > > On 2023/12/11 07:33:53 Asaf Mesika wrote: > > > Hi,

Re: [VOTE] PIP-322: Pulsar Rate Limiting Refactoring

2023-12-11 Thread Matteo Merli
+1 -- Matteo Merli On Mon, Dec 11, 2023 at 4:51 AM Lari Hotari wrote: > +1 (binding) > > -Lari > > On 2023/12/11 06:20:30 Lari Hotari wrote: > > Dear Pulsar community, > > > > I am starting a vote thread for "PIP-322: Pulsar Rate Limiting > Refactor

Re: [VOTE] PIP-315: Configurable max delay limit for delayed delivery

2023-11-29 Thread Matteo Merli
+1 (binding) -- Matteo Merli On Wed, Nov 29, 2023 at 9:38 AM Lari Hotari wrote: > +1 (binding) > > -Lari > > On 2023/11/15 03:59:46 Kevin Lu wrote: > > Hi All, > > > > This thread is to start a vote for PIP-315. > > > > PIP: https://github.com/a

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

2023-09-05 Thread Matteo Merli
+1 (binding) -- Matteo Merli On Mon, Aug 7, 2023 at 11:55 AM Heesung Sohn wrote: > Hi, > > I'd like to start a vote thread for the PIP-281. > https://github.com/apache/pulsar/pull/20748 > > Discussion : > https://lists.apache.org/thread/bdmx4qhn6hkoxm0xbtf67tq4kt5r8jmy > > Best, > Heesung >

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

2023-09-05 Thread Matteo Merli
-- Matteo Merli On Tue, Aug 8, 2023 at 9:56 PM Michael Marshall wrote: > Thanks for your proposal, Heesung. Sorry for my late response. Just > want to make a few points to hopefully improve the implementation. > Overall, I think this feature is absolutely the right direction for >

Re: [VOTE] Pulsar Client Python Release 3.3.0 Candidate 1

2023-08-28 Thread Matteo Merli
+1 binding - Checked signatures - Checked macos and linux wheel files. -- Matteo Merli On Sun, Aug 27, 2023 at 6:13 PM PengHui Li wrote: > OS: macOS Ventura Version 13.4.1 (c) (22F770820d) > Python: 3.11.4 > > +1 (binding) > > - Checked the signature > - Build whee

Re: [VOTE] PIP-264: Enhanced OTel-based metric system

2023-08-28 Thread Matteo Merli
+1 -- Matteo Merli On Mon, Aug 28, 2023 at 8:03 AM Hang Chen wrote: > +1 (binding) > > Thanks for your great proposal! > > Best, > Hang > > Asaf Mesika 于2023年8月28日周一 22:55写道: > > > > Hi, > > > > I'm very happy to start the vote

Re: [DISCUSS] Roll up project status for pulsar-helm-chart

2023-08-08 Thread Matteo Merli
of which one can tweek to its specific needs for productions environments. Since this thread got started, there was no one stepping up, so I guess your prevision was also correct :) and reinforces the idea that we should reduce a bit the scope and expectation for this Helm chart. -- Matteo Merli

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

2023-06-15 Thread Matteo Merli
itch to choose the existing metrics or the new ones. The dashboards will be updated and provided. At the same time, the best sure way to motivate users to switch or not adopt a platform is to stick with confusing/inconsistent APIs/Metrics. -- Matteo Merli On Wed, Jun 14, 2023 at 6:10 PM

Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system

2023-06-06 Thread Matteo Merli
Groups are useless unless there is some understanding of Bundles and Load. Isn't this thread the "discussion"? It has been open for more than a month to let people the time to read and provide feedback on the proposal -- Matteo Merli On Tue, Jun 6, 2023 at 10:00 AM Dave Fisher wr

Re: [VOTE] Pulsar Client Python Release 3.2.0 Candidate 1

2023-06-02 Thread Matteo Merli
+1 * Checked signature * Installed and tested with Mac & linux wheels Matteo -- Matteo Merli On Fri, Jun 2, 2023 at 7:36 AM PengHui Li wrote: > +1 (binding) > > - Checked the signature > - Install pulsar_client-3.2.0-cp311-cp311-macosx_10_15_universal2.whl > - Start

Re: [VOTE] Pulsar Release 3.0.0 Candidate 4

2023-05-01 Thread Matteo Merli
+1 Checked signatures, standalone & docker images. -- Matteo Merli On Sat, Apr 29, 2023 at 8:32 AM Hang Chen wrote: > +1 (binding) > > - Checksum and signatures > - Built from sources on MacOS (JDK 11 and Maven 3.8.6) > - Run rat check and check-binary-license on th

Re: [VOTE] Pulsar Release 3.0.0 Candidate 3

2023-04-26 Thread Matteo Merli
+1 Checked signatures, standalone & docker images. -- Matteo Merli On Tue, Apr 25, 2023 at 7:38 AM Christophe Bornet wrote: > This is the third release candidate for Apache Pulsar, version 3.0.0. > > It fixes the following issues: > https://github.com/apache/pulsar/miles

Re: [Question] [java client] CPU-intensive code on io threads

2023-03-16 Thread Matteo Merli
k, and serialization & compression are definitely part of that. The important part is to avoid any blocking operations. -- Matteo Merli On Thu, Mar 16, 2023 at 5:01 PM Andrey Yegorov wrote: > Hi, > > While looking through the code/thread dumps I noticed that decompression of &

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

2023-03-14 Thread Matteo Merli
+1 (binding) -- Matteo Merli On Tue, Mar 14, 2023 at 8:29 AM Asaf Mesika wrote: > Hi, > > I would like to start the vote on PIP-249: Pulsar website redesign. > > PIP link: https://github.com/apache/pulsar/issues/19611 > > You can read the discussion thread here: >

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 4

2023-03-10 Thread Matteo Merli
+1 (binding) -- Matteo Merli On Fri, Mar 10, 2023 at 7:44 AM Yunze Xu wrote: > Hi Zike, > > It's not a regression. This error applies for Python client 3.0.0 as > well. Before 3.0.0, the Python client cannot be interrupted by a > signal. I'd rather treat it as the cas

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 3

2023-02-22 Thread Matteo Merli
+1 bindind -- Matteo Merli On Fri, Feb 17, 2023 at 3:27 AM Yunze Xu wrote: > This is the 3rd release candidate for Apache Pulsar Client Python, > version 3.1.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-python/milestone/2?closed=1 > >

Re: [PROPOSAL] Roadmap for 3.0 release

2023-02-17 Thread Matteo Merli
Ups, I started from the release date I was meaning April for the RCs: * Tue - 2023-04-11 * Tue - 2023-04-18 - RC-2 * Tue - 2023-04-25 - RC-3 * Tue - 2023-05-02 - Announce 3.0 Release Sorry for the mixup! -- Matteo Merli On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher wrote: > +1. &g

[PROPOSAL] Roadmap for 3.0 release

2023-02-17 Thread Matteo Merli
testing. Since everyone also has other work duties and unexpected tasks that can pop up at any time, it will help to have redundancy in the release-management "team", so that we can release on the exact dates. Thanks, Matteo -- Matteo Merli

Re: [DISCUSS] Using jetty-client instead of async-http-client

2023-02-17 Thread Matteo Merli
lternatives are really not "async" and would cause a lot of performance regressions and other headaches. -- Matteo Merli On Thu, Feb 16, 2023 at 5:52 AM Asaf Mesika wrote: > Oh. I looked at the commits, it seems pretty active to me. > > > On Thu, Feb 16, 2023 at 3:31 P

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

2023-02-17 Thread Matteo Merli
Hi Haiting, We'll publish the LTS and end-of-life policy on the website, with the support dates for each release. -- Matteo Merli On Mon, Feb 13, 2023 at 6:27 PM Haiting Jiang wrote: > Hi Matteo, > > I noticed that 2.10 is not mentioned to be the first LTS version as > dis

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

2023-02-17 Thread Matteo Merli
Thanks everyone for voting. I'm closing the vote with 8 binding +1s and 2 non-binding +1s Binding: * Matteo * Nozomi * PengHui * Nicolò * Yunze * Hang * Michael * Enrico Non-Binding: * Zike * Mattison -- Matteo Merli On Mon, Feb 13, 2023 at 11:06 PM Enrico Olivelli wrote:

[VOTE] PIP-175: Extend time based release process

2023-02-08 Thread Matteo Merli
ssues are found. The last 1 week will be used for the voting process and for updating Pulsar website and the blog post announcing the release, which should (hopefully) happen on the scheduled day. -- Matteo Merli

Re: [VOTE] Pulsar Client C++ Release 3.1.2 Candidate 1

2023-02-08 Thread Matteo Merli
+1 -- Matteo Merli On Wed, Feb 8, 2023 at 12:28 AM Yunze Xu wrote: > > This is the first release candidate for Apache Pulsar Client C++, version > 3.1.2. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/issues?q=label%3Arelease%2F3.1.2 >

Re: Pulsar Cpp client release 3.1.2

2023-02-07 Thread Matteo Merli
+1 -- Matteo Merli On Tue, Feb 7, 2023 at 6:49 PM Yunze Xu wrote: > > Hi all, > > There is a serious OAuth2 authentication regression [1] for all > existing C++ client 3.x.y releases. I see many users tend to downgrade > to old versions like 2.10.2. This behavior is danger

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 2

2023-02-02 Thread Matteo Merli
+1 -- Matteo Merli On Thu, Feb 2, 2023 at 5:57 AM Yunze Xu wrote: > > This is the 2nd release candidate for Apache Pulsar Client Python, > version 3.1.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-python/milestone/2?closed=1 > > *** P

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 1

2023-02-01 Thread Matteo Merli
The wheels work fine (tested Mac & Linux) and the checksums are all correct, though the version is `3.1.0a1`. We need to remove `a1` for final release that are uploaded to PyPI -- Matteo Merli On Wed, Feb 1, 2023 at 1:00 AM Yunze Xu wrote: > > This is the 1st release candidate for Apa

[RESULT] [VOTE] Pulsar Client C++ Release 3.1.1 Candidate 2

2023-01-26 Thread Matteo Merli
Closing this vote with 3 binding +1s votes: * Matteo * Masahiro * Yunze Thanks, Matteo -- Matteo Merli On Wed, Jan 25, 2023 at 3:36 AM Yunze Xu wrote: > > +1 (binding) > > * verify checksum and signatures > * build from source (Ubuntu 20.04 WSL) > * verify ar

[VOTE] Pulsar Client C++ Release 3.1.1 Candidate 2

2023-01-23 Thread Matteo Merli
g PGP keys you use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source package, and follow the README to compile and test. -- Matteo Merli

Re: [VOTE] Pulsar Client C++ Release 3.1.1 Candidate 1

2023-01-23 Thread Matteo Merli
Thanks, I'm canceling this vote, and I'll send out an RC-2 quickly. -- Matteo Merli On Mon, Jan 23, 2023 at 5:42 AM Yunze Xu wrote: > > It makes sense to me, I have cherry-picked it to branch-3.1 now. I > think we need to open another candidate for it. > > Thanks, &

Re: [DISCUSS] Code freeze for Pulsar 2.12

2023-01-19 Thread Matteo Merli
On Thu, Jan 19, 2023 at 3:11 PM Christophe Bornet wrote: > It's great that we released Pulsar 2.11. It has taken quite some time to > stabilize the release branch and now we have more than 5 months of awesome > features and commits on the master branch that would benefit a lot to our > users. That

[VOTE] Pulsar Client C++ Release 3.1.1 Candidate 1

2023-01-19 Thread Matteo Merli
g PGP keys you use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source package, and follow the README to compile and test. -- Matteo Merli

Pulsar Cpp client 3.1.1 release

2023-01-19 Thread Matteo Merli
t-cpp/pull/146, but it still needs to be released. This problem is serious enough that I believe we should get a patch out ASAP. I'll start the work on a 3.1.1 patch release. Matteo -- Matteo Merli

Re: [VOTE] Pulsar Client Python Release 3.0.0 Candidate 3

2022-12-16 Thread Matteo Merli
+1 * From candidate-2 I checked the source tarball for licenses, notice and no binaries included. -- Matteo Merli On Thu, Dec 15, 2022 at 11:30 PM Yunze Xu wrote: > > This is the third release candidate for Apache Pulsar Client Python, > version 3.0.0. > > It fixes the f

Re: Remove unexpected created https://github.com/apache/pulsar-pulsar-client-cpp?

2022-12-15 Thread Matteo Merli
Yes, it was my mistake. I couldn't find a way to do it in Gitbox though. :/ Probably it does require an INFRA ticket. -- Matteo Merli On Thu, Dec 15, 2022 at 3:58 PM tison wrote: > > I found this repo: https://github.com/apache/pulsar-pulsar-client-cpp > > It seems to be cr

Re: [VOTE] Pulsar Client Python Release 3.0.0 Candidate 2

2022-12-14 Thread Matteo Merli
+1 Great work! Checked: * Signatures * Wheel file on Mac ARM, publishing and consuming messages * Wheel file on Alpine Linux, publishing and consuming messages -- Matteo Merli On Wed, Dec 14, 2022 at 7:52 AM Yunze Xu wrote: > > This is the second release candidate for Apache

Re: [VOTE] Pulsar Client Python Release 3.0.0 Candidate 1

2022-12-13 Thread Matteo Merli
Hi Yunze, I think we need to fix the Py client version "3.0.0a1" --> "3.0.0" in https://github.com/apache/pulsar-client-python/blob/main/version.txt -- Matteo Merli On Tue, Dec 13, 2022 at 8:10 PM Yunze Xu wrote: > > This is the first release candidate fo

Re: [DISCUSS] Release Nodejs Client 1.8.0

2022-12-13 Thread Matteo Merli
nt will depend on the Pulsar C++ Client 3.1.0. > > Please remind me if you have any important fixes that need to be > included in 1.8.0 > > [0] https://github.com/apache/pulsar-client-node/compare/v1.7.0...master > > BR, > Zike Yang > -- -- Matteo Merli

Re: [VOTE] Pulsar Client C++ Release 3.1.0 Candidate 3

2022-12-01 Thread Matteo Merli
+1 binding. Checked: * Source compiling and tested with perf producer * Signatures * RPM & Deb packages installing -- Matteo Merli On Thu, Dec 1, 2022 at 5:57 PM Zike Yang wrote: > > This is the third release candidate for Apache Pulsar Client C++, > version 3.1.0. >

Re: [DISCUSS] Remove "triage" series labels?

2022-11-17 Thread Matteo Merli
+1 Good suggestion -- Matteo Merli On Thu, Nov 17, 2022 at 7:32 AM tison wrote: > > Hi, > > When squashing issue backlog, I noticed there're a number of "legacy" tags > in series "traige/week-x". > > It seems the initiative has been halted and

Re: [Vote] PIP-220 TransferShedder (only for PIP-192 New Broker Load Balancer)

2022-11-17 Thread Matteo Merli
+1 -- Matteo Merli On Tue, Nov 15, 2022 at 3:20 PM Heesung Sohn wrote: > > Dear Pulsar Community, > > Please review and vote on this PIP. > > PIP link: https://github.com/apache/pulsar/issues/18215 > > Thank you, > -Heesung

[ANNOUNCE] Apache Pulsar Client C++ 3.0.0 released

2022-11-16 Thread Matteo Merli
possible. Regards, The Pulsar Team -- Matteo Merli

Re: Data quality problem

2022-11-11 Thread Matteo Merli
for maintaining apps using Pulsar. It's also bad PR because > >> then incidents are associated with Pulsar, even though the business > might > >> not understand that the data problem wasn't necessarily caused by > Pulsar. > >> > >> What's the right way for us to address this problem? > >> > >> -- > >> Devin Bost > >> Sent from mobile > >> Cell: 801-400-4602 > >> > > > > > > -- > > > > Elliot West > > > > Senior Platform Engineer > > > > elliot.w...@streamnative.io > > > > streamnative.io > > > > <https://github.com/streamnative> > > <https://www.linkedin.com/company/streamnative> > > <https://twitter.com/streamnativeio> > > -- -- Matteo Merli

[RESULT] [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 3

2022-10-28 Thread Matteo Merli
Thank you for testing this release. Closing the vote 3 binding +1s: * Matteo * PengHui * Hang 3 non binding +1s: * Zike * Kai * Yunze -- Matteo Merli On Tue, Oct 25, 2022 at 11:16 AM Hang Chen wrote: > > +1 (binding) > > - Verified checksum and signatures > - Build from

[VOTE] Pulsar Client C++ Release 3.0.0 Candidate 3

2022-10-21 Thread Matteo Merli
n the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source package, and follow the README to compile and test. -- Matteo Merli

Re: [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 2

2022-10-14 Thread Matteo Merli
is merged. -- Matteo Merli On Thu, Oct 13, 2022 at 10:26 AM Matteo Merli wrote: > > This is the first release candidate for Apache Pulsar Client C++, version > 3.0.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/1?closed=1 > > *** Plea

Re: [DISCUSS] Release Pulsar Client Node.js 3.0.0

2022-10-14 Thread Matteo Merli
w which c++ client is actually underneath. -- Matteo Merli On Fri, Oct 14, 2022 at 1:47 AM Baodi Shi wrote: > > Hi, We're releasing C++ and python 3.0.0 client, Node.js Client is also built > on C++, and I'd like to discuss whether to start working on Node.js Client > 3.

[VOTE] Pulsar Client C++ Release 3.0.0 Candidate 2

2022-10-13 Thread Matteo Merli
n the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source package, and follow the README to compile and test. -- Matteo Merli

Re: [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 1

2022-10-13 Thread Matteo Merli
Canceling this vote. I'll send out the RC2 in a bit. -- Matteo Merli On Wed, Oct 12, 2022 at 9:08 AM Matteo Merli wrote: > > On Wed, Oct 12, 2022 at 9:02 AM Matteo Merli wrote: > > Honestly, I don't know why it was ever documented in the README. > > BTW: it turns o

Re: [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 1

2022-10-12 Thread Matteo Merli
On Wed, Oct 12, 2022 at 9:02 AM Matteo Merli wrote: > Honestly, I don't know why it was ever documented in the README. BTW: it turns out it was me who added these scripts in the README, in 2017 🤦 -- Matteo Merli

Re: [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 1

2022-10-12 Thread Matteo Merli
-- Matteo Merli On Tue, Oct 11, 2022 at 7:35 PM Michael Marshall wrote: > > I am getting an error when building from the downloaded source tarball > while following the instructions in the README. I get this error: > > $ ./docker-build.sh > fatal: not a git repository (or

  1   2   3   4   >