[NOTICE] CFP Extended - Pulsar Summit North America 2023

[tison]

Hi, devs and users,

The CFP for the Pulsar Summit North America 2023[1][2] has been extended to
Friday, July 21!

Top reasons to speak this year:
* Your headshot, bio and session featured on the Pulsar Summit website.
* Your session will be promoted on YouTube, Twitter and LinkedIn.
* The opportunity to share your knowledge and engage with the vibrant
Pulsar community in person! Past Pulsar Summits featured speakers from
Databricks, Splunk, Intuit, Verizon Media, and more!

Important Dates:
* CFP closes (extension): Friday, July 21st, 2023
* Speaker notifications sent: Friday, July 28th, 2023
* Schedule announcement: Friday, August 4th, 2023

Pulsar Summit North America is coming back to Hotel Nikko in San Francisco,
California on Wednesday, October 25th, 2023.

Welcome to submit your CFP at [1].

Best,
tison.

[1] https://sessionize.com/pulsar-summit-north-america-2023/
[2] https://lists.apache.org/thread/s8m33ovxgmmofvpdc74jl4bfhg2m6820

[DISCUSS] PIP-282: Change definition of the recently joined consumers position

[Yuri Mizushima]

Hi, Pulsar Community

I opened a new PIP design PR.
I am looking forward to your feedback.

https://github.com/apache/pulsar/pull/20776


Motivation

Key_Shared has a mechanism called the "recently joined consumers" to keep 
message ordering.
However, currently, it doesn't care about some corner cases.

1. [issue-1] The race condition in the "recently joined consumers", where 
consumers can be added before finishing reading and dispatching messages from 
ledgers.
2. [issue-2] Messages could be added to messagesToRedeliver without 
consumer-side operations such as unacknowledgement.

We should care about these cases in Key_Shared subscription.

Thanks,

--
Yuri Mizushima
yumiz...@yahoo-corp.jp

Re: [VOTE] PIP-280 : Refactor CLI Argument Parsing Logic for Measurement Units using JCommander's custom converter

[Qiang Zhao]

+1(binding)

Best,
Mattison

On 2023/07/07 09:25:22 Joo Hyuk Kim wrote:
> Hi community,
> 
> This PIP has received a couple of approvals in github PR link [1]
> So I thought it's time to vote.
> 
> ## Motivation
> 
> In the current Pulsar codebase, the logic to parse CLI arguments for
> measurement units like time and bytes is
> 
> scattered across various CLI classes. Each value read has its distinct
> parsing implementation, leading to a lack of code
> 
> reuse.
> 
> 
> ## Goals
> 
> 
> This PIP is to refactor the argument parsing logic to leverage the
> `@Parameter.converter`
> 
> functionality provided by JCommander [link 3]. This will isolate the
> measurement-specific parsing logic and increase
> 
> code
> 
> reusability.
> 
> 
> ### In Scope
> 
> 
> - Refactor all `Cmd` classes to utilize the converter functionality of
> JCommander. This will streamline the parsing
> 
>   logic and simplify the codebase.
> 
> - Refer to bottom section "Concrete Example", before "Links"
> 
> - Or on-going PR with small use case in
> https://github.com/apache/pulsar/pull/20663
> 
> 
> ## links
> 
> 
> [1] PR : https://github.com/apache/pulsar/pull/20691
> 
> 
> 
> Best regards,
> 
> JooHyukKim (Vince)
> 

RE: Re: [VOTE] PIP-280 : Refactor CLI Argument Parsing Logic for Measurement Units using JCommander's custom converter

[mattisonchao]

+1(binding)

