Re: [DISCUSS] Release Pulsar 2.7.4

[guo jiwei]

I have pushed out some fixes in https://github.com/apache/pulsar/pull/13243
After the tests get passed, I will send out the RC-1 VOTE for 2.7.4

Regards
Jiwei Guo (Tboy)


On Sun, Dec 12, 2021 at 3:11 PM PengHui Li  wrote:

> Just put an update here. We have done the PR cherry-picking
>
> https://github.com/apache/pulsar/commits/branch-2.7
>
> And most of the integration tests are fixed due to the docker image issue
> or the testcontainer issue, now some integration tests get passed, but some
> are not.
> And there are some failed tests, maybe a flaky test, we need to ensure it's
> not a regression.
>
> We are continuing on the test part.
>
> Penghui
>
>
>
> On Sat, Dec 11, 2021 at 5:36 PM PengHui Li  wrote:
>
> > Hi Michael,
> >
> > +1,
> >
> > Thanks for the great work.
> > We will continue on the PR cherry-picking and the release process to make
> > sure the urgent release can be done ASAP.
> >
> > Penghui
> >
> > On Sat, Dec 11, 2021 at 3:42 PM Michael Marshall 
> > wrote:
> >
> >> Given the log4j CVE, we should work to release 2.7.4.
> >>
> >> I started preparing the release today by cherry-picking merged PRs
> >> that have the `release/2.7.4` label but have not yet been
> >> cherry-picked to `branch-2.7` [0]. There are still 37 PRs that have
> >> not been cherry picked. I think it will take too long to cherry pick
> >> all of these commits, as many have conflicts, and we should prioritize
> >> releasing 2.7.4. The main commits that we should get cherry-picked
> >> before creating the git tag are any labeled with `component/security`.
> >> There are only a few remaining commits to cherry pick. Please let me
> >> know if you think any other commits ought to be cherry-picked.
> >>
> >> The earliest I'll be able to build the release is Monday. If we need
> >> to start sooner, perhaps someone else will be available to manage this
> >> urgent release.
> >>
> >> Thanks,
> >> Michael
> >>
> >> [0] -
> >>
> https://github.com/apache/pulsar/pulls?page=2&q=label%3Arelease%2F2.7.4+sort%3Acreated-asc+is%3Apr+-label%3Acherry-picked%2Fbranch-2.7
> >> [1] -
> >>
> https://github.com/apache/pulsar/pulls?q=label%3Arelease%2F2.7.4+sort%3Acreated-asc+is%3Apr+-label%3Acherry-picked%2Fbranch-2.7+label%3Acomponent%2Fsecurity
> >>
> >>
> >> On Thu, Dec 9, 2021 at 4:03 PM Neng Lu  wrote:
> >> >
> >> > +1
> >> >
> >> > On 2021/12/09 15:29:55 Michael Marshall wrote:
> >> > > Hello Pulsar Community,
> >> > >
> >> > > I'd like to propose that we release 2.7.4. We have merged several
> >> > > important fixes since we released 2.7.3 in August.
> >> > >
> >> > > I am happy to volunteer to be the release manager.
> >> > >
> >> > > Here [0] you can find the list of 36 commits cherry-picked to
> >> > > branch-2.7 since 2.7.3 release. It looks like there are more PRs
> >> > > labeled with `release/2.7.4` than commits cherry-picked, so I will
> >> > > need to work on cherry-picking those before we can create the tag
> for
> >> > > the release [1].
> >> > >
> >> > > Also, I see 3 open PRs labeled with `release/2.7.4`. I'll follow up
> on
> >> > > each of those PRs to see if they will be completed soon.
> >> > >
> >> > > Thanks,
> >> > > Michael
> >> > >
> >> > > [0] - https://github.com/apache/pulsar/compare/v2.7.3...branch-2.7
> >> > > [1] -
> >>
> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.7.4
> >> > >
> >>
> >
>

Re: [ANNOUNCE] New Committer: Marvin Cai

[guo jiwei]

Congratulations Marvin!


Regards
Jiwei Guo (Tboy)


On Tue, Dec 14, 2021 at 3:44 PM Yu  wrote:

> Congratulations Marvin!
>
> On Tue, Dec 14, 2021 at 8:42 AM Guangning E  wrote:
>
> > Configrats!
> >
> > Thanks,
> > Guangning
> >
> > Huanli Meng  于2021年12月14日周二 08:34写道：
> >
> > > Congratulations Marvin!
> > >
> > > BR//Huanli
> > >
> > > > On Dec 13, 2021, at 5:46 PM, linlin  wrote:
> > > >
> > > > The Apache Pulsar Project Management Committee (PMC) has invited
> Marvin
> > > Cai
> > > > https://github.com/MarvinCai to become a committer and we are
> pleased
> > to
> > > > announce that he has accepted.
> > > >
> > > > Marvin has joined the community for more than 1 year now and he is
> > > active in
> > > > the Pulsar community for more than 6 months.
> > > >
> > > > Welcome and Congratulations, Marvin!
> > > >
> > > > Please join us in congratulating and welcoming Marvin onboard!
> > > >
> > > > Best Regards,
> > > > Lin Lin on behalf of the Pulsar PMC
> > >
> > >
> >
>

Re: [DISCUSS] Release Pulsar 2.7.4

[guo jiwei]

Hi,
After we have fixed some issue like ZookeeperCache NPE, listing namespace
exception, and skip some flaky tests (verified locally), now the CI have
passed.
Skipped flaky tests are tracked here:
https://github.com/apache/pulsar/issues/13299
Now we decide to vote for releasing 2.7.4.

Regards
Jiwei Guo (Tboy)


On Tue, Dec 14, 2021 at 11:58 AM PengHui Li  wrote:

> Thanks for the update, I will move it 2.7.5
>
> Thanks,
> Penghui
>
> On Tue, Dec 14, 2021 at 9:47 AM Matteo Merli 
> wrote:
>
> > Let's take https://github.com/apache/pulsar/pull/12484 out of the
> > picture since it's failing the tests.
> >
> >
> > --
> > Matteo Merli
> > 
> >
> > On Sun, Dec 12, 2021 at 11:06 PM PengHui Li  wrote:
> > >
> > > Yes,
> > >
> > > https://github.com/apache/pulsar/pull/13215 has cherry-picked, so we
> can
> > > close it.
> > > https://github.com/apache/pulsar/pull/12484 blocked by the test.
> > >
> > > Penghui
> > >
> > > On Mon, Dec 13, 2021 at 2:35 PM Dave Fisher 
> > wrote:
> > >
> > > > I see 2 PRs still open at
> > > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.7.4
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Dec 12, 2021, at 8:22 PM, guo jiwei 
> wrote:
> > > > >
> > > > > I have pushed out some fixes in
> > > > https://github.com/apache/pulsar/pull/13243
> > > > > After the tests get passed, I will send out the RC-1 VOTE for 2.7.4
> > > > >
> > > > > Regards
> > > > > Jiwei Guo (Tboy)
> > > > >
> > > > >
> > > > >> On Sun, Dec 12, 2021 at 3:11 PM PengHui Li 
> > wrote:
> > > > >>
> > > > >> Just put an update here. We have done the PR cherry-picking
> > > > >>
> > > > >> https://github.com/apache/pulsar/commits/branch-2.7
> > > > >>
> > > > >> And most of the integration tests are fixed due to the docker
> image
> > > > issue
> > > > >> or the testcontainer issue, now some integration tests get passed,
> > but
> > > > some
> > > > >> are not.
> > > > >> And there are some failed tests, maybe a flaky test, we need to
> > ensure
> > > > it's
> > > > >> not a regression.
> > > > >>
> > > > >> We are continuing on the test part.
> > > > >>
> > > > >> Penghui
> > > > >>
> > > > >>
> > > > >>
> > > > >>> On Sat, Dec 11, 2021 at 5:36 PM PengHui Li 
> > wrote:
> > > > >>>
> > > > >>> Hi Michael,
> > > > >>>
> > > > >>> +1,
> > > > >>>
> > > > >>> Thanks for the great work.
> > > > >>> We will continue on the PR cherry-picking and the release process
> > to
> > > > make
> > > > >>> sure the urgent release can be done ASAP.
> > > > >>>
> > > > >>> Penghui
> > > > >>>
> > > > >>> On Sat, Dec 11, 2021 at 3:42 PM Michael Marshall <
> > mmarsh...@apache.org
> > > > >
> > > > >>> wrote:
> > > > >>>
> > > > >>>> Given the log4j CVE, we should work to release 2.7.4.
> > > > >>>>
> > > > >>>> I started preparing the release today by cherry-picking merged
> PRs
> > > > >>>> that have the `release/2.7.4` label but have not yet been
> > > > >>>> cherry-picked to `branch-2.7` [0]. There are still 37 PRs that
> > have
> > > > >>>> not been cherry picked. I think it will take too long to cherry
> > pick
> > > > >>>> all of these commits, as many have conflicts, and we should
> > prioritize
> > > > >>>> releasing 2.7.4. The main commits that we should get
> cherry-picked
> > > > >>>> before creating the git tag are any labeled with
> > `component/security`.
> > > > >>>> There are only a few remaining commits to cherry pick. Please
> let
> > me
> > > > >>>> know if you think any other commits ought to be cherry-picked.
> > > &

[VOTE] Pulsar Release 2.7.4 Candidate 1

[guo jiwei]

This is the first release candidate for Apache Pulsar, version 2.7.4.

It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.4+is%3Apr+

Release note:
https://github.com/apache/pulsar/pull/13391

*** Please download, test and vote on this release. This vote will
stay openfor at least 72 hours ***

Note that we are voting upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.4-candidate-1/

SHA-512 checksums:

1a34a408085328500c8c4c72e5ca9b458058a088674b1bfd550fe01ad365182b8820516f99b5c010a03037e1886ce5539cb57f5ef4a2297f1b7ed8fb5844bcd0
 apache-pulsar-2.7.4-bin.tar.gz
37e75698946f3390a254fa2bd7d974fca27d1aed632e86d64a08dc0bf8f2e0ca830cbeed2820782e59ac6bac7368ae69b54f1f5cd3d6c2cad292166e3538e285
 apache-pulsar-2.7.4-src.tar.gz


Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1113

The tag to be voted upon:
v2.7.4-candidate-1 (ab451b855d873a9bad2005f939a23118a583baa9)
https://github.com/apache/pulsar/releases/tag/v2.7.4-candidate-1

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.



Regards
Jiwei Guo (Tboy)

Re: [VOTE] Pulsar Release 2.7.4 Candidate 1

[guo jiwei]

Hi, community.
Due to the CVE-2021-25105 (more details at
https://logging.apache.org/log4j/2.x/security.html),  we have to upgrade
log4j2 to 2.17,  so suggest canceling this vote.
I will send out the second-round vote later.

Regards
Jiwei Guo (Tboy)


On Mon, Dec 20, 2021 at 6:39 PM Nozomi Kurihara  wrote:

> +1 (binding)
>
> - verified checksums and signatures
> - build from source
> - verified produce/consume and functions
> - verified cassandra connector
> - verified stateful function
>
> Thanks,
> Nozomi
>
> 2021年12月18日(土) 19:43 Enrico Olivelli :
>
> > Jiwei Guo,
> > Thanks for driving the release
> > today is Saturday, so I am not sure how many people will have time to
> test
> > the release candidate during the 72 hours period (for instance I can do
> it
> > only on Monday, hopefully).
> > Please take this into consideration when you are going to close the VOTE,
> > maybe waiting until Tuesday may be a good idea.
> >
> > Enrico
> >
> >
> >
> > Il giorno sab 18 dic 2021 alle ore 09:54 guo jiwei  >
> > ha scritto:
> >
> > > This is the first release candidate for Apache Pulsar, version 2.7.4.
> > >
> > > It fixes the following issues:
> > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.4+is%3Apr+
> > >
> > > Release note:
> > > https://github.com/apache/pulsar/pull/13391
> > >
> > > *** Please download, test and vote on this release. This vote will
> > > stay openfor at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.4-candidate-1/
> > >
> > > SHA-512 checksums:
> > >
> > >
> > >
> >
> 1a34a408085328500c8c4c72e5ca9b458058a088674b1bfd550fe01ad365182b8820516f99b5c010a03037e1886ce5539cb57f5ef4a2297f1b7ed8fb5844bcd0
> > >  apache-pulsar-2.7.4-bin.tar.gz
> > >
> > >
> >
> 37e75698946f3390a254fa2bd7d974fca27d1aed632e86d64a08dc0bf8f2e0ca830cbeed2820782e59ac6bac7368ae69b54f1f5cd3d6c2cad292166e3538e285
> > >  apache-pulsar-2.7.4-src.tar.gz
> > >
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1113
> > >
> > > The tag to be voted upon:
> > > v2.7.4-candidate-1 (ab451b855d873a9bad2005f939a23118a583baa9)
> > > https://github.com/apache/pulsar/releases/tag/v2.7.4-candidate-1
> > >
> > > 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.
> > >
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
> >
>

[VOTE] Pulsar Release 2.7.4 Candidate 2

[guo jiwei]

This is the second release candidate for Apache Pulsar, version 2.7.4.

It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.4+is%3Apr+

Release note:
https://github.com/apache/pulsar/pull/13391

*** Please download, test and vote on this release. This vote will
stay openfor at least 72 hours ***

Note that we are voting upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.4-candidate-2/


SHA-512 checksums:

a56a794bd14c8f4b6d7320496b2be4640a836a7aa940c37aac4f53ae057f8b4887f3f8716f475d2a03c79e3e44bf2ad9234fd05e2b0f58b005a0a4f7f376fc15
 apache-pulsar-2.7.4-bin.tar.gz
03ec488d59d281fdbbbee48f1f62b266cd1163181decbf962d0d58eacc746731d31739955d8afac8bc392547caf2ae76e864d0ad2f2a460cd53920a707a7b40c
 apache-pulsar-2.7.4-src.tar.gz


Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1
130

The tag to be voted upon:
v2.7.4-candidate-2 (2774b464f3b7e1ccfdc84d6d390efe7260cbb7fa)
https://github.com/apache/pulsar/releases/tag/v2.7.4-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.



Regards
Jiwei Guo (Tboy)

[ANNOUNCE] Apache Pulsar 2.7.4 released

[guo jiwei]

The Apache Pulsar team is proud to announce Apache Pulsar version 2.7.4.

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://pulsar.apache.org/download

Release Notes are at:
http://pulsar.apache.org/release-notes

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


Regards
Jiwei Guo (Tboy)

Re: [DISCUSSION] Produce chunk messages failed when topic level maxMessageSize is set

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)

On Tue, Dec 28, 2021 at 5:44 AM 陳智弘  wrote:
>
> +1
>
>  Skip the topic level setting is better
>
> Hang Chen  於 2021年12月27日 週一 22:09 寫道：
>
> > +1
> >
> > We'd better skip the topic level maxMessageSize check for chunk messages.
> >
> > Best,
> > Hang
> >
> > PengHui Li  于2021年12月27日周一 22:07写道：
> > >
> > > +1,
> > >
> > > We can only skip the topic level messages size check for the chunk
> > message.
> > >
> > > Regards,
> > > Penghui
> > >
> > > On Mon, Dec 20, 2021 at 3:37 PM Haiting Jiang 
> > > wrote:
> > >
> > > > Hi Pulsar Community,
> > > >
> > > > I discovered a bug that chunk messages producing fails if topic level
> > > > maxMessageSize is set [1]. The root cause of this issue is because
> > chunk
> > > > message is using broker level maxMessageSize as chunk size. And topic
> > level
> > > > maxMessageSize is always <= broker level maxMessageSize. So once it is
> > set,
> > > > the on-going chunk message producing fails.
> > > >
> > > > ## Proposed changes
> > > > I would like to fix this by just skipping topic level maxMessageSize
> > check
> > > > in
> > > >
> > org.apache.pulsar.broker.service.AbstractTopic#isExceedMaximumMessageSize.Topic
> > > > level maxMessageSize is introduced in [2], for the purpose of "easier
> > to
> > > > plan resource quotas for client allocation". And IMO this change will
> > not
> > > > bring further complex into this.
> > > >
> > > > ## Alternative
> > > > Add a client side topic level maxMessageSize and keep it synced with
> > > > broker.
> > > >
> > > > Required changes:
> > > > - [client] Add a new field
> > > > org.apache.pulsar.client.impl.ProducerBase#maxMessageSize to store this
> > > > client side topic level maxMessageSize.
> > > > - [PulsarApi.proto] Add a new field maxMessageSize in the
> > > > CommandProducerSuccess for the initial value of
> > ProducerBase#maxMessageSize
> > > > - [PulsarApi.proto] Add a new Command like
> > > > CommandUpdateClientPolicy{producerId, maxMessageSize} to update
> > > > ProducerBase#maxMessageSize when topic level maxMessageSize is updated.
> > > > Further more, some other data consistency issues need be handled very
> > > > carefully when maxMessageSize is updated.
> > > > This alternative is complex but can also solve other topic level
> > > > maxMessageSize issue [3] when batching is enabled (non-batching case is
> > > > solved with PR [4]).
> > > >
> > > > Any suggestions or other use cases of topic level maxMessageSize will
> > be
> > > > appreciated.
> > > >
> > > > Thanks,
> > > > Haiting Jiang
> > > >
> > > > [1] https://github.com/apache/pulsar/issues/13360
> > > > [2] https://github.com/apache/pulsar/pull/8732
> > > > [3] https://github.com/apache/pulsar/issues/12958
> > > > [4] https://github.com/apache/pulsar/pull/13147
> > > >
> >

Re: [DISCUSS] Release Pulsar 2.7.4

[guo jiwei]

Hi Shivji,
  The 2.7.4 has been already released and includes 2.17.0.


Regards
Jiwei Guo (Tboy)