Mattison
On 10 Jul 2023 at 19:55 +0800, Joo Hyuk Kim , wrote:
> Thanks,
> JooHyuk.
>
> On 2023/07/10 00:24:20 Zili Chen wrote:
> > +1 (non-binding)
> >
> > On 2023/07/07 09:25:22 Joo Hyuk Kim wrote:
> > > > Hi community,
> > > >
> > > > This PIP has received a couple of approvals in github PR link [1]
> > > > So I thought it's time to vote.
> > > >
> > > > ## Motivation
> > > >
> > > > In the current Pulsar codebase, the logic to parse CLI arguments for
> > > > measurement units like time and bytes is
> > > >
> > > > scattered across various CLI classes. Each value read has its distinct
> > > > parsing implementation, leading to a lack of code
> > > >
> > > > reuse.
> > > >
> > > >
> > > > ## Goals
> > > >
> > > >
> > > > This PIP is to refactor the argument parsing logic to leverage the
> > > > `@Parameter.converter`
> > > >
> > > > functionality provided by JCommander [link 3]. This will isolate the
> > > > measurement-specific parsing logic and increase
> > > >
> > > > code
> > > >
> > > > reusability.
> > > >
> > > >
> > > > ### In Scope
> > > >
> > > >
> > > > - Refactor all `Cmd` classes to utilize the converter functionality of
> > > > JCommander. This will streamline the parsing
> > > >
> > > > logic and simplify the codebase.
> > > >
> > > > - Refer to bottom section "Concrete Example", before "Links"
> > > >
> > > > - Or on-going PR with small use case in
> > > > https://github.com/apache/pulsar/pull/20663
> > > >
> > > >
> > > > ## links
> > > >
> > > >
> > > > [1] PR : https://github.com/apache/pulsar/pull/20691
> > > >
> > > >
> > > >
> > > > Best regards,
> > > >
> > > > JooHyukKim (Vince)
> > > >
> >

Re: Request to contribute to Apache Pulsar JIRA maintenance and documentation

[Jun Ma]

Hi Yuvaraj,

Thanks for your willingness to contribute to Pulsar.

To answer your question about the client docs in short - No, you don't need to 
replicate. They are not excluded but restructured in 3.0 according to PIP-228 
[1]. This restructuring aims to improve the developer experience by helping 
them get started with bite-sized info [2] and build a solid model to make the 
doc set easier to scale.

Feel free to continuously improve the docs!

[1]: 
https://github.com/apache/pulsar/issues/18822https://github.com/apache/pulsar/issues/18822
[2]: https://pulsar.apache.org/docs/3.0.x/client-libraries-java/

Best,
Jun


From: Yuvaraj Madeshwaran 
Sent: Tuesday, July 11, 2023 3:34
To: Dave Fisher ; li...@apache.org 
Cc: dev@pulsar.apache.org 
Subject: Re: Request to contribute to Apache Pulsar JIRA maintenance and 
documentation

Hi Liuyu & Dave,

Thanks for sharing the information.

I have gone through the documentation of Apache Pulsar and found that
the Version 3.0.X documentation for Java client is not complete in the
link, https://pulsar.apache.org/docs/3.0.x/client-libraries-java-use/

It's missing documentation for a couple of topics as below,
1. TableView
2. Schema
3. Authentication
4. Cluster Level failover

Documentation for the same exists in version below in the link
https://pulsar.apache.org/docs/2.11.x/client-libraries-java/

Can you please suggest to me, Do we need to replicate the
documentation in Version 3 ? If yes, Shall I fork a new branch, make
changes in it ?

Thanks in advance!

Regards,
Yuvaraj Madheswaran

Re: Request to contribute to Apache Pulsar JIRA maintenance and documentation

[Yuvaraj Madeshwaran]

Hi Liuyu & Dave,

Thanks for sharing the information.

I have gone through the documentation of Apache Pulsar and found that
the Version 3.0.X documentation for Java client is not complete in the
link, https://pulsar.apache.org/docs/3.0.x/client-libraries-java-use/

It's missing documentation for a couple of topics as below,
1. TableView
2. Schema
3. Authentication
4. Cluster Level failover

Documentation for the same exists in version below in the link
https://pulsar.apache.org/docs/2.11.x/client-libraries-java/

Can you please suggest to me, Do we need to replicate the
documentation in Version 3 ? If yes, Shall I fork a new branch, make
changes in it ?

Thanks in advance!

Regards,
Yuvaraj Madheswaran

On Thu, Jul 6, 2023 at 9:10 PM Dave Fisher  wrote:
>
> Adding the OP who is not subscribed.
>
> Sent from my iPhone
>
> > On Jul 6, 2023, at 6:35 PM, Yu  wrote:
> >
> > Hi Yuvaraj,
> >
> > Thank you for your willingness to contribute to the Pulsar documentation!
> >
> > Feel free to select your desired issues from
> > https://github.com/apache/pulsar/issues?q=is%3Aopen+is%3Aissue+label%3Adoc-required
> > .
> >
> > You can find the documentation contribution guide at
> > https://pulsar.apache.org/contribute/document-intro/, and don't hesitate to
> > reach out to me for any assistance or to have your pull requests reviewed.
> >
> > Yu
> >
> >
> >> On Fri, Jul 7, 2023 at 8:50 AM Yuvaraj Madeshwaran 
> >> wrote:
> >>
> >> Dear Apache Pulsar Foundation,
> >>
> >> I am writing to express my interest in contributing to the JIRA dashboard
> >> maintenance and documentation of Apache Pulsar Github repos. I have
> >> developed a deep understanding of the software and JIRA. I am also
> >> proficient in writing technical documentation.
> >>
> >> I believe that my skills and experience would be a valuable asset to the
> >> Apache Pulsar project. I am a highly motivated and detail-oriented
> >> individual, and I am always willing to go the extra mile. I am also a quick
> >> learner, and I am always eager to learn new things.
> >>
> >> I am particularly interested in contributing to the following areas:
> >> JIRA board maintenance
> >> Documentation
> >> Testing
> >>
> >> I am available to contribute on a part-time basis. I have attached my
> >> resume for your review. I have also included a link to my GitHub profile
> >> https://github.com/yuvarajmms .
> >>
> >> Thank you for your time and consideration. I look forward to hearing from
> >> you soon.
> >>
> >> Sincerely,
> >> Yuvaraj Madheswaran
> >>
>

Re: [DISCUSS] Move superuser/tenantAdmin checks to AuthorizationService from AuthorizationProvider

[Zixuan Liu]

Hi Jiwei,

Sorry, my title seems confusing. I just refactor the
PulsarAuthorizationProvider by moving superuser/tenantAdmin checks to
AuthorizationService from PulsarAuthorizationProvider.

IMO, the superuser and tenant admin are built-in in the Pulsar, not
the third party, we also provide the isSuperUser and isTenantAdmin
methods used for fine-grained control in the AuthorizationProvider, so
I think to move superuser/tenantAdmin checks to AuthorizationService
from PulsarAuthorizationProvider.

Thanks,
Zixuan

guo jiwei  于2023年7月10日周一 16:07写道：
>
> Hi Zixuan,
>   From the perspective of interface implementation, for example, for
> `allowTopicOperationAsync`,
>   we need to determine whether the role is admin or super user in
> PulsarAuthorizationProvider, not in AuthorizationService.
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Fri, Jul 7, 2023 at 5:20 PM Zixuan Liu  wrote:
>
> > Hello everyone,
> >
> > When a role wants to use the resource, the role needs to have resource
> > permissions.
> >
> > The process is to first check whether the role is the superuser or
> > tenant administrator. If yes, operations are allowed. Otherwise, check
> > the policies stored in zk.
> >
> > Right now, we have the AuthorizationService and AuthorizationProvider,
> > the AuthorizationService wraps the AuthorizationProvider call. When
> > you check the code, you will find that both classes have the
> > superuser/tenantAdmin checks in certain places, this may cause
> > confusion when developing the custom AuthorizationProvider, so I
> > suggest unifying superuser/tenantAdmin checks in the
> > `AuthorizationService`, and then the `AuthorizationProvider` only
> > needs to consider their business permissions.
> >
> > I created a PR a while ago, you can check it out:
> > https://github.com/apache/pulsar/pull/20145,
> >
> > Thanks,
> > Zixuan
> >