On Tue, Dec 21, 2021 at 6:47 PM Shivji Kumar Jha  wrote:
>
> Hi Pulsar Team,
>
> 2.16.0 is prone to DDoS attacks [1].  Is it possible to move to 2.17.0 in
> pulsar 2.7.4 ?
>
> [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105
>
> Regards,
> Shivji Kumar Jha
> http://www.shivjijha.com/
> +91 8884075512
>
>
> On Tue, 21 Dec 2021 at 02:46, Michael Marshall 
wrote:
>
> > Thank you Penghui, Technoboy, and BewareMyPower for picking up where I
> > left off to get the 2.7.4 release ready to go. You cherry-picked many
> > commits,
> > resolved many conflicts, and fixed a bunch of tests!
> >
> > Thanks,
> > Michael
> >
> >
> > On Thu, Dec 16, 2021 at 7:37 PM guo jiwei  wrote:
> > >
> > > Hi,
> > > After we have fixed some issue like ZookeeperCache NPE, listing
namespace
> > > exception, and skip some flaky tests (verified locally), now the CI
have
> > > passed.
> > > Skipped flaky tests are tracked here:
> > > https://github.com/apache/pulsar/issues/13299
> > > Now we decide to vote for releasing 2.7.4.
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
> > >
> > > On Tue, Dec 14, 2021 at 11:58 AM PengHui Li 
wrote:
> > >
> > > > Thanks for the update, I will move it 2.7.5
> > > >
> > > > Thanks,
> > > > Penghui
> > > >
> > > > On Tue, Dec 14, 2021 at 9:47 AM Matteo Merli 
> > > > wrote:
> > > >
> > > > > Let's take https://github.com/apache/pulsar/pull/12484 out of the
> > > > > picture since it's failing the tests.
> > > > >
> > > > >
> > > > > --
> > > > > Matteo Merli
> > > > > 
> > > > >
> > > > > On Sun, Dec 12, 2021 at 11:06 PM PengHui Li 
> > wrote:
> > > > > >
> > > > > > Yes,
> > > > > >
> > > > > > https://github.com/apache/pulsar/pull/13215 has cherry-picked,
so
> > we
> > > > can
> > > > > > close it.
> > > > > > https://github.com/apache/pulsar/pull/12484 blocked by the test.
> > > > > >
> > > > > > Penghui
> > > > > >
> > > > > > On Mon, Dec 13, 2021 at 2:35 PM Dave Fisher <
wave4d...@comcast.net
> > >
> > > > > wrote:
> > > > > >
> > > > > > > I see 2 PRs still open at
> > > > > > >
> > > > >
> > > >
> >
https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.7.4
> > > > > > >
> > > > > > > Sent from my iPhone
> > > > > > >
> > > > > > > > On Dec 12, 2021, at 8:22 PM, guo jiwei 
> > > > wrote:
> > > > > > > >
> > > > > > > > I have pushed out some fixes in
> > > > > > > https://github.com/apache/pulsar/pull/13243
> > > > > > > > After the tests get passed, I will send out the RC-1 VOTE
for
> > 2.7.4
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > Jiwei Guo (Tboy)
> > > > > > > >
> > > > > > > >
> > > > > > > >> On Sun, Dec 12, 2021 at 3:11 PM PengHui Li <
> > peng...@apache.org>
> > > > > wrote:
> > > > > > > >>
> > > > > > > >> Just put an update here. We have done the PR cherry-picking
> > > > > > > >>
> > > > > > > >> https://github.com/apache/pulsar/commits/branch-2.7
> > > > > > > >>
> > > > > > > >> And most of the integration tests are fixed due to the
docker
> > > > image
> > > > > > > issue
> > > > > > > >> or the testcontainer issue, now some integration tests get
> > passed,
> > > > > but
> > > > > > > some
> > > > > > > >> are not.
> > > > > > > >> And there are some failed tests, maybe a flaky test, we
need
> > to
> > > > > ensure
> > > > > > > it's
> > > > > > > >> not a regression.
> >

Re: [DISCUSS] Apache Pulsar 2.9.2 release

[guo jiwei]

+1

Regards
Jiwei Guo (Tboy)


On Thu, Jan 6, 2022 at 2:32 AM Michael Marshall 
wrote:

> +1 - thanks for starting this thread.
>
> >171 commits?
> > Why?
> > This is too much in my opinion for a point release.
>
> I agree that this is a lot of commits, and especially since we only
> just released 2.9.1. Note though that this is not a new phenomenon:
> 2.8.2 had 251 commits on top of 2.8.1. [0]
>
> > Every change we cherry pick has a good chance to break the stability
>
> This is one of the challenges to our current cherry-pick based git
> workflow. It's hard to decide which commits to cherry-pick, and it
> requires a high level of effort to later verify the correctness of
> what was cherry-picked. This is one of the reasons I am interested in
> exploring a merge based git workflow.
>
> Our project has grown a ton and will continue to grow. Our git process
> should prioritize the stability of our existing release branches.
>
> > And that we will let branch-2.9 stabilise by not adding any other commits
> > that are not strictly required:
> > - security related issues
> > - data loss/data corruption cases
>
> If we don't change our git workflow, we should at least add a
> cherry-picking guide to the wiki. We have added many new committers in
> the past year, but we don't provide them with much documented guidance
> on how to exercise their new rights.
>
> Thanks,
> Michael
>
> [0] https://github.com/apache/pulsar/compare/v2.8.1...v2.8.2
>
>
> On Wed, Jan 5, 2022 at 11:44 AM Enrico Olivelli 
> wrote:
> >
> > BTW +1
> >
> > I hope we will review carefully what we are including in the release
> >
> > And that we will let branch-2.9 stabilise by not adding any other commits
> > that are not strictly required:
> > - security related issues
> > - data loss/data corruption cases
> >
> >
> > Enrico
> >
> >
> > Thank you Ran Gao for starting this thread.
> >
> >
> >
> > Enrico
> >
> > Il Mer 5 Gen 2022, 17:29 Enrico Olivelli  ha
> scritto:
> >
> > > 171 commits?
> > >
> > > Why?
> > >
> > > This is too much in my opinion for a point release.
> > >
> > > I am pretty sure that we don't need all that changes.
> > >
> > > Every change we cherry pick has a good chance to break the stability
> > >
> > > Enrico
> > >
> > > Il Mer 5 Gen 2022, 16:30 mattison chao  ha
> > > scritto:
> > >
> > >> +1
> > >>
> > >> regards,
> > >> Mattisonchao
> > >>
> > >> On Wed, 5 Jan 2022 at 23:04, Lan Liang 
> wrote:
> > >>
> > >> > +1,Thanks for your work.
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > Best Regards,
> > >> > Lan Liang
> > >> > On 1/5/2022 23:01，Hang Chen wrote：
> > >> > +1
> > >> >
> > >> > Best,
> > >> > Hang
> > >> >
> > >> > 陳智弘  于2022年1月5日周三 21:30写道：
> > >> >
> > >> > +1
> > >> >
> > >> > Lari Hotari  於 2022年1月5日 週三 20:56 寫道：
> > >> >
> > >> > +1
> > >> >
> > >> > On Wed, Jan 5, 2022 at 11:23 AM Ran Gao  wrote:
> > >> >
> > >> > Hello, Pulsar community:
> > >> >
> > >> > I'd like to propose that we release Apache Pulsar 2.9.2.
> > >> >
> > >> > Currently, compared to 2.9.1, branch-2.9 already merged 171
> > >> commits(refer
> > >> > to [0]), they contain the log4j security patch and many important
> fixes.
> > >> >
> > >> > I am happy to volunteer to be the release manager.
> > >> >
> > >> > I see 4 merged PRs are labeled release/2.9.2 but not cherry-pick to
> > >> > branch-2.9, I'll cherry-pick them, and there are also 20 open PRs
> are
> > >> > labeled release/2.9.2, I'll follow them to make sure important fix
> could
> > >> > be
> > >> > merged in 2.9.2.
> > >> >
> > >> >
> > >> > Best,
> > >> > Ran Gao
> > >> >
> > >> >
> > >> > [0] https://github.com/apache/pulsar/compare/v2.9.1...branch-2.9
> > >> >
> > >> >
> > >> >
> > >>
> > >
>

Re: [ANNOUNCE] New Committer: Zhangjian He

[guo jiwei]

Congrats to Zhangjian!


Regards
Jiwei Guo (Tboy)


On Wed, Jan 5, 2022 at 10:59 PM Hang Chen  wrote:

> The Apache Pulsar Project Management Committee (PMC) has invited Zhangjian
> He
> https://github.com/Shoothzj to become a committer and we are pleased to
> announce that he has accepted.
>
> Zhangjian He has joined the community for more than 1 year now and he is
> active in the Pulsar community for more than 6 months
>
> Welcome and Congratulations, Zhangjian!
>
> Please join us in congratulating and welcoming Zhangjian onboard!
>
> Best Regards,
> Hang Chen on behalf of the Pulsar PMC
>

Re: [DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

[guo jiwei]

Hi
 The PIP link : https://github.com/apache/pulsar/issues/13989

Regards
Jiwei Guo (Tboy)


On Sat, Jan 29, 2022 at 11:46 AM mattison chao 
wrote:

> Hello everyone,
>
> I want to start a discussion about PIP-139 : Support Broker send command
> to real close producer/consumer.
>
> This is the PIP document
>
> https://github.com/apache/pulsar/issues/13989 <
> https://github.com/apache/pulsar/issues/13979>
>
> Please check it out and feel free to share your thoughts.
>
> Best,
> Mattison
>
>
>  Pasted below for quoting convenience.
>
>
>
> Relation pull request:  #13337
> Authors: @Technoboy-  @mattisonchao
>
> ## Motivation
>
> Before we discuss this pip, I'd like to supplement some context to help
> contributors who don't want to read the original pull request.
>
> > When there are no user-created topics under a namespace, Namespace
> should be deleted. But currently, the system topic existed and the
> reader/producer could auto-create the system which may cause the namespace
> deletion to fail.
>
> For this reason, we need to close the system topic reader/producer first,
> then remove the system topic. finally, remove the namespace.
>
> Following this way, we first want to use ``terminate`` to solve this
> problem. then we found producers can disconnect, but consumers are still
> alive. So, another PR #13960 wants to add consumers' closing logic.
>
> After #13960, all things look good, but another problem appears. that is
> we need to wait until consumers completely consume all messages (this may
> make terminate topic so long and the operation timeout)then get
> ``reachedEndOfTopic``. the relative code here :
>
>
> https://github.com/apache/pulsar/blob/07ef9231db8b844586b9217ee2d59237eb9c54b7/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/CompactorSubscription.java#L102-L106
>
> In the #13337 case, we need to force close consumers immediately. So we
> write this PIP to discuss another way to resolve this problem.
>
> ## Goal
>
> We can add a new field(`allow_reconnect`) in command
> ``CommandCloseProducer``/ ``CommandCloseConsumer`` to close
> producer/consumers immediately.
>
> ## API Changes
>
> - Add ``allow_reconnect`` to ``CommandCloseProducer``;
>
> ```java
> **Before**
>
> message CommandCloseProducer {
> required uint64 producer_id = 1;
> required uint64 request_id = 2;
> }
>
> **After**
> message CommandCloseProducer {
> required uint64 producer_id = 1;
> required uint64 request_id = 2;
> optional bool allow_reconnect = 3 [default = true];
> }
> ```
>
> - Add ``allow_reconnect`` to ``CommandCloseConsumer``
> ```java
> **Before**
>
> message CommandCloseConsumer {
> required uint64 consumer_id = 1;
> required uint64 request_id = 2;
> }
>
> **After**
> message CommandCloseConsumer {
> required uint64 consumer_id = 1;
> required uint64 request_id = 2;
> optional bool allow_reconnect = 3 [default = true];
> }
> ```
>
> ## Implementation
>
> ### ClientCnx - Producer:
>
> **Before**
> ```java
> @Override
> protected void handleCloseProducer(CommandCloseProducer closeProducer)
> {
> log.info("[{}] Broker notification of Closed producer: {}",
> remoteAddress, closeProducer.getProducerId());
> final long producerId = closeProducer.getProducerId();
> ProducerImpl producer = producers.get(producerId);
> if (producer != null) {
> producer.connectionClosed(this);
> } else {
> log.warn("Producer with id {} not found while closing producer
> ", producerId);
> }
> }
> ```
> After:
> ```java
>@Override
> protected void handleCloseProducer(CommandCloseProducer closeProducer)
> {
> log.info("[{}] Broker notification of Closed producer: {}",
> remoteAddress, closeProducer.getProducerId());
> final long producerId = closeProducer.getProducerId();
> ProducerImpl producer = producers.get(producerId);
> if (producer != null) {
> if (closeProducer.isAllowReconnect) {
> producer.connectionClosed(this);
> } else {
> producer.closeAsync();
> }
> } else {
> log.warn("Producer with id {} not found while closing producer
> ", producerId);
> }
> }
> ```
> ### ClientCnx - Consumer:
>
> **Before**
> ```java
> @Override
> protected void handleCloseConsumer(CommandCloseConsumer closeConsumer)
> {
> log.info("[{}] Broker notification of Closed consumer: {}",
> remoteAddress, closeConsumer.getConsumerId());
> final long consumerId = closeConsumer.getConsumerId();
> ConsumerImpl consumer = consumers.get(consumerId);
> if (consumer != null) {
> consumer.connectionClosed(this);
> } else {
> log.warn("Consumer with id {} not found while closing consumer
> ", consumerId);
> }
> }
> ```
> **After**
> ```java
> @Override
> protected void handleCloseConsumer

Re: [ANNOUNCE] New Committer: Li Li

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Tue, Feb 22, 2022 at 8:28 AM Dianjin Wang 
wrote:

> Congratulations!
>
> Best,
> Dianjin Wang
>
>
> On Tue, Feb 15, 2022 at 3:08 PM PengHui Li  wrote:
>
> > The Apache Pulsar Project Management Committee (PMC) has invited Li Li
> > https://github.com/urfreespace to become a committer and we are pleased
> to
> > announce that he has accepted.
> >
> > Li Li has done a great contribution to Pulsar Website, documentation.
> >
> > Welcome and Congratulations, Li Li!
> >
> > Please join us in congratulating and welcoming Li Li onboard!
> >
> > Best Regards,
> > Penghui Li on behalf of the Pulsar PMC
> >
>

Re: [DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

[guo jiwei]

t;> wrote:
> > > >> > > >>
> > > >> > > >>> If we want to solve this problem, we need to add some sync
> > > >> resources like
> > > >> > > >> lock/state, I think it’s a harm for us, we don’t need to do
> > that.
> > > >> > > >>
> > > >> > > >> I think we can make the namespace/tenants to the inactive
> state
> > > >> first so
> > > >> > > >> that we can avoid any new
> > > >> > > >> producer/consumer connect to the topic under the
> > namespace/tenant.
> > > >> > > >>
> > > >> > > >> The old producer/consumer should be closed after applying the
> > > >> changes from
> > > >> > > >> this proposal.
> > > >> > > >>
> > > >> > > >> Thanks,
> > > >> > > >> Penghui
> > > >> > > >>
> > > >> > > >> On Tue, Feb 8, 2022 at 5:47 PM mattison chao <
> > > >> mattisonc...@gmail.com> wrote:
> > > >> > > >>
> > > >> > > >>>> This is supposed to mean that the namespace should be able
> > to be
> > > >> > > >>>> deleted, correct?
> > > >> > > >>>
> > > >> > > >>> Yes, the main background is the user doesn’t have an active
> > > >> topic. so,
> > > >> > > >>> they want to delete the namespace.
> > > >> > > >>>
> > > >> > > >>>> However, I think
> > > >> > > >>>> we might still have a race condition that could make tenant
> > or
> > > >> > > >>>> namespace deletion fail. Specifically, if a new producer or
> > > >> consumer
> > > >> > > >>>> creates a topic after the namespace deletion has started
> but
> > > >> > > >>>> before it is complete. Do you agree that the underlying
> race
> > > >> still
> > > >> > > >>> exists?
> > > >> > > >>>
> > > >> > > >>> Yes, this condition exists. I think it’s not a big problem
> > > >> because the
> > > >> > > >>> user doesn’t want to use this namespace anymore.
> > > >> > > >>> If this scenario appears, they will get an error and need to
> > > >> delete it
> > > >> > > >>> again.
> > > >> > > >>>
> > > >> > > >>>> What if we expand our usage of the "terminated" feature to
> > apply
> > > >> to
> > > >> > > >>>> namespaces (and tenants)? Then, a terminated namespace can
> > have
> > > >> > > >>>> bundles and topics can be deleted but not created (just as
> a
> > > >> terminated
> > > >> > > >>>> topic cannot have any new messages published to it). This
> > would
> > > >> take
> > > >> > > >>>> care of all topic creation race conditions. We'd probably
> > need
> > > >> to add
> > > >> > > >>>> new protobuf exceptions for this feature.
> > > >> > > >>>
> > > >> > > >>>
> > > >> > > >>> If we want to solve this problem, we need to add some sync
> > > >> resources like
> > > >> > > >>> lock/state, I think it’s a harm for us, we don’t need to do
> > that.
> > > >> > > >>>
> > > >> > > >>> Thanks for your suggestions, let me know what you think.
> > > >> > > >>>
> > > >> > > >>> Best,
> > > >> > > >>> Mattison
> > > >> > > >>>
> > > >> > > >>>> On Feb 1, 2022, at 2:26 PM, Michael Marshall <
> > > >> mmarsh...@apache.org>
> > > >> > > >>> wrote:
> > > >> > > >>>>
> > > >> > > >>>> This proposal identifies an important issue that we should
> > > >> definitely
> > > &g

Re: [DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

[guo jiwei]

27;t delete it from cluster A. For
> > > > example, when should cluster A stop attempting to create producers to
> > > > cluster B for the deleted namespace/topic and how do we inform
> > > > operators that the replication is no longer working as configured. We
> > > > avoid several problems by failing the initial user request.
> > > >
> > > > Note that while a user cannot explicitly delete a replicated topic,
> > > > they can remove the replication configuration in cluster A and
> cluster
> > > > B, and then they are left with unreplicated namespaces and topics,
> > > > which can be deleted.
> > > >
> > > > > But for now, for a replicated topic, users are not able to delete
> it
> > > > because
> > > > > of the internal active producer, adding force delete option can
> > delete
> > > > > the topic, but it will create again if users enabled topic
> > auto-creation.
> > > >
> > > > In this case, the specific problem stems from a remote cluster
> > > > targeting the local cluster. If the user only deletes the local
> topic,
> > > > without removing the replication configuration, I don't think it
> > > > should be surprising when the topic gets recreated (assuming auto
> > > > topic creation is enabled).
> > > >
> > > > In my view, I think it's okay to make it harder to delete
> > > > geo-replicated namespaces or topics than local namespaces or topics.
> > > > Failing requests with a good, informative error message protects
> > > > users. Additionally, if users are able to delete a namespace or topic
> > > > by force, that gives them a work around--although we should document
> > > > the limitations of this workaround.
> > > >
> > > > I am not experienced with geo-replication, so please let me know if
> > > > any of my analysis doesn't align with the actual design.
> > > >
> > > > Thanks,
> > > > Michael
> > > >
> > > >
> > > > On Sun, Feb 27, 2022 at 8:42 PM guo jiwei 
> > wrote:
> > > > >
> > > > > I have added the geo-replicator topic case and updated the PIP.
> > > > >
> > > > >
> > > > > Regards
> > > > > Jiwei Guo (Tboy)
> > > > >
> > > > >
> > > > > On Sun, Feb 27, 2022 at 1:00 PM PengHui Li 
> > wrote:
> > > > >
> > > > > > > To me, the main question is whether we create a custom error or
> > > > expand
> > > > > > the `CommandCloseProducer` command. I lean towards adding an
> error
> > > > > > because it will automatically be backward compatible based on the
> > way
> > > > > > the client determines which errors are retriable. Although, I
> don't
> > > > > > have a strong opinion.
> > > > > >
> > > > > > I have the same opinion as you. But it looks like not able to fix
> > the
> > > > > > geo-replication topic deletion.
> > > > > >
> > > > > > Either replicated topic or non-replicated topic, we should
> provide
> > the
> > > > > > same topic deletion behavior, the topic can be deleted if no
> active
> > > > > > user's producers/consumers, should not be affected by the Pulsar
> > > > > > internal producers/consumers.
> > > > > >
> > > > > > But for now, for a replicated topic, users are not able to delete
> > it
> > > > > > because
> > > > > > of the internal active producer, adding force delete option can
> > delete
> > > > > > the topic, but it will create again if users enabled topic
> > > > auto-creation.
> > > > > >
> > > > > > I think in this case, it seems we don't have a chance to give the
> > > > producer
> > > > > > an exception, because the reconnection will connect to a new
> topic
> > only
> > > > > > with
> > > > > > the same topic name as before.
> > > > > >
> > > > > > Thanks,
> > > > > > Penghui
> > > > > >
> > > > > > On Sat, Feb 26, 2022 at 2:24 PM Michael Marshall <
> > mmarsh...@apache.org
> &g

[DISCUSS] Byte schema compatibility issue

[guo jiwei]

Hi,
   I want to discuss the compatibility issue with the byte schema here.
   For now, the byte-schema is compatible with all other schemas. This may
introduce more issues.
   Case 1:
  1. Consumer1 init with JSON schema for topic A.
  2. But producer1 init without schema and send byte messages
directly to topic A.
  This will cause consumer1 to deserialize msg error.  Also,
producer1 may send unsafe byte data.

 Case 2:
   1. Consumer1 init with byte schema for topic A.
   2. But producer1 init with AVRO/JSON schema and send messages to
topic A.
   This will cause consumer1 don't know how to deserialize msg.

To avoid the above issues, Byte schema should also follow the schema
compatibility policy. I'm open #13701
 to track this. If the idea
is accepted, I will start a PIP.

 Please give some suggestions about this idea.


Regards
Jiwei Guo (Tboy)

Re: [ANNOUNCE] New Committer: Andrey Yegorov

[guo jiwei]

Congratulations Andrey!

Regards
Jiwei Guo (Tboy)


On Wed, Mar 16, 2022 at 1:55 AM Aloys Zhang  wrote:

> Congrats Andrey!
>
> r...@apache.org  于2022年3月14日周一 11:26写道：
>
> > Congrats Andrey!
> >
> > ZhangJian He  于2022年3月14日周一 09:51写道：
> >
> > > Congrats Andrey!
> > >
> > >
> > > Yu  于2022年3月14日周一 09:33写道：
> > >
> > > > Congrats Andrey!
> > > >
> > > > On Mon, Mar 14, 2022 at 9:15 AM Hang Chen 
> wrote:
> > > >
> > > > > Congratulations Andrey!
> > > > >
> > > > > Best,
> > > > > Hang
> > > > >
> > > > > Li Li  于2022年3月14日周一 08:41写道：
> > > > > >
> > > > > > Congrats Andrey!
> > > > > >
> > > > > > -Li Li
> > > > > >
> > > > > > > On Mar 11, 2022, at 5:54 PM, PengHui Li 
> > > wrote:
> > > > > > >
> > > > > > > Congrats Andrey!
> > > > > > >
> > > > > > > -Penghui
> > > > > > >
> > > > > > > On Wed, Mar 9, 2022 at 9:33 PM Lari Hotari  >
> > > > wrote:
> > > > > > >
> > > > > > >> Congrats Andrey!
> > > > > > >>
> > > > > > >> -Lari
> > > > > > >>
> > > > > > >> On 2022/03/07 19:25:44 Dave Fisher wrote:
> > > > > > >>> The Apache Pulsar Project Management Committee (PMC) has
> > invited
> > > > > Andrey
> > > > > > >> Yegorov
> > > > > > >>> https://github.com/dlg99 to become a committer and we are
> > > pleased
> > > > to
> > > > > > >>> announce that he has accepted.
> > > > > > >>>
> > > > > > >>> Andrey has made great contributions to Pulsar including
> > Connector
> > > > and
> > > > > > >> Adaptor work along with updating dependencies for CVEs
> > > > > > >>> Welcome and Congratulations, Li Li!
> > > > > > >>>
> > > > > > >>> Please join us in congratulating and welcoming Andrey
> onboard!
> > > > > > >>>
> > > > > > >>> Best Regards,
> > > > > > >>> Dave Fisher on behalf of the Pulsar PMC
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

[DISCUSS] PIP-143 : Standardize Admin REST API

[guo jiwei]

Hello community,

I want to discuss refactoring and standardizing REST API. Users have
encountered several deadlock problems in the API part before, like #13666
, #12590
. After fixing the above two
issues, we check the related part and find that there are still numbers of
asynchronous call synchronous implementations for other functions of the
REST API. To avoid more problems, I would like to discuss the
standardization of API modules and create the PIP-142  #14365
 . Feel free to comment and
give suggestions.




Regards
Jiwei Guo (Tboy)

Re: [DISCUSS] PIP-143 : Standardize Admin REST API

[guo jiwei]

Ok, I have updated the proposal number to 149.
https://github.com/apache/pulsar/issues/14365.

Regards
Jiwei Guo (Tboy)


On Wed, Mar 16, 2022 at 8:53 PM PengHui Li  wrote:

> PIP-143 is this one https://github.com/apache/pulsar/issues/13761
>
> Please peek a new proposal number
>
> Penghui
>
> On Wed, Mar 16, 2022 at 8:43 PM guo jiwei  wrote:
>
> > Hello community,
> >
> > I want to discuss refactoring and standardizing REST API. Users have
> > encountered several deadlock problems in the API part before, like #13666
> > <https://github.com/apache/pulsar/pull/13666>, #12590
> > <https://github.com/apache/pulsar/pull/12590>. After fixing the above
> two
> > issues, we check the related part and find that there are still numbers
> of
> > asynchronous call synchronous implementations for other functions of the
> > REST API. To avoid more problems, I would like to discuss the
> > standardization of API modules and create the PIP-142  #14365
> > <https://github.com/apache/pulsar/pull/14365> . Feel free to comment and
> > give suggestions.
> >
> >
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
>

Re: [DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

[guo jiwei]

Hi
   As we discussed above, I have posted pr #14730
<https://github.com/apache/pulsar/pull/14730> to solve the deleting
namespace issue.
   Thanks Michael for your idea. And thanks to all the people joining
this.

Regards
Jiwei Guo (Tboy)


On Mon, Mar 7, 2022 at 1:45 PM guo jiwei  wrote:

> Hi  Penghui,
>After test, we can use #12136 to stop the replicator.
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Sat, Mar 5, 2022 at 5:31 PM PengHui Li  wrote:
>
>> > Great point. I was focused on deleting namespaces and missed the case
>> where the user wants to delete a topic from a replicated namespace. I
>> agree that we should make it possible to delete these topics without
>> removing the namespace replication.
>>
>> Oh, sorry. I thought again, after
>> https://github.com/apache/pulsar/pull/12136
>> introduced topic level geo-replication configuration, users can disable
>> for
>> a topic even if the namespace enabled geo-replication.
>>
>> And topic level policy is introduced in 2.6.0. I think It's time to make
>> it
>> one of
>> the features turned on by default.
>>
>> So, we can follow the steps that stop the replication first and then
>> delete
>> the
>> topic from clusters.
>>
>> > Note that it is already possible
>> to delete these topics by deleting with force or by configuring
>> inactive topic deletion.
>>
>> Hmm, I think both of them do not work for now, because the producer of
>> the replicator will always be active.
>>
>> > Considering users can delete replicated topics by deleting with force,
>> are you saying we need to provide a non-force way to delete these
>> topics?
>>
>> Yes, if the topic doesn't have users' producers/consumers, users don't
>> need
>> to force delete the topic, it's a normal deletion.
>>
>>
>> --
>> @mattison @jiwei could you please check if we can use
>> https://github.com/apache/pulsar/pull/12136
>> to stop the geo-replication first, and then delete the topic?
>> If it works, we don't need to change the protocol.
>>
>> Thanks,
>> Penghui
>>
>>
>>
>> On Thu, Mar 3, 2022 at 7:12 AM Michael Marshall 
>> wrote:
>>
>> > > The geo-replication's configuration can be centralized by using
>> > > one configuration store. But that doesn't change anything, we should
>> > > provide the same behavior for both centralized and decentralized
>> > > configuration store.
>> >
>> > Perhaps I misused the word decentralized. I meant that the challenge
>> > comes because geo-replication configurations for clusters are
>> > independent from each other.
>> >
>> > > The current challenge is
>> > > users usually set replicated clusters for a namespace, if remove
>> > > the replication configuration, the entire namespace will be affected.
>> > > We have supported setting the replicated configuration for a topic
>> [1],
>> > > only for 2.10.0 or later.
>> >
>> > Great point. I was focused on deleting namespaces and missed the case
>> > where the user wants to delete a topic from a replicated namespace. I
>> > agree that we should make it possible to delete these topics without
>> > removing the namespace replication. Note that it is already possible
>> > to delete these topics by deleting with force or by configuring
>> > inactive topic deletion.
>> >
>> > > we should provided steps for how to delete an unused replicated
>> > > topic and what are the effects of not removing properly
>> >
>> > I agree, and I think documentation coupled with helpful error logs
>> > will be very helpful here.
>> >
>> > Considering users can delete replicated topics by deleting with force,
>> > are you saying we need to provide a non-force way to delete these
>> > topics?
>> >
>> > If we want to provide a path to normal deletion, we already have an
>> > `isRemote` flag on producers, and the inactive topic deletion code
>> > uses this flag to determine if there are non-replication producers
>> > connected to a topic. We could modify the deletion logic for a global
>> > topic so that it can be deleted as long as the only producers
>> > connected are remote producers. My main concern is that normal
>> > deletion could allow users to miss the nuance that they must also
>

Re: [DISCUSS] PIP-143 : Standardize Admin REST API

[guo jiwei]

Hi, @Enrico
   Sorry for the inappropriate words, I will correct them immediately and
applying in PIP.

Regards
Jiwei Guo (Tboy)


On Wed, Mar 23, 2022 at 8:28 PM Enrico Olivelli  wrote:

> I agree that fixing all the points in which we are doing sync calls is a
> good thing and that we should fix them.
>
> I won't use the name 'standardise' as it sounds to me like creating a new
> API
>
> What about 'Making the REST Admin API fully async' ?
>
> Apart from the name I agreee with the proposal
>
> Enrico
>
> Il Mer 23 Mar 2022, 10:34 Zike Yang  ha scritto:
>
> > +1
> >
> > Thanks,
> > Zike Yang
> >
> > On Tue, Mar 22, 2022 at 8:32 PM 石宝迪 
> > wrote:
> > >
> > > +1
> > >
> > >
> > > > 在 2022年3月22日，19:59，Haiting Jiang  写道：
> > > >
> > > > +1
> > > >
> > > > Thanks,
> > > > Haiting
> > > >
> > > >> On 2022/03/16 12:43:45 guo jiwei wrote:
> > > >> Hello community,
> > > >>
> > > >>I want to discuss refactoring and standardizing REST API. Users
> > have
> > > >> encountered several deadlock problems in the API part before, like
> > #13666
> > > >> <https://github.com/apache/pulsar/pull/13666>, #12590
> > > >> <https://github.com/apache/pulsar/pull/12590>. After fixing the
> > above two
> > > >> issues, we check the related part and find that there are still
> > numbers of
> > > >> asynchronous call synchronous implementations for other functions of
> > the
> > > >> REST API. To avoid more problems, I would like to discuss the
> > > >> standardization of API modules and create the PIP-142  #14365
> > > >> <https://github.com/apache/pulsar/pull/14365> . Feel free to
> comment
> > and
> > > >> give suggestions.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Regards
> > > >> Jiwei Guo (Tboy)
> > > >>
> >
>

Re: [VOTE] PIP-149: Making the REST Admin API fully async

[guo jiwei]

+1

Regards
Jiwei Guo (Tboy)


On Tue, Mar 29, 2022 at 4:16 PM Enrico Olivelli  wrote:

> +1 (binding)
>
> Enrico
>
> Il giorno mar 29 mar 2022 alle ore 09:55 PengHui Li
>  ha scritto:
> >
> > +1,
> >
> > Penghui
> >
> > On Fri, Mar 25, 2022 at 10:13 AM mattison chao 
> > wrote:
> >
> > > This is the voting thread for PIP-149. It will stay open for at least
> 48
> > > hours.
> > >
> > > https://github.com/apache/pulsar/issues/14365
> > >
> > > Pasted below for quoting convenience.
> > >
> > > -
> > >
> > > Motivation
> > >
> > > The Rest API was originally designed to be implemented asynchronously,
> but
> > > with the iteration of functions, some synchronous implementations were
> > > added, resulting in many asynchronous methods called synchronous
> > > implementations. Also, many synchronous calls do not add timeouts. This
> > > greatly reduces concurrency, user operations, and experience.
> > > In order to prevent more problems, and improve code readability and
> > > maintainability, we intend to refactor these synchronous calls and
> > > standardize the implementation of the API.
> > >
> > > Related discussion:
> > > https://lists.apache.org/thread/pkkz2jgwtzpksp6d4rdm1pyxzb3z6vmg
> > >
> > > Goals
> > >
> > > Try to avoid synchronous method calls in asynchronous methods.
> > > Async variable (AsyncResponse) is placed in the first parameter
> position.
> > > Async variable (AsyncResponse) cannot be substituted into method
> > > implementations.
> > > Add more tests and increase the coverage.
> > > Modification
> > > Avoid synchronous method calls in asynchronous methods.
> > >
> > > protected void internalDeleteNamespace(boolean authoritative) {
> > >validateTenantOperation(namespaceName.getTenant(),
> > > TenantOperation.DELETE_NAMESPACE);
> > >validatePoliciesReadOnlyAccess();
> > > }
> > > Suggest to do like this:
> > >
> > > protected CompletableFuture internalDeleteNamespace(boolean
> > > authoritative) {
> > > return validateTenantOperationAsync(namespaceName.getTenant(),
> > > TenantOperation.DELETE_NAMESPACE)
> > >.thenCompose(__ -> validatePoliciesReadOnlyAccessAsync());
> > > }
> > > Async variable (AsyncResponse) is placed in the first parameter
> position
> > >
> > > public void deleteNamespace(@Suspended final AsyncResponse
> asyncResponse,
> > >  @PathParam("tenant") String tenant,
> > >  @PathParam("namespace") String namespace,
> > >  @QueryParam("force") @DefaultValue("false") boolean force,
> > >  @QueryParam("authoritative") @DefaultValue("false") boolean
> > > authoritative) {
> > >
> > > Async variable (AsyncResponse) cannot be substituted into method
> > > implementations
> > >
> > > internalCreateNonPartitionedTopicAsync(asyncResponse, authoritative,
> > > properties);
> > > Suggest to do like this:
> > >
> > > internalCreateNonPartitionedTopicAsync(authoritative, properties)
> > > .thenAccept(__ ->
> > > asyncResponse.resume(Response.noContent().build()))
> > > .exceptionally(ex -> {
> > > resumeAsyncResponseExceptionally(asyncResponse,
> ex.getCause());
> > > return null;
> > > });
> > >
> > > Task tracking
> > > In order to unify the modification and track the modified part, it's
> better
> > > to open an issue to track, like #14353, #14013, #13854.
> > >
> > > ---
> > > Best,
> > > Mattison
> > >
>

Re: [ANNOUNCE] New Committer: Zike Yang

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:

> Congratulations
>
> Thanks
> ZhangJian He
>
> Ran Gao  于2022年4月18日周一 13:33写道：
>
> > Hi, zike, congratulations!
> >
> > Ran Gao
> >
> > Best
> >
> > On 2022/04/13 09:34:23 PengHui Li wrote:
> > > The Apache Pulsar Project Management Committee (PMC) has invited Zike
> > Yang
> > > https://github.com/RobertIndie to become a committer and we are
> pleased
> > to
> > > announce that he has accepted.
> > >
> > > Welcome and Congratulations, Zike Yang!
> > >
> > > Please join us in congratulating and welcoming Zike Yang onboard!
> > >
> > > Best Regards,
> > > Penghui Li on behalf of the Pulsar PMC
> > >
> >
>

Re: [ANNOUNCE] New Committer: Ruguo Yu

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:

> Congratulations
>
> Thanks
> ZhangJian He
>
> Ran Gao  于2022年4月18日周一 13:34写道：
>
> > Congratulations!
> >
> > Ran
> >
> > Best
> >
> > On 2022/04/15 10:06:44 Yu wrote:
> > > The Apache Pulsar Project Management Committee (PMC) has invited Ruguo
> > Yu (
> > > https://github.com/yuruguo) to become a committer and we are pleased
> to
> > > announce that he has accepted.
> > >
> > > Welcome and Congratulations, Ruguo Yu!
> > >
> > > Please join us in congratulating and welcoming Ruguo Yu onboard!
> > >
> > > Best Regards,
> > >
> > > Yu on behalf of the Pulsar PMC
> > >
> >
>

Re: [ANNOUNCE] New Committer: Zhangmin Gao

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:

> Congratulations
>
> Thanks
> ZhangJian He
>
> r...@apache.org  于2022年4月18日周一 16:59写道：
>
> > Congrats Zhangmin!
> >
> > --
> > Thanks
> > Xiaolong Ran
> >
> > Ran Gao  于2022年4月18日周一 13:41写道：
> >
> > > +1
> > >
> > > Best,
> > > Ran Gao
> > >
> > > On 2022/04/13 09:35:57 PengHui Li wrote:
> > > > The Apache Pulsar Project Management Committee (PMC) has invited
> > Zhangmin
> > > > Gao
> > > > https://github.com/gaozhangmin to become a committer and we are
> > pleased
> > > to
> > > > announce that he has accepted.
> > > >
> > > > Welcome and Congratulations, Zhangmin Gao!
> > > >
> > > > Please join us in congratulating and welcoming Zhangmin Gao onboard!
> > > >
> > > > Best Regards,
> > > > Penghui Li on behalf of the Pulsar PMC
> > > >
> > >
> >
>

[DISCUSSION] PIP-156: Enable system topic by default

[guo jiwei]

Hi community:
   In PIP-39
,
we have introduced namespace event to support topic level policy. This
feature was released in Pulsar 2.6.

   Then PIP-92
,
we support topic policy to replicate across clusters and release in Pulsar
2.10.

And with version iteration, the corresponding topic policy CLI and
functions are mature and stable, but users need to enable system topic to
support these features.  So it's better to enable system topic by default.


So I have opened apache/pulsar#15333
 to discuss this.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] [PIP-154] Max active transaction limitation for transaction coordinator

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Wed, Apr 27, 2022 at 10:52 AM Jiuming Tao 
wrote:

> +1
> Thanks,
> Tao Jiuming
>
> > 2022年4月24日 上午10:00，丛搏  写道：
> >
> > Hi Pulsar community,
> >
> > This is the voting thread for PIP-154. It will stay open for at least 48
> hours.
> >
> > The proposal can be found: https://github.com/apache/pulsar/issues/15133
> >
> > Discuss thread:
> https://lists.apache.org/thread/h8gzgs78bm4pzy2rjtgvvmo1jbzttcx8
> >
> > Thanks,
> > Bo
>
>

Discuss about creating partitioned topic in V1

[guo jiwei]

Hi, community:
   I found that in the admin API V1, it is possible to successfully create
a partitioned topic without a namespace.
However, in V1, when getting the partitioned topic list
(getPartitionedTopicList) and when creating a non-partitioned topic, the
existence of the namespace is checked.
In V2, we all need to check whether the namespace exists.
For consistency, I think creating a partitioned topic in V1 also needs to
check for the existence of the namespace.
So, I push out patch #14858 .
If the patch is passed, the user's existing topics will not be affected,
the newly created partitioned topic will fail, and a namespace needs to be
created first.

Above, I hope you can give some other ideas.


Regards
Jiwei Guo (Tboy)

Re: Discuss about creating partitioned topic in V1

[guo jiwei]

Thanks.
@Matteo I will track this.

Regards
Jiwei Guo (Tboy)


On Tue, May 10, 2022 at 7:37 AM Matteo Merli  wrote:

> Why I agree that it "looks like a bug", "walks like a bug" and "talks
> like a bug"...
> this was actually a "feature" :)
>
> not a good one, or with a good reason to exist, but something we've
> been trying not to break. I'm not going to dig into the "wrong"
> reasoning on why this was done in the first place, unless someone is
> really curious. :D
>
> Having said that, V1 admin API was in effect considered as "soft
> deprecated" since Pulsar 2.0. All documentation has been focused on v2
> APIs.
>
> I believe a better approach now would be to disable v1 APIs using the
> configuration, and actually disabling it by default in next Pulsar
> versions.
>
> Matteo
>
> Instead
> --
> Matteo Merli
> 
>
> On Mon, May 9, 2022 at 12:06 PM Enrico Olivelli 
> wrote:
> >
> > +1
> > I agree totally. It is a bug
> >
> > Enrico
> >
> > Il Lun 9 Mag 2022, 20:59 Michael Marshall  ha
> scritto:
> >
> > > Great find, Jiwei Guo. I agree that this should be classified as a bug
> > > and that we should change the V1 implementation so that a topic can
> > > only be created if its namespace already exists.
> > >
> > > Thanks,
> > > Michael
> > >
> > > On Mon, May 9, 2022 at 7:13 AM guo jiwei  wrote:
> > > >
> > > > Hi, community:
> > > >I found that in the admin API V1, it is possible to successfully
> > > create
> > > > a partitioned topic without a namespace.
> > > > However, in V1, when getting the partitioned topic list
> > > > (getPartitionedTopicList) and when creating a non-partitioned topic,
> the
> > > > existence of the namespace is checked.
> > > > In V2, we all need to check whether the namespace exists.
> > > > For consistency, I think creating a partitioned topic in V1 also
> needs to
> > > > check for the existence of the namespace.
> > > > So, I push out patch #14858 <
> https://github.com/apache/pulsar/pull/14858
> > > >.
> > > > If the patch is passed, the user's existing topics will not be
> affected,
> > > > the newly created partitioned topic will fail, and a namespace needs
> to
> > > be
> > > > created first.
> > > >
> > > > Above, I hope you can give some other ideas.
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > >
>

[VOTE] PIP-156: Enable system topic by default

[guo jiwei]

This is the voting thread for PIP-166. It will stay open for at least 48h.

https://github.com/apache/pulsar/issues/15333

---
## Motivation
In [PIP-39](
https://github.com/apache/pulsar/wiki/PIP-39%3A-Namespace-Change-Events),
we have introduced namespace event to support topic level policy. This
feature was released in Pulsar 2.6.

Then [PIP-92](
https://github.com/apache/pulsar/wiki/PIP-92%3A-Topic-policy-across-multiple-clusters),
we support topic policy to replicate across clusters and release in Pulsar
2.10.

And with version iteration, the corresponding topic policy CLI and
functions are mature and stable, but users need to enable system topic to
support these features.  So it's better to enable system topic by default.

## Proposed changes

In 2.11 release, change :

 *  `systemTopicEnabled`:  false -> true
 *  `topicLevelPoliciesEnabled`: false -> true




Regards
Jiwei Guo (Tboy)

Re: [DISCUSS] Byte schema compatibility issue

[guo jiwei]

Good idea @Yunze
Since `isSchemaValidationEnforced` is only on broker side, I decide to
support it on namespace and topic level.


Regards
Jiwei Guo (Tboy)


On Tue, May 17, 2022 at 11:24 AM Yunze Xu 
wrote:

> For case 1, if you are using bytes schema to produce messages, it will be
> user's responsibility to ensure the schema compatibility. Then at consumer
> side,
> `Message#getValue`, which decodes the bytes internally via the schema,
> should throw a `SchemaSerializationException` if the bytes of the value
> cannot
> Be decoded.
>
> Unfortunately, there is a bug that prevents bytes being decoded and it
> always
> failed before decoding. I opened a PR to fix this issue:
> https://github.com/apache/pulsar/pull/15622
>
> If you don’t want to check the schema compatibility at consumer side, you
> can
> configure `isSchemaValidationEnforced` with true so that the creation of a
> producer
> without schema on a topic with schema will fail.
>
> IMO, bytes schema is treated as “without schema”. The issue is actually:
> - Produce messages without schema
> - Consume messages with schema
>
> If `isSchemaValidationEnforced` is true, the producer cannot be created.
> Otherwise, since we cannot guarantee the format of the message at producer
> side
> and we cannot try to decode it at broker side. The only way is handling
> the error
> at consumer side:
> 1. Decoding the message successfully, return the decoded value.
> 2. Otherwise, throw a `SchemaSerializationException`.
>
> There is no problem with current implementation except what I tried to fix
> in #15622.
>
>
> Thanks,
> Yunze
>
>
>
>
> > 2022年3月8日 10:55，guo jiwei  写道：
> >
> > Hi,
> >   I want to discuss the compatibility issue with the byte schema here.
> >   For now, the byte-schema is compatible with all other schemas. This may
> > introduce more issues.
> >   Case 1:
> >  1. Consumer1 init with JSON schema for topic A.
> >  2. But producer1 init without schema and send byte messages
> > directly to topic A.
> >  This will cause consumer1 to deserialize msg error.  Also,
> > producer1 may send unsafe byte data.
> >
> > Case 2:
> >   1. Consumer1 init with byte schema for topic A.
> >   2. But producer1 init with AVRO/JSON schema and send messages
> to
> > topic A.
> >   This will cause consumer1 don't know how to deserialize msg.
> >
> >To avoid the above issues, Byte schema should also follow the schema
> > compatibility policy. I'm open #13701
> > <https://github.com/apache/pulsar/issues/13701> to track this. If the
> idea
> > is accepted, I will start a PIP.
> >
> > Please give some suggestions about this idea.
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
>
>

Discuss about closing Pulsar resource

[guo jiwei]

Hi community:
In the past few days, when investigating the problem of pulsar close
being hung, I saw that many resources are called synchronously and have no
timeout when they are closed. To solve this problem,
patch-15638 , add the async
close method and timeout.
patch-15680 , uniformly
increase the timeout in the pulsar close method.
patch-15777 , add timeout in
the close method.
However, neither increasing the async interface nor the timeout is
guaranteed to shut down the pulsar service within `brokerShutdownTimeoutMs`.

In order to ensure the uniformity of resource closure, I hope to discuss
with you a relatively reasonable solution.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-165: Auto release client useless connections

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Wed, Jun 1, 2022 at 3:12 PM Yubiao Feng
 wrote:

> Hi Pulsar Community:
>
> There were some mistakes in the last email, so I have corrected them.
>
> I would like to start a VOTE on "Auto release client useless connections"
> (PIP-165).
>
> Proposal Link: [PIP-165] Auto release client useless connections · Issue
> #15516 · apache/pulsar (github.com)
> 
>
> Discuss Link: [DISCUSS] [PIP-165] Auto release client useless
> connections-Apache Mail Archives
> 
>
> Voting will stay open for at least 48h.
> Thanks, Yubiao Feng
>
> On Wed, Jun 1, 2022 at 2:40 PM Yubiao Feng 
> wrote:
>
> > [VOTE] PIP-165: Auto release client useless connectionsHi Pulsar
> > Community, I would like to start a VOTE on "Auto release client useless
> > connections" (PIP-165). The proposal can be read at
> > https://github.com/apache/pulsar/issues/15516
> >  and the discussion thead
> > is available at
> > https://lists.apache.org/thread/t6h98qs2coc56z06tw38hdlljl67ft4n
> >   Voting will stay open for at least 48h. Thanks, Yubiao Feng
> >
>

Re: Batch Messages with only 1 message

[guo jiwei]

+1
Good idea

Regards
Jiwei Guo (Tboy)


On Tue, Jul 12, 2022 at 9:07 PM PengHui Li  wrote:

> +1
>
> We should start with a proposal, so that we can clear on the
>
> On Tue, Jul 12, 2022 at 5:50 PM ZhangJian He  wrote:
>
> > +1
> >
> > Thanks
> > ZhangJian He
> >
> > Qiang Huang  于2022年7月12日周二 17:34写道：
> >
> > > +1
> > > Good idea! It will greatly reduce the resource consumption of small
> > > batches.
> > >
> > > Yubiao Feng  于2022年7月12日周二
> 16:00写道：
> > >
> > > > +1
> > > > Good idea.
> > > >
> > > > Thanks
> > > > Yubiao Feng
> > > >
> > > > On Tue, Jul 12, 2022 at 3:54 PM Enrico Olivelli  >
> > > > wrote:
> > > >
> > > > > Hello,
> > > > > I think that we could implement a small but effective enhancement
> to
> > > > > batching.
> > > > >
> > > > > It may happen that even if you enable batching you come to create
> > > > > entries with 1 only message.
> > > > >
> > > > > Processing batch messages requires a good amount of resources, both
> > on
> > > > > the broker and on the client side.
> > > > >
> > > > > Especially when you are using PIP-105, Broker side filtering, you
> > have
> > > > > to unpack (and decompress) the whole entry in order to process the
> > > > > very single message.
> > > > >
> > > > > So my proposal is to change the (Java) producer, to make it
> produce a
> > > > > regular message instead of a batch message if the batch contains
> only
> > > > > 1 message
> > > > >
> > > > > Thoughts ?
> > > > >
> > > > > Enrico
> > > > >
> > > >
> > >
> > >
> > > --
> > > BR,
> > > Qiang Huang
> > >
> >
>

Re: [VOTE] Enable GitHub Discussion for user-facing discussion

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Tue, Jul 12, 2022 at 9:53 PM Enrico Olivelli  wrote:

> +1
>
>
> Enrico
>
> Il giorno mar 12 lug 2022 alle ore 13:05 Yu  ha scritto:
> >
> > Hi tison, thanks for creating this vote!
> > I thought we reached a lay consensus since there was no objection since
> the
> > last discussion [1]
> >
> > +1 for this proposal.
> > I've explained the reasons and showed the benefits previously [2]
> >
> > [1] https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn
> > [2] https://lists.apache.org/thread/83pst643h9cqcryo3zsjd240jmqzvn73
> >
> > On Tue, Jul 12, 2022 at 6:01 PM tison  wrote:
> >
> > > Hi,
> > >
> > > In the previous email[1] I started a discussion about enabling GitHub
> > > Discussions in apache/pulsar repository and we meet a consensus to
> avoid
> > > making development discussions truth happen on the sources. It's also a
> > > requirement of INFRA team[2]
> > >
> > > Apart of it, for user-facing discussions it's conventions for Pulsar
> users
> > > who have a GitHub account but are unfamiliar with mailing list to throw
> > > their use case and questions on GitHub discussion.
> > >
> > > Dave has opened and issue[2][3] and prepare the patch[4] for turning
> on the
> > > discussion option but obviously we still need an explicit consensus
> among
> > > the community and it's also required before INFRA team takes action.
> > >
> > > I'd like to start this voting thread for "Enable GitHub Discussion for
> > > user-facing discussion", please reply with your opinion:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Best,
> > > tison.
> > >
> > > [1] https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn
> > > [2] https://issues.apache.org/jira/browse/INFRA-23477
> > > [3] https://github.com/apache/pulsar/issues/16275
> > > [4] https://github.com/apache/pulsar/pull/16528
> > >
>

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

[guo jiwei]

+1 (non-binding)

- Download links are valid.
- Checksums and signatures.
- LICENSE/NOTICE/exist
- Rat check passes
- Compile source with JDK11
- Run standalone, and run pulsar produce/consume


Regards
Jiwei Guo (Tboy)


On Wed, Jul 13, 2022 at 11:24 PM Hang Chen  wrote:

> +1 (binding)
>
> - Checked the checksum and license
> - Build from source code with JDK 11
> - Run standalone, and run pulsar-perf produce/consume
> - Verified pulsar-io-lakehouse connector
>
> Thanks,
> Hang
>
> PengHui Li  于2022年7月8日周五 23:01写道：
> >
> > +1 binding
> >
> > - checked the signature
> > - run standalone and test produce/consume
> > - verified function and stateful function
> > - verified the Cassandra connector
> >
> > Thanks,
> > Penghui
> >
> > On Fri, Jul 8, 2022 at 8:16 PM Nicolò Boschi 
> wrote:
> >
> > > +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.huang1...@gmail.com> ha scritto:
> > >
> > > > +1
> > > >
> > > > Enrico Olivelli  于2022年7月8日周五 19:42写道：
> > > >
> > > > > +1 (binding)
> > > > > - built from sources, with JDK11, run a couple of smoke tests
> > > > > - verified RAT
> > > > > - verified checksums and signatures
> > > > > - run some JMS tests using Transactions (the JMS library bundles
> > > > > 2.10.x Java client)
> > > > >
> > > > > Thanks for driving the release!
> > > > >
> > > > > Enrico
> > > > >
> > > > > Enrico
> > > > >
> > > > > Il giorno mer 6 lug 2022 alle ore 10:26 mattison chao
> > > > >  ha scritto:
> > > > > >
> > > > > > This is the second release candidate for Apache Pulsar, version
> > > 2.9.3.
> > > > > >
> > > > > > It fixes the following issues:
> > > > > >
> > > > >
> > > >
> > >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> > > > > <
> > > > >
> > > >
> > >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> > > > > >
> > > > > >
> > > > > > *** Please download, test and vote on this release. This vote
> will
> > > stay
> > > > > open
> > > > > > for at least 72 hours ***
> > > > > >
> > > > > > Note that we are voting upon the source (tag), binaries are
> provided
> > > > for
> > > > > > convenience.
> > > > > >
> > > > > > Source and binary files:
> > > > > >
> > > > > >
> > > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.3-candidate-2/
> > > > > >
> > > > > > SHA-512 checksums:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> 291eb3f9da234cf38fcd02de781def9a9354025bb4f98c78b160935a6a9c6721cc8280d80b93049656ee5a20e36ddc5d3446b7b034405c07d447833ff65e
> > > > > ./apache-pulsar-2.9.3-bin.tar.gz
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> d57fa3c8eae1f3ba60422a56288c99a472a671295e41573c884a9d9a71b5fcf622782732e9cfd5128e1b92304b3812cc877675384ac0dbc78109d7efb23681f4
> > > > > ./apache-pulsar-2.9.3-src.tar.gz
> > > > > >
> > > > > > Maven staging repo:
> > > > > >
> > > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1163/
> > > > > >
> > > > > > The tag to be voted upon:
> > > > > > v2.9.3-candidate-2 (dd9a5f1f91651b634600f66c53dcc6ad855fb669)
> > > > > >
> > > > > > https://github.com/apache/pulsar/releases/tag/v2.9.3-candidate-2
> > > > > >
> > > > > > The docker images:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> https://hub.docker.com/layers/248117318/mattison/pulsar/2.9.3-rc-2/images/sha256-a7ac6d5ffb2d77102ca6633313c9d0265c1c89c8b0fe859023fbaf3e0d0a7910?context=repo
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> https://hub.docker.com/layers/247907545/mattison/pulsar-all/2.9.3-rc-2/images/sha256-00e6a886a9285107027afb4c3218c9340efb96627100ff2f1c95d1177bd8dbbe?context=repo
> > > > > >
> > > > > > Pulsar's KEYS file containing PGP keys we use to sign the
> release:
> > > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> > > > > >
> > > > > > Please download the source package, and follow the Release
> Candidate
> > > > > > Validation[1]
> > > > > > to validate the release
> > > > > >
> > > > > > [1]
> > > https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
> > > > <
> > > > > https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
> >
> > > > >
> > > >
> > > >
> > > > --
> > > > BR,
> > > > Qiang Huang
> > > >
> > >
>

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

I will take the release

Regards
Jiwei Guo (Tboy)


On Fri, Jul 22, 2022 at 12:37 AM Nicolò Boschi  wrote:

> 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 in progress targeted for
> 2.11
> > by the mid of August and then start the code freezing as described in the
> > PIP.
> >
> > So the target release date will be early September. One point is Pulsar
> > Summit
> > San Francisco will start on August 18, 2022. I think maybe we can start
> to
> > test
> > the master branch for now and continue the in-progress tasks. If we can
> > have a
> > major release before Pulsar Summit, it should be good news to the
> > Community.
> >
> > Thanks.
> > Penghui
> >
> > On Mon, Jul 18, 2022 at 4:06 PM Enrico Olivelli 
> > wrote:
> >
> > > Nicolò,
> > >
> > > Il Lun 18 Lug 2022, 10:00 Nicolò Boschi  ha
> > scritto:
> > >
> > > > Thanks Penghui for the reminder.
> > > > I'd like to also include PIP: 181 Pulsar shell if the time permits.
> > > >
> > > > I believe that is a good idea to start testing the code freeze
> proposed
> > > by
> > > > PIP-175 (https://github.com/apache/pulsar/issues/15966). Even if not
> > > > officially approved, we discussed it many times and agreed to the
> > > > usefulness of the code freezing.
> > > >
> > >
> > > Great idea!
> > >
> > > We should really try it
> > >
> > > 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 for volunteering
> > >
> > > Enrico
> > >
> > >
> > > > Thanks,
> > > > Nicolò Boschi
> > > >
> > > >
> > > > Il giorno lun 18 lug 2022 alle ore 06:59 Yunze Xu
> > > >  ha scritto:
> > > >
> > > > > In addition to #16202, there is a following PR to support the
> correct
> > > > > ACK implementation for chunked messages. It should depend on #16202
> > > > > But I think I can submit an initial PR this week and change the
> tests
> > > > > after #16202 is merged.
> > > > >
> > > > > Thanks,
> > > > > Yunze
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > 2022年7月18日 11:22，PengHui Li  写道：
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > We released 2.10.0 three months ago. And there are many great
> > changes
> > > > in
> > > > > > the master branch,
> > > > > > including new features and performance improvements.
> > > > > >
> > > > > > - PIP 74: apply client memory to consumer
> > > > > > https://github.com/apache/pulsar/pull/15216
> > > > > > - PIP 143: Support split bundles by specified boundaries
> > > > > > https://github.com/apache/pulsar/pull/13796
> > > > > > - PIP 145: regex subscription improvements
> > > > > > https://github.com/apache/pulsar/pull/16062
> > > > > > - PIP 160: transaction performance improvements (still in
> progress
> > > and
> > > > > > merged some PRs)
> > > > > > - PIP 161: new exclusive producer mode support
> > > > > > https://github.com/apache/pulsar/pull/15488
> > > > > > - PIP 182: Provide new load balance placement strategy
> > implementation
> > > > for
> > > > > > ModularLoadManagerStrategy
> > > https://github.com/apache/pulsar/pull/16281
> > > > > > Add Pulsar Auth support for the Pulsar SQL
> > > > > > https://github.com/apache/pulsar/pull/15571
> > > > > >
> > > > > > And some features are blocked in the review stage, but they are
> > > > powerful
> > > > > > improvements for Pulsar
> > > > > >
> > > > > > PIP 37: Support chunking with Shared subscription
> > > > > > https://github.com/apache/pulsar/pull/16202
> > > > > > PIP-166: Function add MANUAL delivery semantics
> > > > > > https://github.com/apache/pulsar/pull/16279
> > > > > >
> > > > > > You can find the complete change list in 2.11.0 at
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A2.11.0+-label%3Arelease%2F2.10.1+-label%3Arelease%2F2.10.2
> > > > > >
> > > > > > And maybe I missed some important in-progress PRs, please let me
> > know
> > > > if
> > > > > it
> > > > > > should be a blocker of the 2.11.0 release.
> > > > > >
> > > > > > It's a good time to discuss the target time of the 2.11.0
> release.
> > > > > > I think we can leave 2 weeks to complete the in-progress PRs and
> 2
> > > > weeks
> > > > > to
> > > > > > accept bug fixes.
> > > > > > And target the 2.11.0 release in mid-August.
> > > > > >
> > > > > > Please let me know what you think.
> > > > > >
> > > > > > Thanks,
> > > > > > Penghui
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] PIP-184: Topic specific consumer priorityLevel

[guo jiwei]

+1

Regards
Jiwei Guo (Tboy)


On Mon, Jul 18, 2022 at 10:54 AM PengHui Li  wrote:

> +1
>
> Penghui
>
> On Mon, Jul 18, 2022 at 10:15 AM Zike Yang  wrote:
>
> > +1
> >
> > Thanks
> >
> >
> > On Fri, Jul 15, 2022 at 3:58 PM Dave Maughan
> >  wrote:
> > >
> > > Hi Pulsar Community
> > >
> > > I would like to start a VOTE on "PIP-184: Topic specific consumer
> > > priorityLevel".
> > >
> > > The proposal can be read at
> > https://github.com/apache/pulsar/issues/16481
> > >
> > > and the discussion thread is available at
> > > https://lists.apache.org/thread/5zs4gd3r0rtzz16nv62o8ntygg01qjhq
> > >
> > > Voting will stay open for at least 48h.
> > >
> > > Thanks,
> > > Dave
> >
>

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

[guo jiwei]

Congrats Michael!


Regards
Jiwei Guo (Tboy)


On Wed, Jul 27, 2022 at 9:56 AM Haiting Jiang 
wrote:

> Congratulations, Michael!
>
> BR,
> Haiting
>
> On 2022/07/26 15:21:59 Enrico Olivelli wrote:
> > I am glad to announce that the Apache Pulsar PMC invited Micheal to
> > join the PMC and he accepted.
> >
> > Micheal is doing a great job in stewarding our community
> >
> > Please join me and celebrate !
> >
> > Enrico Olivelli
> >
>

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

Hi all,

Put an update here, we have created branch-2.11[1].

[1] https://github.com/apache/pulsar/tree/branch-2.11


Regards
Jiwei Guo (Tboy)


On Wed, Jul 27, 2022 at 10:59 AM Zixuan Liu  wrote:

> +1
>
> Thanks,
> Zixuan
>
> Yunze Xu  于2022年7月26日周二 23:34写道：
>
> > I opened a PR https://github.com/apache/pulsar/pull/16803 that might be
> > the blocker
> > of the release of 2.11.0, PTAL.
> >
> > Thanks,
> > Yunze
> >
> >
> >
> >
> > > 2022年7月22日 18:21，Zixuan Liu  写道：
> > >
> > > +1
> > >
> > > Thanks,
> > > Zixuan
> > >
> > > Enrico Olivelli  于2022年7月22日周五 18:06写道：
> > >
> > >> Il giorno ven 22 lug 2022 alle ore 12:05 guo jiwei
> > >>  ha scritto:
> > >>>
> > >>> I will take the release
> > >>
> > >> Thanks !
> > >>
> > >> Enrico
> > >>
> > >>>
> > >>> Regards
> > >>> Jiwei Guo (Tboy)
> > >>>
> > >>>
> > >>> On Fri, Jul 22, 2022 at 12:37 AM Nicolò Boschi  >
> > >> wrote:
> > >>>
> > >>>> 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 in progress targeted
> > >> for
> > >>>> 2.11
> > >>>>> by the mid of August and then start the code freezing as described
> > >> in the
> > >>>>> PIP.
> > >>>>>
> > >>>>> So the target release date will be early September. One point is
> > >> Pulsar
> > >>>>> Summit
> > >>>>> San Francisco will start on August 18, 2022. I think maybe we can
> > >> start
> > >>>> to
> > >>>>> test
> > >>>>> the master branch for now and continue the in-progress tasks. If we
> > >> can
> > >>>>> have a
> > >>>>> major release before Pulsar Summit, it should be good news to the
> > >>>>> Community.
> > >>>>>
> > >>>>> Thanks.
> > >>>>> Penghui
> > >>>>>
> > >>>>> On Mon, Jul 18, 2022 at 4:06 PM Enrico Olivelli <
> eolive...@gmail.com
> > >>>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Nicolò,
> > >>>>>>
> > >>>>>> Il Lun 18 Lug 2022, 10:00 Nicolò Boschi  ha
> > >>>>> scritto:
> > >>>>>>
> > >>>>>>> Thanks Penghui for the reminder.
> > >>>>>>> I'd like to also include PIP: 181 Pulsar shell if the time
> > >> permits.
> > >>>>>>>
> > >>>>>>> I believe that is a good idea to start testing the code freeze
> > >>>> proposed
> > >>>>>> by
> > >>>>>>> PIP-175 (https://github.com/apache/pulsar/issues/15966). Even
> > >> if not
> > >>>>>>> officially approved, we discussed it many times and agreed to the
> > >>>>>>> usefulness of the code freezing.
> > >>>>>>>
> > >>>>>>
> > >>>>>> Great idea!
> > >>>>>>
> > >>>>>> We should really try it
> > >>>>>>
> > >>>>>> 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
> > >>>>>>>
> > 

Re: [Vote] PIP-192 New Pulsar Broker Load Balancer

[guo jiwei]

+1

Regards
Jiwei Guo (Tboy)


On Tue, Aug 9, 2022 at 3:12 PM Qiang Huang 
wrote:

> +1 (non-binding)
>
> Kai Wang  于2022年8月5日周五 10:18写道：
>
> > +1 (non-binding)
> >
> > Thanks,
> > Kai
> >
> > Heesung Sohn  于2022年8月2日周二
> 08:50写道：
> >
> > > Dear Pulsar Community,
> > >
> > > Please review and vote on this PIP.
> > >
> > > PIP link: https://github.com/apache/pulsar/issues/16691
> > >
> > > Thank you,
> > > -Heesung
> > >
> >
>
>
> --
> BR,
> Qiang Huang
>

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

Thanks for Yunze's help for fixing rpm and deb packaging.


Regards
Jiwei Guo (Tboy)


On Wed, Aug 10, 2022 at 11:02 PM Yunze Xu 
wrote:

> I found the scripts to build rpm and deb packages are broken, see
>
> https://github.com/apache/pulsar/wiki/Release-process#31-build-rpm-and-deb-packages
> .
>
> It's caused by https://github.com/apache/pulsar/pull/15376 and only
> affects the 2.11.0 release and higher versions. It should be a blocker
> for 2.11.0 release. I'm working on this issue at the moment and going
> to push a fix soon, as well as the CI to protect the rpm/deb packaging
> to avoid the regression.
>
> Thanks,
> Yunze
>
>
>
>
> > 2022年8月4日 23:44，guo jiwei  写道：
> >
> > Hi all,
> >
> > Put an update here, we have created branch-2.11[1].
> >
> > [1] https://github.com/apache/pulsar/tree/branch-2.11
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Wed, Jul 27, 2022 at 10:59 AM Zixuan Liu  wrote:
> >
> >> +1
> >>
> >> Thanks,
> >> Zixuan
> >>
> >> Yunze Xu  于2022年7月26日周二 23:34写道：
> >>
> >>> I opened a PR https://github.com/apache/pulsar/pull/16803 that might
> be
> >>> the blocker
> >>> of the release of 2.11.0, PTAL.
> >>>
> >>> Thanks,
> >>> Yunze
> >>>
> >>>
> >>>
> >>>
> >>>> 2022年7月22日 18:21，Zixuan Liu  写道：
> >>>>
> >>>> +1
> >>>>
> >>>> Thanks,
> >>>> Zixuan
> >>>>
> >>>> Enrico Olivelli  于2022年7月22日周五 18:06写道：
> >>>>
> >>>>> Il giorno ven 22 lug 2022 alle ore 12:05 guo jiwei
> >>>>>  ha scritto:
> >>>>>>
> >>>>>> I will take the release
> >>>>>
> >>>>> Thanks !
> >>>>>
> >>>>> Enrico
> >>>>>
> >>>>>>
> >>>>>> Regards
> >>>>>> Jiwei Guo (Tboy)
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Jul 22, 2022 at 12:37 AM Nicolò Boschi <
> boschi1...@gmail.com
> >>>
> >>>>> wrote:
> >>>>>>
> >>>>>>> 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 in progress targeted
> >>>>> for
> >>>>>>> 2.11
> >>>>>>>> by the mid of August and then start the code freezing as described
> >>>>> in the
> >>>>>>>> PIP.
> >>>>>>>>
> >>>>>>>> So the target release date will be early September. One point is
> >>>>> Pulsar
> >>>>>>>> Summit
> >>>>>>>> San Francisco will start on August 18, 2022. I think maybe we can
> >>>>> start
> >>>>>>> to
> >>>>>>>> test
> >>>>>>>> the master branch for now and continue the in-progress tasks. If
> we
> >>>>> can
> >>>>>>>> have a
> >>>>>>>> major release before Pulsar Summit, it should be good news to the
> >>>>>>>> Community.
> >>>>>>>>
> >>>>>>>> Thanks.
> >>>>>>>> Penghui
> >>>>>>>>
> >>>>>>>> On Mon, Jul 18, 2022 at 4:06 PM Enrico Olivelli <
> >> eolive...@gmail.com
> >>>>>>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Nicolò,
> >>>>>>>>>
> >>>>>>>>> Il Lun 18 Lug 2022, 10:00 Nicolò Boschi 
> ha
> >>>>>>>> s

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

[guo jiwei]

Thank you all!
I will continue to contribute to the project and the community in a new way.

Regards
Jiwei Guo (Tboy)


On Thu, Aug 18, 2022 at 11:18 PM Enrico Olivelli 
wrote:

> Congratulations !
>
>
> Enrico
>
> Il giorno gio 18 ago 2022 alle ore 17:10 Cong Zhao
>  ha scritto:
> >
> > Congratulations!
> >
> > Thanks,
> > Cong Zhao
> >
> > On 2022/08/18 11:24:01 PengHui Li wrote:
> > > Hi, all
> > >
> > > I'm glad to announce that the Apache Pulsar PMC invited Jiwei Guo to
> join
> > > the
> > > PMC and he accepted.
> > >
> > > Please join in celebrating!
> > >
> > > Best,
> > > Penghui
> > >
>

Re: [VOTE]PIP-189: No batching if only one message in batch.

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Aug 8, 2022 at 11:17 AM PengHui Li  wrote:

> +1 (binding)
>
> Penghui
>
> On Tue, Jul 26, 2022 at 10:23 PM Zike Yang  wrote:
>
> > +1 (non-binding)
> > Great work!
> >
> > Thanks
> > Zike Yang
> >
> > On Tue, Jul 26, 2022 at 7:31 PM Enrico Olivelli 
> > wrote:
> > >
> > > +1 (binding)
> > >
> > > This is a small improvement but a great impact !!
> > >
> > > Enrico
> > >
> > > Il giorno mar 26 lug 2022 alle ore 12:48 Anon Hxy
> > >  ha scritto:
> > > >
> > > > Hi Zike
> > > >
> > > > Thanks for your reminding.  I just forgot to update the issue and
> have
> > > > updated it now.  I am not going to add the configuration
> > > > `batchingSingleMessage ` to the producer.
> > > >
> > > > Thanks,
> > > > Xiaoyu Hou
> > > >
> > > > Zike Yang  于2022年7月26日周二 18:16写道：
> > > >
> > > > > Hi, Anon
> > > > >
> > > > > So are you going to add the configuration `batchingSingleMessage `
> to
> > > > > the producer? I saw that it was still in the PIP:
> > > > >
> > > > > > So this may cause  ((BatchMessageIdImpl) messageId) throw
> > > > > ClassCastException.  we need to add a switch for the producer to
> > enable or
> > > > > disable this feature
> > > > > > ProducerBuilder batchingSingleMessage(boolean
> > > > > batchingSingleMessage);  // default value is true
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Zike Yang
> > > > >
> > > > > On Tue, Jul 26, 2022 at 6:05 PM Qiang Huang <
> > qiang.huang1...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > +1(non-binding)
> > > > > >
> > > > > > BR,
> > > > > > Qiang Huang
> > > > > >
> > > > > > mattison chao  于2022年7月25日周一 13:17写道：
> > > > > >
> > > > > > > +1(non-binding)
> > > > > > >
> > > > > > > Best,
> > > > > > > Mattison
> > > > > > >
> > > > > > > On Mon, 25 Jul 2022 at 10:35, Haiting Jiang <
> > jianghait...@apache.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > +1
> > > > > > > > Thanks,
> > > > > > > > Haiting
> > > > > > > >
> > > > > > > > On 2022/07/25 02:23:20 Anon Hxy wrote:
> > > > > > > > > Dear Community,
> > > > > > > > >
> > > > > > > > > I would like to start a VOTE on "PIP-189: No batching if
> > only one
> > > > > > > message
> > > > > > > > > in batch."
> > > > > > > > >
> > > > > > > > > The proposal can be read at [0] and the discussion thread
> is
> > > > > available
> > > > > > > at
> > > > > > > > > [1] and the PR link is available at [2]
> > > > > > > > >
> > > > > > > > > Voting will stay open for at least 48h.
> > > > > > > > >
> > > > > > > > > [0] https://github.com/apache/pulsar/issues/16619
> > > > > > > > > [1]
> > > > > https://lists.apache.org/thread/dbq1lrv03bhtk0lr5nwm5txo9ndjplv0
> > > > > > > > > [2] https://github.com/apache/pulsar/pull/16605
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Xiaoyu
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > BR,
> > > > > > Qiang Huang
> > > > >
> >
>

Re: [VOTE] Pulsar Release 2.7.5 Candidate 2

[guo jiwei]

+1 (binding)

 - Checked signatures/checksums
 - Checked the license headers
 - Build sources
-  Ran the standalone.
 - Validate Connectors
 - Validate Pub/Sub and Java Functions
 - Validate Stateful Functions


Regards
Jiwei Guo (Tboy)


On Sun, Aug 14, 2022 at 11:01 AM Qiang Huang 
wrote:

> +1 (non-binding)
>
> Haiting Jiang  于2022年8月13日周六 00:27写道：
>
> > Here is the docker images:
> >
> >
> >
> https://hub.docker.com/layers/271293864/jason918/pulsar/2.7.5/images/sha256-8863429ae891cfdac609455992105427188ccadef98723819c882644084748c9
> >
> >
> >
> https://hub.docker.com/layers/271294049/jason918/pulsar-all/2.7.5/images/sha256-db90c52962abd7314973242e272b91be36c1ac34a206db482575fc65d9f3abaf
> >
> > Thanks,
> > Haiting
> >
> > On 2022/08/12 07:50:43 Haiting Jiang wrote:
> > > This is the second release candidate for Apache Pulsar, version 2.7.5.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar/compare/v2.7.4...v2.7.5-candidate-2
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > open
> > > for at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.5-candidate-2/
> > >
> > > SHA-512 checksums:
> > >
> > >
> >
> 50ab0c3fd954fd1911c84917be411302e8b4dd1afca8b6af67df6d4f4f74ea43125dd18c2bc84aa62b635ff3ca21c54d59085a89ef029d15e7f078854958edb5
> > > apache-pulsar-2.7.5-bin.tar.gz
> > >
> >
> 9d8a327a728b917513b492cda585c11423705261e7f6a13d1c9e33a991b4e6f60b9aae7179a24c56e1c7bf0136d9fb64199e8b7952f2a63e8ed98bb518a05988
> > > apache-pulsar-2.7.5-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1171/
> > >
> > > The tag to be voted upon:
> > > v2.7.5-candidate-2 (43a8436ca6cd6604cd25174d7388390bcd5d6b12)
> > > https://github.com/apache/pulsar/releases/tag/v2.7.5-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.
> > >
> > > Thanks,
> > > Haiting
> > >
> >
>
>
> --
> BR,
> Qiang Huang
>

Re: [VOTE] Pulsar Release 2.8.4 Candidate 1

[guo jiwei]

+1 (binding)

- Checked checksums and signatures
- Checked license headers using Apache Rat
- Compiled the source by JDK11
- Ran the standalone server
- Confirmed that producer and consumer work properly
- Validated functions, connectors, and stateful functions


Regards
Jiwei Guo (Tboy)


On Mon, Aug 15, 2022 at 10:18 AM Qiang Huang 
wrote:

> Got it. Thx.
>
> Yunze Xu  于2022年8月14日周日 23:22写道：
>
> > You can see
> > https://lists.apache.org/thread/rg1g083c06ozm5go6zo1jophg9y9zl2f
> > for more details about the LTS release.
> >
> > Thanks,
> > Yunze
> >
> >
> >
> >
> > > 2022年8月14日 11:00，Qiang Huang  写道：
> > >
> > > +1 (non-binding)
> > > Is 2.8.4 a long term support release?
> > >
> > > Yunze Xu  于2022年8月12日周五 16:20写道：
> > >
> > >> This is the first release candidate for Apache Pulsar, version 2.8.4.
> > >>
> > >> It fixes the following issues:
> > >>
> > >>
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.8.4
> > >>
> > >> *** Please download, test and vote on this release. This vote will
> stay
> > >> open
> > >> for at least 72 hours ***
> > >>
> > >> Note that we are voting upon the source (tag), binaries are provided
> for
> > >> convenience.
> > >>
> > >> Source and binary files:
> > >>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.8.4-candidate-1/
> > >>
> > >> SHA-512 checksums:
> > >>
> > >>
> >
> c3d26704f2cfb3365c29d4110612ca7351084f8bee3c306d5e906b3f9b22c7557cc5baf12f74f8c222baccae3310691419eda5b47fdf9cd6c5281b70134ab5eb
> > >> apache-pulsar-2.8.4-bin.tar.gz
> > >>
> >
> 28160ee94dccfb74dfb56e0e5d0e08870c6612659507333a52b5660ecbf060a75d1eed667cffd8596f9468de95055b78916b932db0e0d4c2745868d55429ee98
> > >> apache-pulsar-2.8.4-src.tar.gz
> > >>
> > >> Maven staging repo:
> > >>
> > https://repository.apache.org/content/repositories/orgapachepulsar-1170/
> > >>
> > >> The tag to be voted upon:
> > >> v2.8.4-candidate-1 (02ee5616866d4eda8dd94f85d9d9b71c459f248d)
> > >> https://github.com/apache/pulsar/releases/tag/v2.8.4-candidate-1
> > >>
> > >> Pulsar's KEYS file containing PGP keys we use to sign the release:
> > >> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > >>
> > >> Docker images:
> > >>
> > >>
> > >>
> >
> https://hub.docker.com/layers/pulsar/bewaremypower/pulsar/2.8.4/images/sha256-fba51a75c0f2ca79fbff7b254f80f641fcda661fd702f8149bbfdd5994078e3a
> > >>
> > >>
> > >>
> >
> https://hub.docker.com/layers/pulsar-all/bewaremypower/pulsar-all/2.8.4/images/sha256-42d4b41e5869edc6242bb49d6a1687bd6d191a6385637122edc5c7b2c44ee46f
> > >>
> > >> Please download the source package, and follow the Release Candidate
> > >> Validation[1] to validate the release
> > >>
> > >> [1]
> https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
> > >>
> > >> Thanks,
> > >> Yunze
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > > --
> > > BR,
> > > Qiang Huang
> >
> >
>
> --
> BR,
> Qiang Huang
>

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

Hi all,
   We have merged all the blocker patches, and I decide to start the
release.
   The release note[1] for 2.11.0 is available for review, please help
review it and feel free to leave comments.


[1] https://github.com/apache/pulsar-site/pull/167


Regards
Jiwei Guo (Tboy)


On Wed, Aug 17, 2022 at 10:43 PM Enrico Olivelli 
wrote:

> This test is blocking all the PRs and so it is blocking the release:
> Error: Tests run: 9, Failures: 2, Errors: 0, Skipped: 3, Time elapsed:
> 21.724 s <<< FAILURE! - in
> org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest
> 3681 Error:
> testParallelSubscribeAsync(org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest)
> Time elapsed: 5.05 s <<< FAILURE!
> org.testng.internal.thread.ThreadTimeoutException: Method
>
> org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest.testParallelSubscribeAsync()
> didn't finish within the time-out 5000
>
>
> Enrico
>
> Il giorno mer 17 ago 2022 alle ore 14:40 Nicolò Boschi
>  ha scritto:
> >
> > 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 blocker PR that is waiting for CI
> > > https://github.com/apache/pulsar/pull/17118
> > > the problem is about a new API that has been introduced in 2.11 but
> > > the API has a little problem and we must fix it before the API to be
> > > released to the public
> > >
> > > Enrico
> > >
> > > Il giorno mar 16 ago 2022 alle ore 10:13 guo jiwei
> > >  ha scritto:
> > > >
> > > > Thanks for Yunze's help for fixing rpm and deb packaging.
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > > >
> > > > On Wed, Aug 10, 2022 at 11:02 PM Yunze Xu
> 
> > > > wrote:
> > > >
> > > > > I found the scripts to build rpm and deb packages are broken, see
> > > > >
> > > > >
> > >
> https://github.com/apache/pulsar/wiki/Release-process#31-build-rpm-and-deb-packages
> > > > > .
> > > > >
> > > > > It's caused by https://github.com/apache/pulsar/pull/15376 and
> only
> > > > > affects the 2.11.0 release and higher versions. It should be a
> blocker
> > > > > for 2.11.0 release. I'm working on this issue at the moment and
> going
> > > > > to push a fix soon, as well as the CI to protect the rpm/deb
> packaging
> > > > > to avoid the regression.
> > > > >
> > > > > Thanks,
> > > > > Yunze
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > 2022年8月4日 23:44，guo jiwei  写道：
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Put an update here, we have created branch-2.11[1].
> > > > > >
> > > > > > [1] https://github.com/apache/pulsar/tree/branch-2.11
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > > Jiwei Guo (Tboy)
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 27, 2022 at 10:59 AM Zixuan Liu 
> > > wrote:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Zixuan
> > > > > >>
> > > > > >> Yunze Xu  于2022年7月26日周二 23:34写道：
> > > > > >>
> > > > > >>> I opened a PR https://github.com/apache/pulsar/pull/16803 that
> > > might
> > > > > be
> > > > > >>> the blocker
> > > > > >>> of the release of 2.11.0, PTAL.
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> Yunze
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>> 2022年7月22日 18:21，Zixuan Liu  写道：
> > > > > >>>>
> > > > > >>>> +1
> > > > > >>>>
> > > > > >>>&

Re: [VOTE] [PIP-169] Support split bundle by flow or qps

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, Aug 24, 2022 at 1:01 AM Heesung Sohn
 wrote:

> +1 (non-binding)
>
> Heesung
>
> On Tue, Aug 23, 2022 at 10:00 AM Anon Hxy  wrote:
> >
> > +1 (non-binding)
> >
> > Thanks,
> > Xiaoyu Hou
> >
> > lordcheng10 <1572139...@qq.com.invalid> 于2022年8月23日周二 15:10写道：
> >
> > > Hi Pulsar Community, I would like to start a VOTE on "Support split
> bundle
> > > by flow or qps."(PIP-169)
> > > Here is the design detail:
> https://github.com/apache/pulsar/issues/16782
> > >
> > >
> > > and the discussion thread:
> > > https://lists.apache.org/thread/cshyt10fwcjjxs93g8yf0svgwcgnshmg
> > >
> > >
> > > Thanks,
> > > lordcheng10
>

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

Hi  Anon
   After we cut the branch, the code freezed.


Regards
Jiwei Guo (Tboy)


On Thu, Aug 25, 2022 at 9:45 PM Anon Hxy  wrote:

> Hi jiwei
>
> Sorry for late reply.  I'd like to add PIP189 to 2.11.0, is it possible now
>
> - PIP 189: No batching if only one message in batch.
> https://github.com/apache/pulsar/pull/16605
>
> Thanks,
> Xiaoyu Hou
>
> guo jiwei  于2022年8月24日周三 10:16写道：
>
> > Hi all,
> >We have merged all the blocker patches, and I decide to start the
> > release.
> >The release note[1] for 2.11.0 is available for review, please help
> > review it and feel free to leave comments.
> >
> >
> > [1] https://github.com/apache/pulsar-site/pull/167
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Wed, Aug 17, 2022 at 10:43 PM Enrico Olivelli 
> > wrote:
> >
> > > This test is blocking all the PRs and so it is blocking the release:
> > > Error: Tests run: 9, Failures: 2, Errors: 0, Skipped: 3, Time elapsed:
> > > 21.724 s <<< FAILURE! - in
> > > org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest
> > > 3681 Error:
> > >
> >
> testParallelSubscribeAsync(org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest)
> > > Time elapsed: 5.05 s <<< FAILURE!
> > > org.testng.internal.thread.ThreadTimeoutException: Method
> > >
> > >
> >
> org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest.testParallelSubscribeAsync()
> > > didn't finish within the time-out 5000
> > >
> > >
> > > Enrico
> > >
> > > Il giorno mer 17 ago 2022 alle ore 14:40 Nicolò Boschi
> > >  ha scritto:
> > > >
> > > > 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 blocker PR that is waiting for CI
> > > > > https://github.com/apache/pulsar/pull/17118
> > > > > the problem is about a new API that has been introduced in 2.11 but
> > > > > the API has a little problem and we must fix it before the API to
> be
> > > > > released to the public
> > > > >
> > > > > Enrico
> > > > >
> > > > > Il giorno mar 16 ago 2022 alle ore 10:13 guo jiwei
> > > > >  ha scritto:
> > > > > >
> > > > > > Thanks for Yunze's help for fixing rpm and deb packaging.
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > > Jiwei Guo (Tboy)
> > > > > >
> > > > > >
> > > > > > On Wed, Aug 10, 2022 at 11:02 PM Yunze Xu
> > > 
> > > > > > wrote:
> > > > > >
> > > > > > > I found the scripts to build rpm and deb packages are broken,
> see
> > > > > > >
> > > > > > >
> > > > >
> > >
> >
> https://github.com/apache/pulsar/wiki/Release-process#31-build-rpm-and-deb-packages
> > > > > > > .
> > > > > > >
> > > > > > > It's caused by https://github.com/apache/pulsar/pull/15376 and
> > > only
> > > > > > > affects the 2.11.0 release and higher versions. It should be a
> > > blocker
> > > > > > > for 2.11.0 release. I'm working on this issue at the moment and
> > > going
> > > > > > > to push a fix soon, as well as the CI to protect the rpm/deb
> > > packaging
> > > > > > > to avoid the regression.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Yunze
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > 2022年8月4日 23:44，guo jiwei  写道：
> > > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Put an update here, we have created branch-2.11[1].
> > > > > > > >
> > > > > > > >

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

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Wed, Aug 31, 2022 at 10:22 AM Zixuan Liu  wrote:

> +1
>
> Best regards,
> Zixuan
>
> Joe F  于2022年8月31日周三 08:53写道：
>
> > +1
> >
> > On Tue, Aug 30, 2022 at 9:37 AM Matteo Merli 
> > wrote:
> >
> > > +1
> > >
> > >
> > > --
> > > Matteo Merli
> > > 
> > >
> > > On Mon, Aug 29, 2022 at 5:56 AM Lari Hotari 
> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I have drafted PIP-204: Reactive Java client for Apache Pulsar.
> > > >
> > > > PIP link:
> > > > https://github.com/apache/pulsar/issues/17335
> > > >
> > > > Here's a copy of the contents of the GH issue for your references:
> > > >
> > > > Motivation
> > > >
> > > > There's a need to "go reactive from end-to-end" when building modern
> > > > reactive applications with platforms such as Spring Reactive.
> > > > There are ways to adapt the Apache Pulsar Java client async API calls
> > to
> > > > Reactive Streams with a few lines of code.
> > > > However, a lot will be missing and achieving the complete solution
> will
> > > > require much more effort.
> > > >
> > > > A better solution would be to have first-class support Reactive
> Streams
> > > in
> > > > Apache Pulsar.
> > > >
> > > > Reactive Streams  is an
> > > interoperability
> > > > specification and there are multiple implementations for the JVM.
> > > > It's not about a single programming language.
> > > > For example, a Reactive client for Apache Pulsar supporting Reactive
> > > > Streams can be used together with Project Reactor / Spring Reactive,
> > Akka
> > > > Streams, RxJava 3, Vert.x, SmallRye Mutiny (RedHat/Quarkus) and
> others.
> > > > Goal
> > > >
> > > > Provide Reactive Java client for Apache Pulsar
> > > >
> > > > The Reactive Java client for Apache Pulsar exposes a Reactive Streams
> > > > compatible Reactive client API for Apache Pulsar.
> > > > Reactive programming is about non-blocking applications that are
> > > > asynchronous and event-driven and require a small number of threads
> to
> > > > scale. The Reactive Java client for Apache Pulsar supports
> non-blocking
> > > > reactive asynchronous back pressure for producing and consuming
> > messages
> > > so
> > > > that the producing or consuming pipeline doesn't get overwhelmed by
> > > > producing or consuming.
> > > > Libraries that support Reactive Streams provide a programming model
> > that
> > > is
> > > > efficient and optimal for message producing and consuming
> (processing)
> > > use
> > > > cases.
> > > > API Changes
> > > >
> > > > Establish a Reactive Streams compatible client API for Apache Pulsar.
> > > > This client will be published in Maven central as a library.
> > > > Implementation
> > > >
> > > > There's an existing proof-of-concept available at
> > > > https://github.com/datastax/pulsar .
> > > > This implementation will be used as a reference for an entirely new
> > > > implementation that is started as a new repository under the Apache
> > > Pulsar
> > > > project.
> > > >
> > > > The proposal for the repository location is
> > > > https://github.com/apache/pulsar-client-reactive .
> > > > The Maven central group Id is "org.apache.pulsar" and the main
> artifact
> > > id
> > > > is "pulsar-client-reactive".
> > > > The root package name is "org.apache.pulsar.reactive.client".
> > > >
> > > > The implementation will provide an interface module that abstracts
> the
> > > > Reactive client API.
> > > > This interface is implemented by wrapping the current Apache Pulsar
> > Java
> > > > client and adapts the existing async Java API to the the Reactive
> > client
> > > > API.
> > > > The reason for this particular detail is that it is possible to
> > provide a
> > > > native Reactive client later while having the possibility to start
> > > > developing applications immediately using the Reactive client API.
> > > > Applications depending on the API will be able to migrate to use the
> > > native
> > > > Reactive client with minor or no changes when it becomes available.
> > > > Anything else?
> > > >
> > > > By having an official Reactive Java client for Apache Pulsar, it will
> > > > provide a way to contribute and improve the official client.
> > > > Other opensource projects might want to provide support for using
> > Apache
> > > > Pulsar within reactive application frameworks. Without an official
> > > reactive
> > > > client, this becomes hard, since open source projects would like to
> use
> > > > stable client dependencies instead of a hobby project provided by an
> > > > individual.
> > > > There are several members within the existing Apache Pulsar
> > contributors
> > > > and committers that have expressed the desire to contribute to a
> > Reactive
> > > > client for Apache Pulsar and are willing to maintain the new
> > repository.
> > > > With the new repository and sub-project we will most likely see new
> > > active
> > > > contributors and could possibly appoint new Apache Pulsar committers
> to
> > > the
> > > > project 

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

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Sep 1, 2022 at 1:36 AM Lari Hotari  wrote:

> +1 (binding)
>
> -Lari
>
> On 2022/08/29 13:25:51 tison wrote:
> > 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: https://github.com/apache/pulsar/issues/17137
> > Here is the discussion thread:
> > https://lists.apache.org/thread/s985ypf0r0hzcm0mx653n5h2rt7n273v
> > Here is the link to the draft PR:
> > https://github.com/apache/pulsar/pull/17062
> >
> > Voting will stay open for at least 72h.
> >
> > Best,
> > tison.
> >
>

Re: [VOTE] PIP-195: New bucket based delayed message tracker

[guo jiwei]

+1 Great work!


Regards
Jiwei Guo (Tboy)


On Wed, Aug 31, 2022 at 6:19 PM Ran Gao  wrote:

> +1 Great work!
>
> Thanks,
> Ran Gao
>
> On 2022/08/29 10:37:31 Cong Zhao wrote:
> > Hi Pulsar Community,
> >
> > In order to facilitate community review, I copied this proposal to
> Google Docs, please review it and complete the vote.
> >
> > PIP:
> https://docs.google.com/document/d/17HE88w4WuEsLoz0DExPpRN555UC_Tc3MEIKckVWksDc/edit
> >
> > On 2022/08/08 06:51:31 Cong Zhao wrote:
> > >  Hi Pulsar Community,
> > >
> > > I would like to start a VOTE on "New bucket based delayed message
> tracker"
> > > (PIP-195).
> > >
> > > The proposal can be read at
> https://github.com/apache/pulsar/issues/16763
> > > and the discussion thread is available at
> > > https://lists.apache.org/thread/1krdhrvs803kb6rqzdh17q0f199nroz4
> > >
> > > Voting will stay open for at least 48h.
> > >
> > > Thanks,
> > > Cong Zhao
> > >
> >
>

Re: [VOTE] [PIP-204] Extensions for BrokerInterceptor

[guo jiwei]

+1 (binding)

Regards
Jiwei Guo (Tboy)


On Wed, Aug 31, 2022 at 10:11 AM Haiting Jiang 
wrote:

> +1
>
> Thanks,
> Haiting
>
> On Tue, Aug 30, 2022 at 8:26 PM Enrico Olivelli 
> wrote:
>
> > +1 (binding)
> >
> >
> > Enrico
> >
> > Il giorno mar 30 ago 2022 alle ore 13:24 lin chen
> >  ha scritto:
> > >
> > > +1
> > >
> > > Aloys Zhang  于2022年8月30日周二 19:02写道：
> > >
> > > > Hi devs,
> > > >
> > > > This is the VOTE thread for PIP-204  Extensions for
> BrokerInterceptor.
> > > >
> > > > PIP issue: https://github.com/apache/pulsar/issues/17267
> > > >
> > > > Discussion thread:
> > > > https://lists.apache.org/thread/3zgpbxffo7gzsb5mdh0sk2rq27bgw2bo
> > > >
> > > > This voting will open for at least 72h.
> > > >
> > > >
> > > >
> > > > Best,
> > > > Aloys
> > > >
> >
>

Re: [VOTE] Pulsar Release 2.7.5 Candidate 3

[guo jiwei]

+1 (binding)

- Verified checksum and signatures
- Apache Rat check passes
- Compiled from source
- Run Pulsar standalone
- Validate Pub/Sub and Java Functions
- Validate Stateful Functions

Regards
Jiwei Guo (Tboy)


On Thu, Sep 1, 2022 at 11:36 AM Michael Marshall 
wrote:

> +1 (binding)
>
> - Verified checksums and signatures on 45 artifacts
> - Compiled from source (apache-pulsar-2.7.5-src.tar.gz)
> using `mvn clean install -DskipTest` using JDK 8
> - Ran `mvn apache-rat:check` successfully
> - Verified binary licenses
> - Verified that the lib directory jars from the binary tarball match
> my local build of the git tag (the only differences came from the
> pulsar jars, which is expected)
> - Ran pulsar standalone with the performance producer and consumer using
> JDK 8
>
> Thank you for managing the release, Haiting!
>
> Thanks,
> Michael
>
>
> On Wed, Aug 31, 2022 at 2:15 AM Haiting Jiang 
> wrote:
> >
> > >
> > > This is an interesting result. It would be great if the download page
> > > after this release is made would indicate JDK versions.
> >
> >
> > Yes, this info seems missing.
> > I opened a PR[1] to add this info. Please take a look.
> >
> > [1] https://github.com/apache/pulsar/pull/17368
> >
> > Thanks,
> > Haiting
> >
> > On Wed, Aug 31, 2022 at 2:31 PM Dave Fisher 
> wrote:
> >
> > > This is an interesting result. It would be great if the download page
> > > after this release is made would indicate JDK versions.
> > >
> > > Thanks!
> > > Dave
> > >
> > > Sent from my iPhone
> > >
> > > > On Aug 30, 2022, at 10:46 PM, Michael Marshall  >
> > > wrote:
> > > >
> > > > Thank you both for verifying it on your end. After debugging this
> for
> > > > a way too long tonight, I discovered my mistake was using Java 11
> > > > instead of Java 8. It didn't occur to me that the different versions
> > > > could/would result in a different set of dependencies.
> > > >
> > > > When I use Java 8, this command passes now: src/check-binary-license
> > > > distribution/server/target/apache-pulsar-2.7.5-bin.tar.gz. I plan to
> > > > finish my release validation tomorrow.
> > > >
> > > > Thanks!
> > > > Michael
> > > >
> > > >
> > > >
> > > >> On Tue, Aug 30, 2022 at 4:21 AM Anon Hxy 
> wrote:
> > > >>
> > > >> Hi Michael,
> > > >>
> > > >> I also couldn't reproduce it  with the same steps Haiting provided.
> > > >>
> > > >> Here is my local environment info with `mvn -v`
> > > >>
> > > >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> > > >> Maven home: /Users/didi/Documents/apache-maven-3.6.3
> > > >> Java version: 1.8.0_291, vendor: Oracle Corporation, runtime:
> > > >> /Library/Java/JavaVirtualMachines/jdk1.8.0_291.jdk/Contents/Home/jre
> > > >> Default locale: zh_CN, platform encoding: UTF-8
> > > >> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> > > >>
> > > >> Thanks,
> > > >> Xiaoyu Hou
> > > >>
> > > >>
> > > >> Haiting Jiang  于2022年8月30日周二 15:23写道：
> > > >>
> > > >>> Hi Michael,
> > > >>> Thanks for your verification.
> > > >>>
> > > >>> I tried to recreate the issue, but I can't reproduce this.
> > > >>> Here is my steps:
> > > >>> - wget
> > > >>>
> > > >>>
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.5-candidate-3/apache-pulsar-2.7.5-src.tar.gz
> > > >>> - tar -xvf apache-pulsar-2.7.5-src.tar.gz
> > > >>> - cd apache-pulsar-2.7.5
> > > >>> - mvn clean install -DskipTests
> > > >>> - src/check-binary-license
> > > >>> distribution/server/target/apache-pulsar-2.7.5-bin.tar.gz
> > > >>>
> > > >>> And nothing appears in `check-binary-license` output.
> > > >>>
> > > >>> Here is my local environment info with `mvn -v`
> > > >>>
> > > >>> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> > > >>> 2019-04-05T03:00:29+08:00)
> > > >>> Maven home: /Users/jason/apache-maven-3.6.1
> > > >>> Java version: 1.8.0_291, vendor: Oracle Corporation, runtime:
> > > >>>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_291.jdk/Contents/Home/jre
> > > >>> Default locale: en_CN, platform encoding: UTF-8
> > > >>> OS name: "mac os x", version: "10.15.7", arch: "x86_64", family:
> "mac"
> > > >>>
> > > >>> Please check the settings again and I also will ask others to help
> > > verify
> > > >>> the issue you mention.
> > > >>>
> > > >>> Thanks,
> > > >>> Haiting
> > > >>>
> > > >>>
> > > >>> On Tue, Aug 30, 2022 at 12:37 PM Michael Marshall <
> > > mmarsh...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  When I build from the source (both for the git tag
> > >  `v2.7.5-candidate-3` and the extracted src tarball
> > >  `apache-pulsar-2.7.5-src.tar.gz`), I am getting an error when I
> run
> > >  the license check:
> > > 
> > >  ```
> > >  $ src/check-binary-license
> > >  distribution/server/target/apache-pulsar-2.7.5-bin.tar.gz
> > >  com.sun.activation-jakarta.activation-1.2.2.jar unaccounted for in
> > > >>> LICENSE
> > >  jakarta.activation-jakarta.activation-api-1.2.2.jar unaccounted
> for in
> > >  LICENS

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

Hi  dev,
We find two new issues[1] that block the release.
After the two issues are resolved, I will start the release.

[1] : https://github.com/apache/pulsar/pull/17474
   https://github.com/apache/bookkeeper/issues/3466

Regards
Jiwei Guo (Tboy)


On Fri, Aug 26, 2022 at 10:02 AM guo jiwei  wrote:

> Hi  Anon
>After we cut the branch, the code freezed.
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Thu, Aug 25, 2022 at 9:45 PM Anon Hxy  wrote:
>
>> Hi jiwei
>>
>> Sorry for late reply.  I'd like to add PIP189 to 2.11.0, is it possible
>> now
>>
>> - PIP 189: No batching if only one message in batch.
>> https://github.com/apache/pulsar/pull/16605
>>
>> Thanks,
>> Xiaoyu Hou
>>
>> guo jiwei  于2022年8月24日周三 10:16写道：
>>
>> > Hi all,
>> >We have merged all the blocker patches, and I decide to start the
>> > release.
>> >The release note[1] for 2.11.0 is available for review, please help
>> > review it and feel free to leave comments.
>> >
>> >
>> > [1] https://github.com/apache/pulsar-site/pull/167
>> >
>> >
>> > Regards
>> > Jiwei Guo (Tboy)
>> >
>> >
>> > On Wed, Aug 17, 2022 at 10:43 PM Enrico Olivelli 
>> > wrote:
>> >
>> > > This test is blocking all the PRs and so it is blocking the release:
>> > > Error: Tests run: 9, Failures: 2, Errors: 0, Skipped: 3, Time elapsed:
>> > > 21.724 s <<< FAILURE! - in
>> > > org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest
>> > > 3681 Error:
>> > >
>> >
>> testParallelSubscribeAsync(org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest)
>> > > Time elapsed: 5.05 s <<< FAILURE!
>> > > org.testng.internal.thread.ThreadTimeoutException: Method
>> > >
>> > >
>> >
>> org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest.testParallelSubscribeAsync()
>> > > didn't finish within the time-out 5000
>> > >
>> > >
>> > > Enrico
>> > >
>> > > Il giorno mer 17 ago 2022 alle ore 14:40 Nicolò Boschi
>> > >  ha scritto:
>> > > >
>> > > > 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 blocker PR that is waiting for CI
>> > > > > https://github.com/apache/pulsar/pull/17118
>> > > > > the problem is about a new API that has been introduced in 2.11
>> but
>> > > > > the API has a little problem and we must fix it before the API to
>> be
>> > > > > released to the public
>> > > > >
>> > > > > Enrico
>> > > > >
>> > > > > Il giorno mar 16 ago 2022 alle ore 10:13 guo jiwei
>> > > > >  ha scritto:
>> > > > > >
>> > > > > > Thanks for Yunze's help for fixing rpm and deb packaging.
>> > > > > >
>> > > > > >
>> > > > > > Regards
>> > > > > > Jiwei Guo (Tboy)
>> > > > > >
>> > > > > >
>> > > > > > On Wed, Aug 10, 2022 at 11:02 PM Yunze Xu
>> > > 
>> > > > > > wrote:
>> > > > > >
>> > > > > > > I found the scripts to build rpm and deb packages are broken,
>> see
>> > > > > > >
>> > > > > > >
>> > > > >
>> > >
>> >
>> https://github.com/apache/pulsar/wiki/Release-process#31-build-rpm-and-deb-packages
>> > > > > > > .
>> > > > > > >
>> > > > > > > It's caused by https://github.com/apache/pulsar/pull/15376
>> and
>> > > only
>> > > > > > > affects the 2.11.0 release and higher versions. It should be a
>> > > blocker
>> > > > > > > for 2.11.0 release. I'm working on this issue at the moment
>> and
>> > > going
>> 

Re: [ANNOUNCE] New PMC member: Lin Lin (@315157973)

[guo jiwei]

Congrats to Lin lin.

Regards
Jiwei Guo (Tboy)


On Tue, Aug 3, 2021 at 1:08 PM Huanli Meng 
wrote:

> Congrats Lin Lin!
>
> BR// Huanli Meng
>
> > On Aug 3, 2021, at 12:00 PM, Hang Chen  wrote:
> >
> > Congrats Lin Lin!
>
>

Re: [ANNOUNCE] New PMC member: Enrico Olivelli (eolivelli)

[guo jiwei]

Congrats to Enrico.

Regards
Jiwei Guo (Tboy)


On Tue, Aug 3, 2021 at 12:33 PM Anonymitaet _ 
wrote:

> Congrats Enrico! Great job on all your hard work!
>
> On 2021/8/3, 12:02, "Hang Chen"  wrote:
>
> Congrats Enrico!
>
> Regards,
> Hang
>
> Aloys Zhang  于2021年8月3日周二 上午10:39写道：
>
> > Congrats Enrico!
> >
> > r...@apache.org  于2021年8月3日周二 上午10:27写道：
> >
> > > Congratulations to Enrico~
> > >
> > > --
> > >
> > > Thanks
> > > Xiaolong Ran
> > >
> > > Jinfeng Huang  于2021年8月3日周二 上午8:48写道：
> > >
> > > > Congrats Enrico and thanks for all your awesome work on the
> project!!
> > > >
> > > > Best Regards,
> > > > Jennifer
> > > >
> > > >
> > > > On Tue, Aug 3, 2021 at 8:30 AM Rui Fu  wrote:
> > > >
> > > > > Congrats Enrico!
> > > > >
> > > > > Best,
> > > > >
> > > > > Rui
> > > > > 在 2021年8月2日 +0800 PM10:19，Nozomi Kurihara  >，写道：
> > > > > > Hi everyone,
> > > > > >
> > > > > > The Apache Pulsar Project Management Committee (PMC) has
> invited
> > > Enrico
> > > > > > Olivelli (https://github.com/eolivelli) as a member of the
> PMC and
> > > we
> > > > > are
> > > > > > pleased to announce that he has accepted.
> > > > > >
> > > > > > Enrico has actively contributed to Apache Pulsar so far, e.g.
> > > > > > Pull-Requests, code reviews and presentations at Pulsar
> Summit. We
> > > > > believe
> > > > > > that his future contribution as a member of the PMC will
> lead our
> > > > > community
> > > > > > forward.
> > > > > >
> > > > > > Welcome and Congratulations, Enrico!
> > > > > >
> > > > > > Best Regards,
> > > > > > Nozomi on behalf of the Pulsar PMC
> > > > >
> > > >
> > >
> >
> >
> > --
> > Best,
> > Aloys.
> >
>
>
>

Re: [ANNOUNCE] New Committer: Jiwei Guo

[guo jiwei]

Thanks to the community and to all the people who have helped me. I will
continue to work hard.


Regards
Jiwei Guo (Tboy)


On Mon, Nov 22, 2021 at 2:07 PM Enrico Olivelli  wrote:

> Congrats!
>
> Enrico
>
> Il Lun 22 Nov 2021, 05:35 PengHui Li  ha scritto:
>
> > The Apache Pulsar Project Management Committee (PMC) has invited Jiwei
> Guo
> > https://github.com/Technoboy- to become a committer and we are pleased
> to
> > announce
> > that he has accepted.
> >
> > Jiwei has joined the community for more than 1 year now and he is active
> > in the Pulsar community for more than 5 months, and he is a PMC member of
> > Apache dolphinscheduler
> > https://dolphinscheduler.apache.org/en-us/community/team.html
> >
> > Welcome and Congratulations, Jiwei!
> >
> > Please join us in congratulating and welcoming Jiwei onboard!
> >
> > Best Regards,
> > Penghui Li on behalf of the Pulsar PMC
> >
>

[VOTE] PIP-277: Add `current` option in the Clusters list cmd

[guo jiwei]

Hi dev,
   This thread is to start a vote for PIP-277:  Add `current` option in the
Clusters list cmd

Discuss thread :
https://lists.apache.org/thread/800r6ld5wg7bttbywmk38m1qx12hs6nl
PIP: https://github.com/apache/pulsar/pull/20614



Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-277: Add `current` option in the Clusters list cmd

[guo jiwei]

Thanks.
Close the vote with 3+ (binding):
Penghui
Mattison
tison

2+(non-binding):
Zike
Zixuan

Regards
Jiwei Guo (Tboy)


On Thu, Sep 7, 2023 at 12:48 AM Zixuan Liu  wrote:

> +1 (non-binding)
>
> Best,
> Zixuan
>
> Zike Yang  于2023年9月6日周三 23:56写道：
> >
> > +1 (non-binding)
> >
> > BR,
> > Zike Yang
> >
> > On Wed, Sep 6, 2023 at 11:47 PM tison  wrote:
> > >
> > > +1 (binding)
> > >
> > > Trivial with low risk.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > mattison chao  于2023年9月6日周三 22:50写道：
> > >
> > > > +1 (binding)
> > > >
> > > > Best,
> > > > Mattison
> > > > On 6 Sep 2023 at 22:37 +0800, PengHui Li ,
> wrote:
> > > > > +1 (binding)
> > > > >
> > > > > The proposal just added a new option to show which cluster is the
> current
> > > > > cluster accessed. It will not break any existing behavior.
> > > > >
> > > > > Regards,
> > > > > Penghui
> > > > >
> > > > > On Wed, Sep 6, 2023 at 4:21 PM guo jiwei 
> wrote:
> > > > >
> > > > > > Hi dev,
> > > > > > This thread is to start a vote for PIP-277: Add `current` option
> in the
> > > > > > Clusters list cmd
> > > > > >
> > > > > > Discuss thread :
> > > > > > https://lists.apache.org/thread/800r6ld5wg7bttbywmk38m1qx12hs6nl
> > > > > > PIP: https://github.com/apache/pulsar/pull/20614
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > > Jiwei Guo (Tboy)
> > > > > >
> > > >
>

Re: [VOTE] PIP-286: Make the TopicCompactionService to support find entry based on publishTime or index

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Sep 18, 2023 at 11:01 AM Zike Yang  wrote:

> +1 (non-binding)
>
> BR,
> Zike Yang
>
> On Mon, Sep 18, 2023 at 9:35 AM mattison chao 
> wrote:
> >
> > +1 (binding)
> >
> > Best,
> > Mattison
> > On 18 Sep 2023 at 09:19 +0800, PengHui Li , wrote:
> > > +1 (binding)
> > >
> > > Thanks,
> > > Penghui
> > >
> > > On Thu, Sep 14, 2023 at 11:23 AM Cong Zhao 
> wrote:
> > >
> > > > Hi, all
> > > >
> > > > Since there are no other concerns in the discussion, I'm delighted to
> > > > start the voting process for the PIP-286.
> > > >
> > > > Here is the link to the PIP:
> https://github.com/apache/pulsar/pull/20867
> > > >
> > > > Thanks,
> > > > Cong Zhao
> > > >
>

[DISCUSS] Release Pulsar 3.1.1

[guo jiwei]

Hi all,

I would like to propose releasing the Pulsar 3.1.1.

It's over one month since the release of 3.1.0 and there are 56 new commits
in branch-3.1:
https://github.com/apache/pulsar/compare/v3.1.0...branch-3.1

We need to cut a new release. Please let me know if you have any
important fixes that need to be included in Pulsar 3.1.1.


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-301: Introduce LoadBalanceResources to unify the load-date CRUD

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Sep 18, 2023 at 8:57 PM houxiaoyu  wrote:

> Hi dev,
>This thread is to start a vote for PIP-301: Introduce
> LoadBalanceResources to unify the load-date CRUD
>
>Discuss thread :
> https://lists.apache.org/thread/7ngw9dc62tj2c4c5484dgsnlwgtstpbj
>PIP: https://github.com/apache/pulsar/pull/21129
>
>
>
> Regards
> houxiaoyu
>

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

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, Sep 20, 2023 at 8:53 AM mattison chao 
wrote:

> +1 (binding)
>
> Best,
> Mattison
> On 20 Sep 2023 at 08:40 +0800, PengHui Li , wrote:
> > There are a lot of discussions that happened in the DISCUSS thread.
> > The proposal looks good to me.
> >
> > +1 (binding)
> >
> > Regards,
> > Penghui
> >
> > On Wed, Sep 6, 2023 at 1:51 PM Heesung Sohn
> >  wrote:
> >
> > > Yes, this was my last comment in the PIP.
> > > https://github.com/apache/pulsar/pull/20748#discussion_r1300733232
> > > I saw your comment,
> > > https://github.com/apache/pulsar/pull/20748#discussion_r1303801386.
> > >
> > > I am sorry. I probably didn't make it clear.
> > > I thought you would leave more comments to conclude the discussion,
> > > or we would discuss more during the community meeting.
> > >
> > >
> > >
> > > On Tue, Sep 5, 2023 at 6:19 PM Michael Marshall 
> > > wrote:
> > >
> > > > > > > In my last comment, I proposed a follow-up PIP if we want to
> add the
> > > > > > > "prepare" command(Michael’s idea) on top of this PIP.
> > > > > > > I have been waiting to hear from him since then.
> > > > >
> > > > > Out of curiosity, where was your proposal? If it was on the PIP
> PR, I
> > > > > already replied here:
> > > > > https://github.com/apache/pulsar/pull/20748#discussion_r1303801386
> > > > >
> > > > > On Tue, Sep 5, 2023 at 8:09 PM Matteo Merli <
> matteo.me...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > +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
> > > > > > > > >
> > > > >
> > >
>

[VOTE] Pulsar Release 3.1.1 Candidate 1

[guo jiwei]

This is the first release candidate for Apache Pulsar version 3.1.1.

It fixes the following issues:
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.1+label%3Acherry-picked%2Fbranch-3.1+

*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***

Note that we are voting upon the source (tag), binaries are provided
for convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.1-candidate-1/

SHA-512 checksums:

af79f970c8835320584faf58c85bfc5cd12261f5e366c2c16bce2f7628d769ef7374a3c0e383ff443519e484a35a23e86415e0156a0f35dd3bc1f606d2fa0421

apache-pulsar-3.1.1-bin.tar.gz

a43306b8a08a330c721ca96501c0c4285e5c47cfab4a037034148401afc4dbd65e505da591ef9ca76ca5acf39d6fd9c96537a08956ad6fb37f7c70d8ab747510

apache-pulsar-3.1.1-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1243/

The tag to verify:
v3.1.1-candidate-1 (80fb39085b4e49ff31f2df17b10addcca5abdccb)
https://github.com/apache/pulsar/releases/tag/v3.1.1-candidate-1

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/mattison/pulsar-all/3.1.1-80fb390/images/sha256-1088b07fd2448733db1d165676b82c1278f2940cb0861c704450ef2be5c2fa1c?context=explore

pulsar-all images:
https://hub.docker.com/layers/mattison/pulsar/3.1.1-80fb390/images/sha256-21e8bf1571e4ab559a51b3f6e524d725cffabe3c6836101f9d7ea7eb1e2bf62c?context=explore

Please download the source package, and follow the README to build
and run the Pulsar standalone service.



Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Sat, Oct 7, 2023 at 8:07 PM PengHui Li  wrote:

> +1
>
> Thanks,
> Penghui
>
> On Wed, Sep 27, 2023 at 3:09 PM Zike Yang  wrote:
>
> > +1
> >
> > BR,
> > Zike Yang
> >
> > On Wed, Sep 27, 2023 at 3:05 PM Xiangying Meng 
> > wrote:
> > >
> > > Hi dev,
> > >This thread is to start a vote for PIP-302 Add new API
> > > refreshAsync for TableView.
> > > Discuss thread:
> > https://lists.apache.org/thread/o085y2314o0fymvx0x8pojmgjwcwn59q
> > > PIP: https://github.com/apache/pulsar/pull/21166
> > >
> > > BR,
> > > Xiangying
> >
>

Re: [VOTE] PIP-299: Stop dispatch messages if the individual acks will be lost in the persistent storage

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Oct 9, 2023 at 8:14 AM PengHui Li  wrote:

> +1 (binding)
>
> Left to minor comments on the proposal, PTAL.
>
> Thanks,
> Penghui
>
> On Thu, Sep 21, 2023 at 2:53 PM Yubiao Feng
>  wrote:
>
> > Sorry.  The last email was sent by mistake. Just correct it by this one.
> >
> > I'd like to start a vote thread for the PIP-299.
> > https://github.com/apache/pulsar/pull/21118
> >
> > Discussion :
> > https://lists.apache.org/thread/2fzo1gnlyd1t5o80g1polbvbx4699r09
> >
> > Thanks
> > Yubiao Feng
> >
> > On Thu, Sep 21, 2023 at 2:49 PM Yubiao Feng  >
> > wrote:
> >
> > > Hi all
> > >
> > > I'd like to start a vote thread for the PIP-299.
> > >
> >
>

[DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Hi dev,
   Currently WebSocket only supports the consumption of a single topic,
which cannot satisfy users' consumption scenarios of multiple topics.  So
in order to support consumption of multiple topics or pattern topics, I
start discussing PIP-307 .


Ref:
• PIP-307: https://github.com/apache/pulsar/pull/21390


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Oct 19, 2023 at 10:11 AM Zili Chen  wrote:

> +1 binding
>
> On 2023/10/17 07:23:29 Diego Salvi wrote:
> > Hi Community,
> >
> > This thread is to start a vote for PIP-305.
> >
> > PIP: https://github.com/apache/pulsar/pull/21352
> > Discussion thread:
> > https://lists.apache.org/thread/p0870y7o6brv5y1ghn5tz9hvs24bl1k4
> >
> > Best regards
> > Diego Salvi
> >
>

Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Thanks, I will send out the vote mail.


Regards
Jiwei Guo (Tboy)


On Thu, Oct 19, 2023 at 11:50 AM Zixuan Liu  wrote:

> +1
>
> Thanks,
> Zixuan
>
> guo jiwei  于2023年10月18日周三 20:45写道：
> >
> > Hi dev,
> >Currently WebSocket only supports the consumption of a single topic,
> > which cannot satisfy users' consumption scenarios of multiple topics.  So
> > in order to support consumption of multiple topics or pattern topics, I
> > start discussing PIP-307 <https://github.com/apache/pulsar/pull/21390>.
> >
> >
> > Ref:
> > • PIP-307: https://github.com/apache/pulsar/pull/21390
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
>

[VOTE] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Hi dev,
   Currently WebSocket only supports the consumption of a single topic,
which cannot satisfy users' consumption scenarios of multiple topics.  So
in order to support consumption of multiple topics or pattern topics, I
would like to start a vote for PIP-307
.


Ref:
• Discuss Mail:
https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
• PIP-307: https://github.com/apache/pulsar/pull/21390


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-298 Consumer supports specifying consumption isolation level

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Oct 23, 2023 at 1:40 PM Yunze Xu  wrote:

> +1 (binding)
>
> Thanks,
> Yunze
>
> On Mon, Oct 23, 2023 at 1:08 PM PengHui Li  wrote:
> >
> > +1 (binding)
> >
> > Regards,
> > Penghui
> >
> > On Mon, Oct 23, 2023 at 10:37 AM hzh0425  wrote:
> >
> > > Dave previously mentioned in the discussion thread that he will
> continue
> > > to support this pip if the documentation is supplemented and improved.
> Due
> > > to inability to contact him, we apply to cancel his -1 binding.
> > >
> > >
> > >
> > >  Replied Message 
> > > | From | Dave Fisher |
> > > | Date | 09/26/2023 04:03 |
> > > | To | dev@pulsar.apache.org |
> > > | Cc | |
> > > | Subject | Re: [VOTE] PIP-298 Consumer supports specifying consumption
> > > isolation level |
> > > -1 (binding) I’m not convinced that breaking transaction isolation is
> the
> > > proper course of action.
> > >
> > > Regards,
> > > Dave
> > >
> > > > On Sep 25, 2023, at 6:46 AM, hzh0425  wrote:
> > > >
> > > > Hi dev,
> > > > This thread is to start a vote for PIP-298 Consumer supports
> specifying
> > > consumption isolation level
> > > > Discuss thread:
> > > > https://lists.apache.org/thread/8ny0qtp7m9qcdbvnfjdvpnkc4c5ssyld
> > > >
> > > > https://lists.apache.org/thread/2opqjof83425vry6gzszd5glqgryrv11
> > > >
> > > > PIP: https://github.com/apache/pulsar/pull/21114
> > > >
> > > > BR,
> > > > hzh
> > >
>

Re: [VOTE] Pulsar Release 3.1.1 Candidate 1

[guo jiwei]

Close this vote by 3 binding +1:

- Penghui
- Mattison
- Yunze


Regards
Jiwei Guo (Tboy)


On Tue, Oct 24, 2023 at 6:27 PM PengHui Li  wrote:

> +1 (binding)
>
> - Checked the signatures
> - Built from source tarball
> - Run standalone and check the produce, consume
> - Verified Cassandra connector
> - Verified stateful function
>
> Regards,
> Penghui
>
> On Tue, Oct 24, 2023 at 12:34 PM Yunze Xu  wrote:
>
> > +1 (binding)
> >
> > - Verified checksum and signatures
> > - Built from source with Java 17.0.7 and Maven 3.9.3 on macOS m1
> > - Started standalone and verified produce and consume
> > - Ran it with StreamNative KoP and verified produce and consume with
> > Kafka clients 3.5.0
> >
> > Thanks,
> > Yunze
> >
> > On Thu, Oct 19, 2023 at 5:53 PM mattison chao 
> > wrote:
> > >
> > > +1 (binding)
> > >
> > >
> > > - Built from source code. (Java version: 17.0.8.1, Apache Maven 3.9.4,
> > OS name: "mac os x", version: "13.4.1", arch: "x86_64")
> > > - Checked binary license
> > > - Started Standalone
> > > - Ran a round of publish and consume
> > >
> > > Best,
> > > Mattison
> > >
> > > > On 7 Oct 2023, at 09:09, guo jiwei  wrote:
> > > >
> > > > This is the first release candidate for Apache Pulsar version 3.1.1.
> > > >
> > > > It fixes the following issues:
> > > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.1+label%3Acherry-picked%2Fbranch-3.1+
> > > >
> > > > *** Please download, test and vote on this release. This vote will
> > > > stay open for at least 72 hours ***
> > > >
> > > > Note that we are voting upon the source (tag), binaries are provided
> > > > for convenience.
> > > >
> > > > Source and binary files:
> > > >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.1-candidate-1/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> >
> af79f970c8835320584faf58c85bfc5cd12261f5e366c2c16bce2f7628d769ef7374a3c0e383ff443519e484a35a23e86415e0156a0f35dd3bc1f606d2fa0421
> > > >
> > > > apache-pulsar-3.1.1-bin.tar.gz
> > > >
> > > >
> >
> a43306b8a08a330c721ca96501c0c4285e5c47cfab4a037034148401afc4dbd65e505da591ef9ca76ca5acf39d6fd9c96537a08956ad6fb37f7c70d8ab747510
> > > >
> > > > apache-pulsar-3.1.1-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1243/
> > > >
> > > > The tag to verify:
> > > > v3.1.1-candidate-1 (80fb39085b4e49ff31f2df17b10addcca5abdccb)
> > > > https://github.com/apache/pulsar/releases/tag/v3.1.1-candidate-1
> > > >
> > > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > > >
> > > > Docker images:
> > > >
> > > > pulsar images:
> > > >
> >
> https://hub.docker.com/layers/mattison/pulsar-all/3.1.1-80fb390/images/sha256-1088b07fd2448733db1d165676b82c1278f2940cb0861c704450ef2be5c2fa1c?context=explore
> > > >
> > > > pulsar-all images:
> > > >
> >
> https://hub.docker.com/layers/mattison/pulsar/3.1.1-80fb390/images/sha256-21e8bf1571e4ab559a51b3f6e524d725cffabe3c6836101f9d7ea7eb1e2bf62c?context=explore
> > > >
> > > > Please download the source package, and follow the README to build
> > > > and run the Pulsar standalone service.
> > > >
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > >
> >
>

[ANNOUNCE] Apache Pulsar 3.1.1 released

[guo jiwei]

The Apache Pulsar team is proud to announce Apache Pulsar version 3.1.1.

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://pulsar.apache.org/download

Release Notes are at:
https://pulsar.apache.org/release-notes

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


Regards
Jiwei Guo (Tboy)

Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket

[guo jiwei]

Thanks @Tison

Close this vote first and then I will change the pip num.

Regards
Jiwei Guo (Tboy)


On Wed, Oct 25, 2023 at 3:02 AM tison  wrote:

> PIP number conflicts.
>
> May we keep using pip-xxx instead of pip_xxx so that Git can help detect
> number conflict..
>
> Best,
> tison.
>
>
> 太上玄元道君  于2023年10月24日周二 23:50写道：
>
> > +1(no-binding)
> >
> > Thanks,
> > Tao Jiuming
> >
> > Cong Zhao 于2023年10月24日 周二16:03写道：
> >
> > > +1(no-binding)
> > >
> > > Thanks,
> > > Cong Zhao
> > >
> > > On 2023/10/19 12:47:45 guo jiwei wrote:
> > > > Hi dev,
> > > >Currently WebSocket only supports the consumption of a single
> topic,
> > > > which cannot satisfy users' consumption scenarios of multiple topics.
> > So
> > > > in order to support consumption of multiple topics or pattern
> topics, I
> > > > would like to start a vote for PIP-307
> > > > <https://github.com/apache/pulsar/pull/21390>.
> > > >
> > > >
> > > > Ref:
> > > > • Discuss Mail:
> > > > https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
> > > > • PIP-307: https://github.com/apache/pulsar/pull/21390
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > >
> >
>

Re: [VOTE] PIP-300: Add custom dynamic configuration for plugins

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Sun, Oct 8, 2023 at 2:13 PM 太上玄元道君  wrote:

> +1 (no-binding)
>
>
> Zixuan Liu 于2023年9月26日 周二10:54写道：
>
> > Hi Pulsar Community,
> >
> > Voting for PIP-300: https://github.com/apache/pulsar/pull/21127
> > Discussion thread:
> > https://lists.apache.org/thread/ysnsnollgy1b6w1dsvmx1t1y2rz1tyd6
> >
> > Thanks,
> > Zixuan
> >
>

Re: [VOTE] PIP-312 Use StateStoreProvider to manage state in Pulsar Functions endpoints

[guo jiwei]

+1 binding


Regards
Jiwei Guo (Tboy)


On Sat, Nov 18, 2023 at 12:27 AM 太上玄元道君  wrote:

> +1 non binding
>
> Zili Chen 于2023年11月17日 周五17:56写道：
>
> > +1 binding
> >
> > Thanks for your proposal.
> >
> > On 2023/11/15 03:39:42 Pengcheng Jiang wrote:
> > > Hi Pulsar Community,
> > >
> > > This thread is to start a vote for PIP-312: Use StateStoreProvider to
> > > manage state in Pulsar Functions endpoints.
> > >
> > > I start the voting process since there are some approves for the PIP
> PR.
> > >
> > > PR: https://github.com/apache/pulsar/pull/21438
> > > Discussion thread:
> > > https://lists.apache.org/thread/0rz29wotonmdck76pdscwbqo19t3rbds
> > >
> > > Sincerely,
> > > Pengcheng Jiang
> > >
> >
>

Re: [VOTE] PIP-303: Add optional parameters for getPartitionedStats

[guo jiwei]

+1 (binding)

Regards
Jiwei Guo (Tboy)


On Thu, Nov 16, 2023 at 12:46 PM Yunze Xu  wrote:

> +1 (binding)
>
> Thanks,
> Yunze
>
> On Thu, Nov 16, 2023 at 11:01 AM Jie crossover 
> wrote:
> >
> > Hi All, This thread is to start a vote for PIP-303. PIP:
> > https://github.com/apache/pulsar/pull/21228 Discussion thread:
> > https://lists.apache.org/thread/c92043zq6lyrsd5z1hnln48mx858n7vj
> > --
> > Best Regards！
> > crossoverJie
>

Re: [VOTE] Pulsar Release 2.11.3 Candidate 1

[guo jiwei]

+1 (binding)

- Checked the signatures
- Built from source
- Run standalone and check the produce, consume
- Verified Cassandra connector
- Verified stateful function

Regards
Jiwei Guo (Tboy)


On Tue, Nov 21, 2023 at 9:47 PM Baodi Shi  wrote:

>  Patch:
>
> Docker images:
> docker pull wudixiaobaozi/pulsar-all:2.11.3
> docker pull wudixiaobaozi/pulsar:2.11.3
>
> Thanks,
> Baodi Shi
>
>
> On Nov 21, 2023 at 21:23:41, Baodi Shi  wrote:
>
> > This is the first release candidate for Apache Pulsar, version 2.11.3.
> >
> > It fixes the following issues:
> >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed
> >
> > *** Please download, test and vote on this release. This vote will stay
> > open for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.11.3-candidate-1/
> >
> > SHA-512 checksums:
> >
> >
> 1104ce10ee55f99f162f71487922d9883201516754936feab07a631b25b8f76bc2443735b4bdff17d821d62ca20f605d386ce9ca2e0450ce8d2555ca07fd8dd
> ./apache-pulsar-2.11.3-bin.tar.gz
> >
> >
> bdf2579d718d25def297538def0c237974c856f63aea00db30e61b10683eec29a52a354b61daa6eda5ffe5bdfda78e6a83d473f8d7f44104fc5d715ffb1892fc
> ./apache-pulsar-2.11.3-src.tar.gz
> >
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1251
> >
> > The tag to be voted upon:
> > v2.11.3-candidate-1 (aa7082efcafb58b1fc4b7bb1bc68c6e22f7bc2d3)
> > https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-1
> >
> > Pulsar’s KEYS file containing PGP keys you use to sign the release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> >
> > Docker images:
> > docker pull wudixiaobaozi/pulsar-all:2.11.3
> > docker pull wudixiaobaozi/pulsar
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> > Thanks,
> > Baodi Shi
> >
>

Re: [VOTE] Pulsar Release 3.0.2 Candidate 4

[guo jiwei]

+1 (binding)

- Checked the signatures
- Built from source
- Run standalone and check the produce, consume
- Verified Cassandra connector
- Verified stateful function


Regards
Jiwei Guo (Tboy)


On Sun, Nov 26, 2023 at 10:10 PM Yike Xiao  wrote:

> +1 (non-binding)
>
>   *   Checked the signatures and checksums
>   *   Built from source
> ```
> Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
> Maven home: /usr/local/maven
> Java version: 17.0.5, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-17.0.5.jdk/Contents/Home
> Default locale: en_CN, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1", arch: "aarch64", family: "mac"
> ```
>   *   Run standalone and checked produce and consume
>   *   Run a cluster with three nodes with docker image (pulsar)
>
> 
> From: Yubiao Feng 
> Sent: Monday, November 20, 2023 10:24
> To: dev@pulsar.apache.org 
> Subject: [VOTE] Pulsar Release 3.0.2 Candidate 4
>
> This is the first release candidate for Apache Pulsar version 3.0.4.
>
> It fixes the following issues:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpulls%3Fq%3Dis%253Apr%2Bis%253Amerged%2Blabel%253Arelease%252F3.0.2%2Blabel%253Acherry-picked%252Fbranch-3.0&data=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699813981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=O0t7XQ%2Fyl8E1jqomYW9ObingScQ3j0ynFvpgpmAdWkk%3D&reserved=0+
> <
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.0.2+label%3Acherry-picked%2Fbranch-3.0
> >
>
> *** Please download, test and vote on this release. This vote will
> stay open for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.2-candidate-4%2F&data=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CEKQMg7XumWSg9OsK1iHTBNYDqtAFfnXOE52LfPZV8Y%3D&reserved=0
> 
>
> SHA-512 checksums:
>
>
> 9bd5b4030de47c10a906d6271731ca7bcfb8801984cdd625789bc0c5047138f0f2eb1aaceaec1c8941e2ccfa639bbb2458496518e87fb29abb9ebc518e2da60d
>
> apache-pulsar-3.0.2-bin.tar.gz
>
>
> 6854d1776de08c9079228a5a5d2f670f92b1b905f0d92c50ee35c5bc9c53be5225626a6d84fc3bbb209b8b12ff3b142685b5c9ea33609e1bb934e9679402e0b8
>
> apache-pulsar-3.0.2-src.tar.gz
>
> Maven staging repo:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1249&data=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oZ44u3rpSGhgdzvrWXlA3XTrLjjGIHiPlf2o9cFRvYE%3D&reserved=0
> 
>
> The tag to verify:
> v3.0.2-candidate-4 (12c92fed7847965e3bc3769a91c866b2f0ec2e44)
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Freleases%2Ftag%2Fv3.0.2-candidate-4&data=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KOuCBWEIvtBkourwAuQJfx7NKFLrWWZVlAVd%2FChDpgk%3D&reserved=0
> 
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS&data=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oX2GoSYu4ZSW997%2BTdJOC%2BJxyfbvMIPalRMAC09OHwU%3D&reserved=0
> 
>
> Docker images:
>
> pulsar images:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Frepository%2Fdocker%2F9947090%2Fpulsar-all&data=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XWmZ9Ytz%2BW7Wryc1M6WcLzQMSLoP3YN6ZTallD15IJs%3D&reserved=0
> 
>

Re: [DISCUSS] Release Pulsar 3.1.2

[guo jiwei]

+1


Regards
Jiwei Guo (Tboy)


On Mon, Nov 27, 2023 at 9:55 AM Yubiao Feng
 wrote:

> +1
>
> Thanks
> Yubiao Feng
>
> On Sun, Nov 26, 2023 at 4:10 PM houxiaoyu  wrote:
>
> > Hi all,
> >
> > I would like to propose releasing the Pulsar 3.1.2.
> >
> > It's over one month since the release of 3.1.1 and there are 56 new
> commits
> > in branch-3.1:
> > https://github.com/apache/pulsar/compare/v3.1.1...branch-3.1
> >
> > We need to cut a new release. Please let me know if you have any
> > important fixes that need to be included in Pulsar 3.1.2.
> >
> >
> > Regards
> > Xiaoyu Hou
> >
>

Re: [VOTE] Pulsar Release 3.1.2 Candidate 1

[guo jiwei]

Hi
 We find a regression in 3.0,  Apache/Pulsar/#17512
 has fixed the data being
deleted when offload met Metastore exception, but Apache/Pulsar/#17915
 skip the logic, causing the
broker to delete the data from the tiered storage.
 I suggest dropping this vote and fix the issue then raise a new candidate.

Regards
Jiwei Guo (Tboy)


On Sat, Dec 2, 2023 at 4:56 PM houxiaoyu  wrote:

> This is the first release candidate for Apache Pulsar version 3.1.2.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.1+
>
> *** Please download, test and vote on this release. This vote will
> stay open for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.2-candidate-1/
>
> SHA-512 checksums:
>
>
> 47e487de57c4354ed07a1690197eed9057e67ee85055d11c098ae6cff642b20e4966d43c3d52f449a942547d417dd20b94c353c7485cbd599f6f059147826f5f
> apache-pulsar-3.1.2-bin.tar.gz
>
>
> 664a5811788817c302c1e2a943f959339832ef77417e2ca566696948e330172ada878e1487402e9aff6a0a81a89b44404c797114eb2f27922f58831adfaa0582
> apache-pulsar-3.1.2-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1255/
>
> The tag to verify:
> v3.1.2-candidate-1 (9f110390ebd3ccaeb67adec9c51631e735414ccd)
> https://github.com/apache/pulsar/releases/tag/v3.1.2-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Docker images:
>
> pulsar images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar
>
> pulsar-all images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar-all
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> Regards
> houxiaoyu
>

Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia  wrote:

> Hi,
>
> I would like to start voting thread for PIP-313  which also addresses issue
> # https://github.com/apache/pulsar/issues/21451
>
> PIP design PR:
> https://github.com/apache/pulsar/pull/21452
>
> Thread:
> https://lists.apache.org/thread/hptx8z9mktn94gvqtt4547wzcfcgdsrv
>
> Thanks,
> Rajan
>

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

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Dec 11, 2023 at 2:20 PM Lari Hotari  wrote:

> Dear Pulsar community,
>
> I am starting a vote thread for "PIP-322: Pulsar Rate Limiting
> Refactoring".
>
> PIP-322 document:
> https://github.com/apache/pulsar/pull/21680
>
> Draft changes for "PIP-322: Pulsar Rate Limiting Refactoring":
> https://github.com/apache/pulsar/pull/21681
>
> Discussion thread:
> https://lists.apache.org/thread/xzrp2ypggp1oql437tvmkqgfw2b4ft33
>
> Please review the PIP document and vote!
>
> Thanks,
>
> Lari
>

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

[guo jiwei]

+1 (binding)

- Verified the signature and checksum
- Build from the source
- Test SampleConsumer and SampleProducer

Regards
Jiwei Guo (Tboy)


On Tue, Dec 12, 2023 at 4:30 PM tison  wrote:

> +1 (binding)
>
> * Download URL valid
> * Checksum and sign match
> * Can build from source
> * LICENSE and NOTICE present
>
> nit: Years in NOTICE can be updated.
>
> Best,
> tison.
>
> Yunze Xu  于2023年12月6日周三 16:00写道：
> >
> > This is the first release candidate for Apache Pulsar Client C++,
> version 3.4.2.
> >
> > It fixes the following issues:
> >
> https://github.com/apache/pulsar-client-cpp/pulls?q=is%3Apr+is%3Aclosed+label%3Arelease%2F3.4.2
> >
> > *** Please download, test and vote on this release. This vote will stay
> open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-cpp/pulsar-client-cpp-3.4.2-candidate-1/
> >
> > SHA-512 checksums:
> >
> d64a07c4f78071ae0607f1afac4ab0db15f9dc25cb1f2ceae7152e262b65e660719f1520f93933da6615691ea0de2f25a6fb2806369126c4a777c0a075af0f5e
> >  apache-pulsar-client-cpp-3.4.2.tar.gz
> >
> > The tag to be voted upon:
> > v3.4.2-candidate-1 (1cb1bf8ba1ca1033b4a36d35514f22fcf150973a)
> >
> https://github.com/apache/pulsar-client-cpp/releases/tag/v3.4.2-candidate-1
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://downloads.apache.org/pulsar/KEYS
> >
> > Please download the source package, and follow
> >
> https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env
> > to compile and test.
> >
> > Note: If you're going to run the unit tests locally, please make sure
> > the proxy is disabled.
>

Re: [VOTE] Pulsar Release 3.1.2 Candidate 2

[guo jiwei]

+1 (binding)

- Checked the signatures
- Built from source
- Run standalone and check the produce, consume
- Verified Cassandra connector
- Verified stateful function


Regards
Jiwei Guo (Tboy)


On Sat, Dec 9, 2023 at 2:48 PM houxiaoyu  wrote:

> This is the second release candidate for Apache Pulsar version 3.1.2.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.1+
>
> *** Please download, test and vote on this release. This vote will
> stay open for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.2-candidate-2/
>
> SHA-512 checksums:
>
> apache-pulsar-3.1.2-bin.tar.gz
>
> 48e2d0069cd69c6f2bf5b5d5aa9fbc775436d3e160bd51645a6626fb86706ddba4901a5d6b87e29a57b9f19c0d0b8c22aef2dfa3d3525260ad55d0a39db6
>
> apache-pulsar-3.1.2-src.tar.gz
>
> 4d29b1f707047d1bd55d8cb8aacb488517fbd82903fef57c9924180b62454725bdbdc53adf7af5d5caa4d57522a10d6eb15028fd929325b9cadd088a6e3de20a
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1256/
>
> The tag to verify:
> v3.1.2-candidate-2 (c4196fba3ae107d74f9421d3f7ed11c0c245f10f)
> https://github.com/apache/pulsar/releases/tag/v3.1.2-candidate-2
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Docker images:
>
> pulsar images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar
>
> pulsar-all images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar-all
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> Regards
> Xiaoyu Hou
>

Re: [VOTE] PIP-323: Complete Backlog Quota Telemetry

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Wed, Dec 13, 2023 at 4:23 PM Asaf Mesika  wrote:

> Hi,
>
> I'm starting the vote for PIP-323, since it has been reviewed by several
> people and all comments have been resolved.
>
> Reminder:
>
> PIP-323 is introduced to fill the gap of backlog quota telemetry. It allows
> the user to know when a time-based backlog quota is about to exceed, and
> how many times it exceeded. It also adds backlog quota check duration
> metric allowing the user to configure the interval for that check based on
> data. Once this is implemented, the user can finally create an alert to
> know when a certain topic is about to exceed its defined backlog quota
> limit, alert on it, and use topic stats Admin API to grab the subscription
> name causing it.
>
> PIP link: https://github.com/apache/pulsar/pull/21709
>
>
> Thanks,
>
> Asaf
>

[DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Hi community,
   It has been more than three months since the release of 3.1.0.  we now
have more than 305 commits

and
26 PIPs

merged.  We'd better prepare for the 3.2.0 release. I would like to cut
branch-3.2 in the next week and freeze the code for two weeks.
   Please leave any ideas or concerns.


Regards
Jiwei Guo (Tboy)

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

[guo jiwei]

+1 (binding)

- Verify the signature and checksum.
- Verified staged maven artifacts by running the test
HelloPulsarClientReactive

We can correct the commit in this thread to v0.5.1-candidate-1
(92a1e390e854876b54936bd0e6d21bf1e5071aeb)


Regards
Jiwei Guo (Tboy)


On Thu, Dec 14, 2023 at 7:39 PM Christophe Bornet 
wrote:

> +0
>
> The git commit is incorrect in the voting mail
> (d45c08827387bd8d2a0d6bdc542c2bf7e4ebcda8 instead of
> 92a1e390e854876b54936bd0e6d21bf1e5071aeb)
> I don't think it needs a new RC but I believe it needs a new voting
> mail with the correct commit.
>
> Regards
>
> Christophe
>
> Le mer. 13 déc. 2023 à 22:59, Chris Bo  a écrit :
> >
> > Following PIP-205: Reactive Java client for Apache Pulsar (
> > https://github.com/apache/pulsar/issues/17335), this is release
> > candidate 1 for the Reactive Java client for Apache Pulsar, version
> 0.5.1.
> >
> > *** Please download, test and vote on this release. This vote will stay
> open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag). Binaries in the Maven
> > repository
> > are provided for convenience.
> >
> > Source package:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.1-candidate-1/
> >
> > SHA-512 checksums:
> >
> def9a9d97ac69ca27bed66f1a1ce15194f589aa95b68f0add75ffa4488efd9eac96bd9af0f278b3eba5872a7bd4c47394127a42b55f4a4a8140ab9f401641238
> >  pulsar-client-reactive-0.5.1-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1257/
> >
> > The tag to be voted upon:
> > v0.5.1-candidate-1 (d45c08827387bd8d2a0d6bdc542c2bf7e4ebcda8)
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.1-candidate-1
> >
> > Please download the source package, and follow detailed instructions for
> > pulsar-client-reactive release validation at
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > .
> >
> > Best regards
> >
> > Chris Bono
>

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

[guo jiwei]

Hi Xiangying,
   I think  we can rename this PIP to:   *Introduce `allowed-clusters` and
`topic-policy-synchronized-clusters` to fully support replication on
message and topic level*
   Currently, we can set replication clusters on the message and topic
level, but the replication clusters should be a subset of the namespace
replication clusters. which means :
   If we set namespace replication clusters: cluster1, cluster2, cluster3,
at most, these three or two clusters can be set on message or topic. If the
user wanna set cluster4 or others, the replication
   can't work as expected.
   It's easy to reproduce by this test:

>@Test

public void testEnableReplicationInTopicLevel() throws Exception {

// 1. Create namespace and topic

String namespace =
> BrokerTestUtil.newUniqueName("pulsar/testEnableReplicationInTopicLevel");

String topic1 = "persistent://" + namespace + "/topic-1";

admin1.namespaces().createNamespace(namespace);

admin1.topics().createNonPartitionedTopic(topic1);

// 2. Configure replication clusters for the topic.

admin1.topics().setReplicationClusters(topic1, List.of("r1", "r2"));

// 3. Check if the replicator connected successfully.

Awaitility.await().atMost(5, TimeUnit.MINUTES).untilAsserted(() -> {

List keys = pulsar1.getBrokerService()

.getTopic(topic1, false).get().get()

.getReplicators().keys();

assertEquals(keys.size(), 1);

assertTrue(pulsar1.getBrokerService()

.getTopic(topic1, false).get().get()

.getReplicators().get(keys.get(0)).isConnected());

});

}


  To fully support the replication, we find out an easy way to solve it.
Introduce `allowed-clusters` on namespace policies, which Xiangying
explains above.
  How could this work and solve the issue? The same example :
  If we set namespace replication clusters: cluster1, cluster2, cluster3,
and
   set topic1 replication clusters: cluster2, cluster4.
   set topic2 replication clusters: cluster1, cluster4.
  We must set `allowed-clusters` with cluster1, cluster2, cluster3, and
cluster4.  The broker side will validate the topic or message replication
clusters from the `allowed-cluster.`
  In this way,  we can simplify more codes and logic here.
  For *`topic-policy-synchronized-clusters` *we also add examples in the
PIP.

  Hope the explanation could help @Rajan @Girish




Regards
Jiwei Guo (Tboy)


On Thu, Dec 7, 2023 at 10:29 PM Xiangying Meng  wrote:

> Hi Girish,
>
> I'm very pleased that we have reached some consensus now. Pulsar already
> supports geo-replication at the topic level, but the existing
> implementation of this topic level replication does not match our
> expectations.
>
> At the moment, I can think of three directions to solve this problem:
>
> 1. Treat this issue as a bug and fix it so that Pulsar can truly support
> replication at the topic level.
> 2. Limit the replication topic policy, so that the replication clusters at
> the topic level must be included in the replication clusters configured at
> the namespace level. In this case, the topic level replication would serve
> as a supplement to the namespace replication, rather than a true topic
> level policy.
> 3. Remove topic level replication.
>
> I lean towards the first option, as it would make Pulsar's replication
> configuration more flexible and would not break the previous behavior
> logic.
>
> >Yes, that's my viewpoint. In case that's not your view point, then in your
> >use cases do you ever have more than one namespace inside a tenant?
> >With every property coming at topic level, it makes no sense for the
> >namespace hierarchy to exist anymore.
>
> I didn't propose this from the perspective of a user, but from the
> perspective of a Pulsar maintainer. The replication cluster at the topic
> level cannot function independently like other topic policies, and I
> attempted to fix it after finding the reason.
>
> From the user's perspective, I could modify my system to put topics with
> the same replication strategy under the same namespace. From the
> maintainer's perspective, if a feature can help users use Pulsar more
> flexibly and conveniently without introducing risks, then this feature
> should be implemented. Perhaps business systems do not want to maintain too
> many namespaces, as they would need to configure multiple namespace
> policies or it might make their business logic complex. The other
> configurations for topics under this namespace might be consistent, with
> only a few topics needing to enable replication. In this case, topic level
> replication becomes valuable. Therefore, I lean towards the first option,
> to solve this problem and make it a truly expected topic policy.
>
> On Thu, Dec 7, 2023 at 12:45 PM Girish Sharma 
> wrote:
>
> > Hello Xiangying,
> >
> >
> > On Thu, Dec 7, 2023 at 6:32 A

Re: [VOTE] PIP-313 Support force unsubscribe using consumer api

[guo jiwei]

We can close this vote with 4 (binding) and 1(non-binding).

Regards
Jiwei Guo (Tboy)


On Mon, Dec 11, 2023 at 9:09 PM Enrico Olivelli  wrote:

> +1 (binding)
>
> Enrico
>
> Il giorno lun 11 dic 2023 alle ore 12:56 Yunze Xu  ha
> scritto:
> >
> > +1 (binding)
> >
> > Thanks,
> > Yunze
> >
> > On Mon, Dec 11, 2023 at 2:18 PM Apurva Telang 
> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > On Sun, Dec 10, 2023 at 6:12 PM guo jiwei 
> wrote:
> > >
> > > > +1 (binding)
> > > >
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > > >
> > > > On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia 
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I would like to start voting thread for PIP-313  which also
> addresses
> > > > issue
> > > > > # https://github.com/apache/pulsar/issues/21451
> > > > >
> > > > > PIP design PR:
> > > > > https://github.com/apache/pulsar/pull/21452
> > > > >
> > > > > Thread:
> > > > > https://lists.apache.org/thread/hptx8z9mktn94gvqtt4547wzcfcgdsrv
> > > > >
> > > > > Thanks,
> > > > > Rajan
> > > > >
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Apurva Telang.
>

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Hi community
  I have cut branch 3.2 and will freeze the code for the next two weeks.

Regards
Jiwei Guo (Tboy)


On Thu, Dec 14, 2023 at 11:40 AM guo jiwei  wrote:

> Hi community,
>It has been more than three months since the release of 3.1.0.  we now
> have more than 305 commits
> <https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged>
>  and
> 26 PIPs
> <https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged+label%3APIP>
> merged.  We'd better prepare for the 3.2.0 release. I would like to cut
> branch-3.2 in the next week and freeze the code for two weeks.
>Please leave any ideas or concerns.
>
>
> Regards
> Jiwei Guo (Tboy)
>

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Thanks Lari.


Regards
Jiwei Guo (Tboy)


On Sat, Dec 23, 2023 at 1:35 AM Lari Hotari  wrote:

> There was a discussion yesterday in the community meeting to make the
> proposed change
> to drop Pulsar SQL (Trino/Presto), already in the 3.2.0 release.
>
> Matteo started the discussion thread:
> https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666
>
> I deleted branch-3.2 for now so that we don't spend unnecessary time
> backporting these changes from master to branch-3.2. Let's cut branch-3.2
> when we have voted about the Pulsar SQL removal and made the changes in
> master branch. I hope this makes sense.
>
> -Lari
>
> On 2023/12/22 03:14:01 guo jiwei wrote:
> > Hi community
> >   I have cut branch 3.2 and will freeze the code for the next two weeks.
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Thu, Dec 14, 2023 at 11:40 AM guo jiwei  wrote:
> >
> > > Hi community,
> > >It has been more than three months since the release of 3.1.0.  we
> now
> > > have more than 305 commits
> > > <
> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged>
> and
> > > 26 PIPs
> > > <
> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged+label%3APIP
> >
> > > merged.  We'd better prepare for the 3.2.0 release. I would like to cut
> > > branch-3.2 in the next week and freeze the code for two weeks.
> > >Please leave any ideas or concerns.
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
> >
>

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

[guo jiwei]

yes, +1 agree


Regards
Jiwei Guo (Tboy)


On Sat, Dec 23, 2023 at 11:37 AM Matteo Merli 
wrote:

> 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 target release 3.2.0 if this change gets accepted?
> >
> > The code freeze for 3.2.0 was about to start today and I blocked that. I
> > removed the already started branch-3.2 (which didn't contain any changes)
> > until the decision has been made. I hope this makes sense. If not, we can
> > always cut the branch again, nothing has been lost.
> >
> > re: https://lists.apache.org/thread/0pl9by5c53nkjp7vld3x89c8nqjrx9on
> >
> > -Lari
> >
> > On 2023/12/22 17:09:19 Matteo Merli wrote:
> > > I want to start a discussion regarding the removal of all the code
> > related
> > > to the Trino (PrestoDB) plugin from the Pulsar main repository.
> > >
> > > This topic was already discussed and approved long time ago in PIP-62 (
> > >
> >
> https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories
> > > )
> > >
> > > The main reasons for not having Presto plugin as part of the main
> > > distribution of Pulsar were (and still are valid):
> > >
> > >  1. We need to ship the entire Presto runtime which is ~400 MB. This
> > makes
> > > our tgz and Docker images huge
> > >  3. There is no strict need for this component to be in the same
> > > distribution / image: it could easily be provided in a different
> release
> > > tgz or Docker image
> > >
> > > Though I think that since then it became more clear that the current
> > state
> > > of this plugin has been stagnating over the years.
> > >
> > > 1. There are not many active users of Pulsar-SQL component (I'd be very
> > > happy to be contradicted here)
> > > 2. The plugin code has not been improved in a long time
> > > 3. There are several open security issues (actually, almost the
> totality
> > of
> > > current dependencies issues are today coming from Trino).
> > >
> > > My suggestion would be that, if there is any volunteer willing to pick
> > this
> > > plugin up and maintain it in a separate repository (within the Apache
> > > Pulsar project) and with a separate release schedule, we should go
> ahead
> > > and move it.
> > > If there are no volunteers, we should just remove it as it is. If later
> > on
> > > we want to revive it, we can always import the code from the last
> commit.
> > >
> > > Thoughts?
> > >
> > >
> > > --
> > > Matteo Merli
> > > 
> > >
> >
>

Re: [VOTE] Pulsar Release 2.11.3 Candidate 2

[guo jiwei]

+1 (binding)


- Checked the signatures
- Built from source
- Run standalone and check the produce, consume
- Verified Cassandra connector
- Verified stateful function

Regards
Jiwei Guo (Tboy)


On Thu, Dec 21, 2023 at 9:32 AM Baodi Shi  wrote:

> This is the second release candidate for Apache Pulsar, version 2.11.3.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed
>
> *** Please download, test and vote on this release. This vote will stay
> open for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.11.3-candidate-2/
>
> SHA-512 checksums:
>
>
> 521316ea9f01b54f0fb3981dc017d3529de4019360c57c38c72c1ecfa53030927b93608acd71d0eb58f3e7eb6b4a2583a94796462d577d7dca0ba935a2f68fcf
>  ./apache-pulsar-2.11.3-bin.tar.gz
>
>
> 4510c16d6ec90847eb8dff0246bd09190f99bc10a30702ab5f521971b13b6cffe0f9d1de9637b85340154ee38764a39551fd871bd1132d7760fb3a7e931a20e3
>  ./apache-pulsar-2.11.3-src.tar.gz
>
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1258/
>
> The tag to be voted upon:
> v2.11.3-candidate-2 (c7ac62c
> <
> https://github.com/apache/pulsar/commit/c7ac62ca9eb718e15c3e3e4a460167643ef3f48b
> >
> )
> https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-2
>
> Pulsar’s KEYS file containing PGP keys you use to sign the release:
> https://downloads.apache.org/pulsar/KEYS
>
> Docker images:
> docker pull wudixiaobaozi/pulsar-all:2.11.3
> docker pull wudixiaobaozi/pulsar:2.11.3
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
> Thanks,
> Baodi Shi
>

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[guo jiwei]

Hi
   https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666 has
been agreed upon, and the related patch has been merged. Now I have cut the
new branch-3.2.


Regards
Jiwei Guo (Tboy)


On Sat, Dec 23, 2023 at 4:34 PM guo jiwei  wrote:

> Thanks Lari.
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Sat, Dec 23, 2023 at 1:35 AM Lari Hotari  wrote:
>
>> There was a discussion yesterday in the community meeting to make the
>> proposed change
>> to drop Pulsar SQL (Trino/Presto), already in the 3.2.0 release.
>>
>> Matteo started the discussion thread:
>> https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666
>>
>> I deleted branch-3.2 for now so that we don't spend unnecessary time
>> backporting these changes from master to branch-3.2. Let's cut branch-3.2
>> when we have voted about the Pulsar SQL removal and made the changes in
>> master branch. I hope this makes sense.
>>
>> -Lari
>>
>> On 2023/12/22 03:14:01 guo jiwei wrote:
>> > Hi community
>> >   I have cut branch 3.2 and will freeze the code for the next two weeks.
>> >
>> > Regards
>> > Jiwei Guo (Tboy)
>> >
>> >
>> > On Thu, Dec 14, 2023 at 11:40 AM guo jiwei 
>> wrote:
>> >
>> > > Hi community,
>> > >It has been more than three months since the release of 3.1.0.  we
>> now
>> > > have more than 305 commits
>> > > <
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged>
>> and
>> > > 26 PIPs
>> > > <
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A3.2.0+is%3Amerged+label%3APIP
>> >
>> > > merged.  We'd better prepare for the 3.2.0 release. I would like to
>> cut
>> > > branch-3.2 in the next week and freeze the code for two weeks.
>> > >Please leave any ideas or concerns.
>> > >
>> > >
>> > > Regards
>> > > Jiwei Guo (Tboy)
>> > >
>> >
>>
>

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

[guo jiwei]

+1 (binding)

- Checked the signature and checksums
- Install the pulsar_client-3.4.0-cp39-cp39-macosx_10_15_universal2.whl
- Run Pulsar standalone
- Run the Python examples producer and consumer


Regards
Jiwei Guo (Tboy)


On Fri, Dec 29, 2023 at 12:34 PM Yunze Xu  wrote:

> +1 (binding)
>
> For source code,
> * verified signatures and checksums
> * built from source on macOS (with C++ client 3.4.2)
>
> For the following wheels, verified end-to-end with OAuth2
> authentication on specific platforms.
> * the wheel built from source (macOS Ventura 13.6.3)
> * pulsar_client-3.4.0-cp312-cp312-macosx_10_15_universal2.whl (macOS
> Ventura 13.6.3)
> *
> pulsar_client-3.4.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
> (Rocky Linux 9)
> *
> pulsar_client-3.4.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
> (Ubuntu 22.04)
>
> Thanks,
> Yunze
>
> On Thu, Dec 28, 2023 at 5:13 PM PengHui Li  wrote:
> >
> > +1 (binding)
> >
> > - Checked the signature
> > - Install the pulsar_client-3.4.0-cp39-cp39-macosx_10_15_universal2.whl
> > - Run Pulsar standalone
> > - Run the Python examples `python3 ./examples/consumer.py` and `python3
> > ./examples/producer.py`
> >
> > Regards,
> > Penghui
> >
> > On Tue, Dec 26, 2023 at 4:54 PM Zike Yang  wrote:
> >
> > > This is the first release candidate for Apache Pulsar Client Python,
> > > version 3.4.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar-client-python/milestone/5?closed=1
> > >
> > > *** Please download, test and vote on this release. This vote will
> > > stay open for at least 72 hours ***
> > >
> > > Python wheels:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-python-3.4.0-candidate-1/
> > >
> > > The supported python versions are 3.8, 3.9, 3.10, 3.11 and 3.12. The
> > > supported platforms and architectures are:
> > > - Windows x86_64 (windows/)
> > > - glibc-based Linux x86_64 (linux-glibc-x86_64/)
> > > - glibc-based Linux arm64 (linux-glibc-arm64/)
> > > - musl-based Linux x86_64 (linux-musl-x86_64/)
> > > - musl-based Linux arm64 (linux-musl-arm64/)
> > > - macOS universal 2 (macos/)
> > >
> > > You can download the wheel (the `.whl` file) according to your own OS
> > > and Python version
> > > and install the wheel:
> > > - Windows: `py -m pip install *.whl --force-reinstall`
> > > - Linux or macOS: `python3 -m pip install *.whl --force-reinstall`
> > >
> > > The tag to be voted upon: v3.4.0-candidate-1
> > > (v3.4.0-candidate-1)
> > > https://github.com/apache/pulsar-client-python/tree/v3.4.0-candidate-1
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://downloads.apache.org/pulsar/KEYS
> > >
> > > Please download the Python wheels and follow the README to test.
> > >
>

[VERIFY] Pulsar Release 3.2.0 Candidate 1

[guo jiwei]

This is the first release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Jan 15 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-1/

SHA-512 checksums:

cf4e661d78f4194f4cde88e102bc9a734e2777613c5315f09115d64236759fbc5ded868c7e0cc3d07813c3fd34b1b123ca6f06f4335d6c9c96393789c6eda5bc

apache-pulsar-3.2.0-bin.tar.gz

6ebe72de801db9a3f51dde39587b93d947904856385a21020319edb6988776fd68ec079471bcce5db17ea1b79c58e22ebf89a854debb40437ad9dc2bc2350357

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1259/

The tag to verify:
v3.2.0-candidate-1 (4ab09374ade3c1402812c3c6be0d07984ab373a4)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-1/

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Docker images:

pulsar images:
https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-4ab0937/images/sha256-06d35d60f3bd4f954b8b1b6f4cc4f663556ace5da097173f41a61622e81a76b9?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-4ab0937/images/sha256-a6f87bc5fd8025f096f35f26d47303267452e35d92f9f974d8536b61543ddbeb?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.


Regards
Jiwei Guo (Tboy)

Re: [VERIFY] Pulsar Release 3.2.0 Candidate 1

[guo jiwei]

Hi Zike,
   Thanks for reporting this, drop this candidate, I will raise a new
candidate after the fix.


Regards
Jiwei Guo (Tboy)


On Fri, Jan 12, 2024 at 10:46 AM Zike Yang  wrote:

> There is a regression bug introduced in 3.2.0:
> https://github.com/apache/pulsar/issues/21888
> The producer name will be conflicted when multiple consumers in the
> same topic and subscription send messages to the same DLQ
> concurrently.
>
> I will provide a fix later.
>
> Best,
> Zike Yang
>
> On Tue, Jan 9, 2024 at 8:34 PM houxiaoyu  wrote:
> >
> > +1 (non-binding)
> >
> >
> > - Checksum and signatures
> > - Build on Mac, using JDK17.0.8
> > - Run Pulsar standalone and produce/consume case
> >
> > Thanks,
> > Xiaoyu Hou
> >
> > guo jiwei  于2024年1月9日周二 16:15写道：
> > >
> > > This is the first release candidate for Apache Pulsar version 3.2.0.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/pulsar/milestone/36?closed=1
> > >
> > > *** Please download, test and verify on this release. This release
> > > candidate verification will stay open until Jan 15 ***
> > >
> > > Note that we are verifying upon the source (tag), binaries are
> provided for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-1/
> > >
> > > SHA-512 checksums:
> > >
> > >
> cf4e661d78f4194f4cde88e102bc9a734e2777613c5315f09115d64236759fbc5ded868c7e0cc3d07813c3fd34b1b123ca6f06f4335d6c9c96393789c6eda5bc
> > >
> > > apache-pulsar-3.2.0-bin.tar.gz
> > >
> > >
> 6ebe72de801db9a3f51dde39587b93d947904856385a21020319edb6988776fd68ec079471bcce5db17ea1b79c58e22ebf89a854debb40437ad9dc2bc2350357
> > >
> > > apache-pulsar-3.2.0-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1259/
> > >
> > > The tag to verify:
> > > v3.2.0-candidate-1 (4ab09374ade3c1402812c3c6be0d07984ab373a4)
> > > https://github.com/apache/pulsar/commits/v3.2.0-candidate-1/
> > >
> > > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > >
> > > Docker images:
> > >
> > > pulsar images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-4ab0937/images/sha256-06d35d60f3bd4f954b8b1b6f4cc4f663556ace5da097173f41a61622e81a76b9?context=repo
> > > <
> https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore
> >
> > > pulsar-all images:
> > >
> https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-4ab0937/images/sha256-a6f87bc5fd8025f096f35f26d47303267452e35d92f9f974d8536b61543ddbeb?context=repo
> > >
> > > Please download the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> > > Note that this RC doesn't require a formal vote, but we would also
> > > appreciate your feedback with +1/-1. And please provide specific
> > > comments if your feedback is not +1.
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
>

Re: [VOTE] PIP-325: Add command to abort transaction

[guo jiwei]

+1 (binding)


Regards
Jiwei Guo (Tboy)


On Mon, Jan 15, 2024 at 9:36 AM PengHui Li  wrote:

> +1 (binding)
>
> Regards,
> Penghui
>
> On Mon, Jan 8, 2024 at 4:00 PM Enrico Olivelli 
> wrote:
>
> > +1 (binding)
> >
> >
> > Enrico
> >
> > Il Lun 8 Gen 2024, 03:55 ruihongzhou  ha
> > scritto:
> >
> > > Hi community,
> > >
> > > This thread is to start a vote for PIP-325: Add command to abort
> > > transaction.
> > >
> > > PIP: https://github.com/apache/pulsar/pull/21731
> > >
> > > Releted PR: https://github.com/apache/pulsar/pull/21630
> > >
> > >  Discussion thread:
> > > https://lists.apache.org/thread/ssgngyrlgx36zvygvsd5b2dm5q6krn0f
> > >
> > > Ruihong
> > >
> > >
> > >
> > > ruihongzhou
> > > ruihongz...@qq.com
> > >
> > >
> > >
> > >  
> >
>