RE: Re: [VOTE] PIP-280 : Refactor CLI Argument Parsing Logic for Measurement Units using JCommander's custom converter

[Joo Hyuk Kim]

Thanks,
JooHyuk.

On 2023/07/10 00:24:20 Zili Chen wrote:
> +1 (non-binding)
>
> On 2023/07/07 09:25:22 Joo Hyuk Kim wrote:
> > Hi community,
> >
> > This PIP has received a couple of approvals in github PR link [1]
> > So I thought it's time to vote.
> >
> > ## Motivation
> >
> > In the current Pulsar codebase, the logic to parse CLI arguments for
> > measurement units like time and bytes is
> >
> > scattered across various CLI classes. Each value read has its distinct
> > parsing implementation, leading to a lack of code
> >
> > reuse.
> >
> >
> > ## Goals
> >
> >
> > This PIP is to refactor the argument parsing logic to leverage the
> > `@Parameter.converter`
> >
> > functionality provided by JCommander [link 3]. This will isolate the
> > measurement-specific parsing logic and increase
> >
> > code
> >
> > reusability.
> >
> >
> > ### In Scope
> >
> >
> > - Refactor all `Cmd` classes to utilize the converter functionality of
> > JCommander. This will streamline the parsing
> >
> >   logic and simplify the codebase.
> >
> > - Refer to bottom section "Concrete Example", before "Links"
> >
> > - Or on-going PR with small use case in
> > https://github.com/apache/pulsar/pull/20663
> >
> >
> > ## links
> >
> >
> > [1] PR : https://github.com/apache/pulsar/pull/20691
> >
> >
> >
> > Best regards,
> >
> > JooHyukKim (Vince)
> >
>

Re: [DISCUSS] About cherry-picking `Use Ubuntu 22.04 for Pulsar images (#20475)`

[asn]

Updating ubuntu 22.04 can fix some CVE issues. Since python client has been
removed, we don't need to build python client in pulsar docker
building stage. Instead, we can install python-client from pypi directly. I
created this PR to fix this issue.
https://github.com/apache/pulsar/pull/20770

Dave Fisher  于2023年6月30日周五 13:23写道：

> We’ve been seeing this too.
>
> The issue is that the docker build gets it mirror list from Ubuntu, some
> of the mirrors are bad, and output reveals that the patching of the
> original ubuntu image requires every patch and these eventually stall. We
> are working on improvements to mirror selection.
>
> I think a better approach is to make a base image on a schedule or on
> demand. Each docker image needed can start from that saved “ready” image,
> install the JDK, and then the Pulsar components.
>
> Best,
> Dave
>
> Sent from my iPhone
>
> > On Jun 29, 2023, at 9:41 PM, asn  wrote:
> >
> > Hi, everyone
> >
> > Since this PR cherry-picked to branch-2.11, the Docker image build
> failed.
> > The reason is this script `
> >
> https://github.com/apache/pulsar/blob/branch-2.10/docker/pulsar/scripts/install-pulsar-client.sh`
> 
> ,
> > ubuntu 20.04 python version is 3.8, but 22.04 python version is 3.10.
> >
> > Furthermore, branch-3.0 can build success because it removes cpp and
> python
> > build in this branch and master. Currently, python and cpp clients are
> > removed from pulsar, so why not cherry-pick this PR (
> > https://github.com/apache/pulsar/pull/17881) to 2.10 and 2.11 branch?
> >
> > Zixuan Liu  于2023年6月28日周三 19:02写道：
> >
> >> +1, but we need to remove the pulsar client changes.
> >>
> >> Thanks,
> >> Zixuan
> >>
> >> Zike Yang  于2023年6月28日周三 16:24写道：
> >>>
> >>> +1 for cherry-picking the PR.
> >>>
> >>> Thanks,
> >>> Zike Yang
> >>>
> >>> On Wed, Jun 28, 2023 at 4:22 PM  wrote:
> 
>  Agree with cherry-pick PR.
> 
>  Best
>  Mattison
>  On 26 Jun 2023 at 17:10 +0800, guo jiwei ,
> >> wrote:
> > Hello community:
> > For this patch Use Ubuntu 22.04 for Pulsar images
> > , we need some ideas
> >> about
> > cherry-picking to other branches.
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >>
> >
> >
> > --
> > yaalsn
>
>

-- 
yaalsn

[ANNOUNCE] Apache Pulsar Node.js client 1.9.0 released

[Baodi Shi]

The Apache Pulsar team is proud to announce Apache Pulsar Node.js
client version 1.9.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

For Pulsar Node.js client release details and downloads, visit:
https://www.npmjs.com/package/pulsar-client

Release Notes are at:
https://github.com/apache/pulsar-client-node/releases

We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team

[ANNOUNCE] Apache Pulsar Go Client 0.11.0 released

[Zike Yang]

The Apache Pulsar team is proud to announce Apache Pulsar Go Client
version 0.11.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

For Pulsar release details and downloads, visit:
https://github.com/apache/pulsar-client-go/releases/tag/v0.11.0

Release Notes are at:
https://github.com/apache/pulsar-client-go/blob/master/CHANGELOG.md

We would like to thank the contributors that made the release possible.

Regards,
The Pulsar Team

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

[Zike Yang]

Close the vote with 3(+1 binding) 1(+1 non-binding) 0(-1)

binding:
   - Penghui
   - Jiwei Guo
   - Mattison

non-binding
   - Rui Fu

Thanks,
Zike Yang

On Mon, Jul 10, 2023 at 3:40 PM  wrote:
>
> +1 (binding)
>
> • Downloaded the source code.
> • Built from the source code on macOS.
> • Ran make test.
> • Ran all of the examples with pulsar-3.0.0.
>
>
> Best,
> Mattison
> On 10 Jul 2023 at 11:37 +0800, Rui Fu , wrote:
> > +1
> >
> > - verified checksum and signature
> > - run producer and consumer examples
> >
> > Best,
> >
> > Rui Fu
> > On Jul 4, 2023 at 17:22 +0800, Zike Yang , wrote:
> > > Hi everyone,
> > > Please review and vote on the release candidate #1 for the version
> > > 0.11.0, as follows:
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > This is the first release candidate for Apache Pulsar Go client, version 
> > > 0.11.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar-client-go/milestone/13?closed=1
> > >
> > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this 
> > > release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > >
> > > Please download these packages and review this release candidate:
> > > - Review release notes: 
> > > https://github.com/apache/pulsar-client-go/pull/1048
> > > - Download the source package (verify shasum, and asc) and follow the
> > > README.md to build and run the pulsar-client-go.
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > > Source file:
> > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.11.0-candidate-1/
> > >
> > > The tag to be voted upon:
> > > v0.11.0
> > > https://github.com/apache/pulsar-client-go/tree/v0.11.0-candidate-1
> > >
> > > SHA-512 checksums:
> > > 72cf0f71c82095f0d412ff15b35e32c56f118ec7f297ad662073c14786fead0a416d7b1a8b8caa890b76bd722cba1734e52fd4f53ee3daa793cb5a7915e5fb32
> > > apache-pulsar-client-go-0.11.0-src.tar.gz

Re: [VOTE] Pulsar Node.js Client Release 1.9.0 Candidate 1

[Baodi Shi]

Close the vote with 3(+1 binding) 1(+1 non-binding) 0(-1)

binding:

   - Masahiro
   - Yunze
   - Penghui


non-binding

   - Hideaki



Thanks,
Baodi Shi


On Jul 10, 2023 at 09:34:21, PengHui Li  wrote:

> +1(binding)
>
> - Install from npm
> - Run the produce and consume example [1]
>
> Regards,
> Penghui
>
> [1]
>
> https://github.com/apache/pulsar-client-node/tree/v1.9.0-rc.1#getting-started
>
> On Fri, Jul 7, 2023 at 7:32 PM Yunze Xu  wrote:
>
> +1 (binding)
>
>
> - Verified checksum and signature
>
> - Build from source on macOS m1 with Node.js v20.4.0
>
> - Run basic e2e examples
>
>
> Two additional notes:
>
> 1. You should use https://downloads.apache.org/pulsar/KEYS instead of
>
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> 2. When building from the TAR source, you need to modify
>
> `pkg/mac/common.sh`. Change `ROOT_DIR=$(git rev-parse
>
> --show-toplevel)` to `ROOT_DIR=$PWD`.
>
>
> Thanks,
>
> Yunze
>
>
> On Fri, Jul 7, 2023 at 10:28 AM Masahiro Sakamoto
>
>  wrote:
>
> >
>
> > +1 (binding)
>
> >
>
> > - verified checksum and signature
>
> > - confirmed that the build was successful
>
> > - ran produce/consume
>
> >
>
> > Regards,
>
> >
>
> > Masahiro Sakamoto
>
> > Yahoo Japan Corp.
>
> > E-mail: massa...@yahoo-corp.jp
>
>
>

Re: [DISCUSS] Move superuser/tenantAdmin checks to AuthorizationService from AuthorizationProvider

[guo jiwei]

Hi Zixuan,
  From the perspective of interface implementation, for example, for
`allowTopicOperationAsync`,
  we need to determine whether the role is admin or super user in
PulsarAuthorizationProvider, not in AuthorizationService.

Regards
Jiwei Guo (Tboy)


On Fri, Jul 7, 2023 at 5:20 PM Zixuan Liu  wrote:

> Hello everyone,
>
> When a role wants to use the resource, the role needs to have resource
> permissions.
>
> The process is to first check whether the role is the superuser or
> tenant administrator. If yes, operations are allowed. Otherwise, check
> the policies stored in zk.
>
> Right now, we have the AuthorizationService and AuthorizationProvider,
> the AuthorizationService wraps the AuthorizationProvider call. When
> you check the code, you will find that both classes have the
> superuser/tenantAdmin checks in certain places, this may cause
> confusion when developing the custom AuthorizationProvider, so I
> suggest unifying superuser/tenantAdmin checks in the
> `AuthorizationService`, and then the `AuthorizationProvider` only
> needs to consider their business permissions.
>
> I created a PR a while ago, you can check it out:
> https://github.com/apache/pulsar/pull/20145,
>
> Thanks,
> Zixuan
>

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

[mattisonchao]

+1 (binding)

• Downloaded the source code.
• Built from the source code on macOS.
• Ran make test.
• Ran all of the examples with pulsar-3.0.0.


Best,
Mattison
On 10 Jul 2023 at 11:37 +0800, Rui Fu , wrote:
> +1
>
> - verified checksum and signature
> - run producer and consumer examples
>
> Best,
>
> Rui Fu
> On Jul 4, 2023 at 17:22 +0800, Zike Yang , wrote:
> > Hi everyone,
> > Please review and vote on the release candidate #1 for the version
> > 0.11.0, as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > This is the first release candidate for Apache Pulsar Go client, version 
> > 0.11.0.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar-client-go/milestone/13?closed=1
> >
> > Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> >
> > Please download these packages and review this release candidate:
> > - Review release notes: https://github.com/apache/pulsar-client-go/pull/1048
> > - Download the source package (verify shasum, and asc) and follow the
> > README.md to build and run the pulsar-client-go.
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Source file:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.11.0-candidate-1/
> >
> > The tag to be voted upon:
> > v0.11.0
> > https://github.com/apache/pulsar-client-go/tree/v0.11.0-candidate-1
> >
> > SHA-512 checksums:
> > 72cf0f71c82095f0d412ff15b35e32c56f118ec7f297ad662073c14786fead0a416d7b1a8b8caa890b76bd722cba1734e52fd4f53ee3daa793cb5a7915e5fb32
> > apache-pulsar-client-go-0.11.0-src.tar.gz