+1
houxiaoyu 于2023年7月24日周一 20:00写道：
> +1
>
> Thanks
> Xiaoyu Hou
>
> 丛搏 于2023年7月24日周一 19:58写道：
>
> > Hi, Pulsar Community
> >
> > I opened a new PIP design PR.
> >
> > https://github.com/apache/pulsar/pull/20859
> >
> > Thanks,
> > Bo
> >
>
--
BR,
Qiang Huang
improvements to
> > > > Pulsar and its CI pipeline. In addition to his technical
> contributions,
> > > > Nicolò also plays an important role in reviewing pull requests and
> > > > ensuring the overall quality of our project. We look forward to his
> > > > continued contributions.
> > > >
> > > > On behalf of the Pulsar PMC, we extend a warm welcome and
> > > > congratulations to Nicolò Boschi.
> > > >
> > > > Best regards, Lari, on behalf of the Pulsar PMC
> > > >
> > >
>
--
BR,
Qiang Huang
> Welcome Bo Cong to the Apache Pulsar PMC.
> >
> > Best Regards,
> > Penghui on behalf of the Pulsar PMC
> >
>
--
BR,
Qiang Huang
t;
> > Welcome and congratulations, Baodi Shi!
> >
> > Please join us in congratulating and welcoming Baodi Shi onboard!
> >
> > Thanks,
> > Yunze on behalf of the Pulsar PMC
> >
>
--
BR,
Qiang Huang
> > (https://github.com/BewareMyPower) as a member of the PMC and we are
> > pleased to announce that he has accepted.
> >
> > He is very active in the community in the past few years and made a lot
> of great contributions.
> >
> > Welcome Yunze to the Apache Pulsar PMC.
> >
> > Best Regards,
> > Haiting Jiang on behalf of the Pulsar PMC
>
>
--
BR,
Qiang Huang
> > > > project since there is no need to go via the patch
> > > > > submission process. This should enable better productivity.
> > > > >
> > > > > Welcome and congratulations, Cong Zhao!
> > > > >
> > > > > Please join us in congratulating and welcoming Cong Zhao onboard!
> > > > >
> > > > > Best Regards,
> > > > > Haiting on behalf of the Pulsar PMC
> > > > >
> > > >
> >
>
--
BR,
Qiang Huang
On Nov 10, 2022 at 8:16 AM +0800, dev@pulsar.apache.org, wrote:
> > >
> > > Congratulations! tison
>
--
BR,
Qiang Huang
elcome and congratulations, Lin Chen!
> >
> > Please join us in congratulating and welcoming Lin Chen onboard!
> >
> > Best Regards,
> > Penghui on behalf of the Pulsar PMC
> >
>
--
BR,
Qiang Huang
fsk708sgb1n7vbo
> > > https://lists.apache.org/thread/k090ftlqc149yr1cnprxb29vxg160131
> > >
> > > PIP: https://github.com/apache/pulsar/issues/18182
> > >
> > > Thanks,
> > > bo
> > >
>
--
BR,
Qiang Huang
ing
> > > > Jiang
> > > > > (https://github.com/Jason918) as a member of the PMC and we are
> > > > > pleased to announce that he has accepted.
> > > > >
> > > > > He is very active in the community on GitHub.
> > > > >
> > > > > Welcome Haiting to the Apache Pulsar PMC
> > > > >
> > > > > Best Regards,
> > > > > Hang Chen on behalf of the Pulsar PMC
> > > >
> > >
> >
>
--
BR,
Qiang Huang
to be voted upon:
> > > > > v2.10.2-candidate-3 (11b5df797b2e9cb48dfc38137f0b7ef736a8a47c)
> > > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-3
> > > > >
> > > > > 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/jason918/pulsar/2.10.2/images/sha256-6a501a0dc0e05b6bbd76e0f9edd1ff7223d0447bd318332dcf9551b48e831cf9
> > > > >
> > > > >
> > >
> https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-fd3e027771f08eb224a3a9e8874514f0f258a0356059120d3f25f151f96506c8
> > > > >
> > > > > Please download the source package, and follow the
> > > > > release-candidate-validation doc to build
> > > > > and run the Pulsar standalone service.
> > > > >
> > > > >
> > >
> https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md
> > > > >
> > > > > Thanks,
> > > > > Haiting
> > > > >
> > >
>
--
BR,
Qiang Huang
; > > > README.md to build and run the pulsar-client-go.
> > > > > >
> > > > > > The vote will be open for at least 72 hours. It is adopted by
> > majority
> > > > > > approval, with at least 3 PMC affirmative votes.
> > > > > >
> > > > > > Source file:
> > > > > >
> > > > > >
> > > > >
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.9.0-candidate-2/
> > > > > >
> > > > > > The tag to be voted upon:
> > > > > > v0.9.0
> > > > > >
> > > > >
> >
> https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0-candidate-2
> > > > > >
> > > > > > SHA-512 checksums:
> > > > > >
> > > > > >
> > > > >
> >
> 9731d6a0615288e77feb4b73fedbbdf6d275ebefeee3cee5fc4e849f38789863f0532c7e8b93eb1e601bd98f9bb21d50a714fcf87fac9987a745a052bbe23ca3
> > > > > > apache-pulsar-client-go-0.9.0-candidate-2-src.tar.gz
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Xiaolong Ran
> > > > > >
> > > > >
> >
>
--
BR,
Qiang Huang
pling Java, C++ and Python releases will make each of
> them
> > > > > much easier.
> > > > >
> > > > > We'll be able to do patch releases with a tenth of the manual work
> > > involved.
> > > > >
> > > > > > > The client <--> broker compatibility is in general always
> > > guaranteed.
> > > > > >
> > > > > > I think we should make this more visible in our Pulsar
> > documentation.
> > > > > > It's a fantastic feature, and I get the sense that it is not well
> > > > > > known.
> > > > >
> > > > > Agree, it's something that still surprises a lot of people.
> > >
> >
>
--
BR,
Qiang Huang
22年9月27日周二 09:56写道：
> >
> >> +1 (non)
> >>
> >> Haiting
> >>
> >> On Tue, Sep 27, 2022 at 9:30 AM Zike Yang wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>>
> >>> Zike Yang
> >>>
> >>> On Tue, Sep 27, 2022 at 9:24 AM Kai Wang
> >> wrote:
> >>>>
> >>>> +1 (non-binding)
> >>>>
> >>>> Thanks,
> >>>> Kai
> >>
>
>
--
BR,
Qiang Huang
el free to comment on this doc.
> > > > > Sincerely,
> > > > > Xiangying
> > > > >
> > > > > On Wed, Sep 7, 2022 at 4:55 PM Xiangying Meng <
> xiangy...@apache.org>
> > > > wrote:
> > > > >
> > > > > > Hi, community
> > > > > > I,d like to start a vote for the PIP-196
> > > > > > <https://github.com/apache/pulsar/issues/16913> Segmented
> > > transaction
> > > > > > buffer snapshot.
> > > > > > And the discussion can be found here
> > > > > > <
> https://lists.apache.org/thread/bqoy3oz8flvxy7xpmnw81cr4c9sz5vy0>.
> > > > > >
> > > > > > Sincerely,
> > > > > > Xiangying
> > > > > >
> > > > > >
> > > >
> > >
>
--
BR,
Qiang Huang
. The broker will no longer close the TCP connection
> (with its adverse effects on other consumers and produces "riding" on that
> connection)
> c. Reset the cursor to the newly requested position.
> d. Continue dispatching messages from newly requested positions to
> co
ys 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
has been changed a lot since that. It looks other codes are not
> much related to these two overloads now. IMO, we should not encourage
> users to use these two overloads, so I suggest marking them as
> deprecated and might remove them in future releases.
>
>
> Thanks,
> Yunze
>
>
>
>
>
--
BR,
Qiang Huang
ulsar/issues/17155
> >> This is the discussion:
> >> https://lists.apache.org/thread/287ft8twc11cp4s1y4qkcx5nmh451cyo
> >>
> >> I am still working on the PR, that is the subject of the VOTE.
> >>
> >> Best regards
> >> Enrico Olivelli
> >>
>
>
--
BR,
Qiang Huang
; > > 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
> > > > >
> > > >
> > >
>
--
BR,
Qiang Huang
Here is the PR: https://github.com/apache/pulsar/pull/17248.
>
> Thanks,
> Michael
>
--
BR,
Qiang Huang
ps://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.2+
> > [1]
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.2+-label%3Acherry-picked%2Fbranch-2.10+
> > [2]
> >
> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.10.2+
> >
> > Best Regards
> > Haiting Jiang
> >
>
--
BR,
Qiang Huang
behaviour causes some test scenarios to go unchecked and risk
> > > introducing some regressions, and I think we need to make this test
> group
> > > set required.
> > >
> > > e.g. https://github.com/apache/pulsar/pull/17163
> > >
> > > WDYT?
> > >
> > > Best,
> > > Mattison
> > >
> >
>
--
BR,
Qiang Huang
adds
> check permissions method in authorization provider, no grant, revoke, and
> get action, so I want to add this feature.
>
> Best,
> Zixuan
>
--
BR,
Qiang Huang
; > This Project is currently only for clients maintained by the main
> > > pulsar repository, such as C++ and Python clients.
> > >
> > > I have created a PR [1] to add C++ and Python client issues and PRs to
> > > the Multi Clients project.
> > >
> > > Please let me know what you think. Thanks!
> > >
> > > [0] https://github.com/apache/pulsar/projects/12
> > > [1] https://github.com/apache/pulsar/pull/17201
> > >
> > > Best,
> > > Zike Yang
> >
> >
>
--
BR,
Qiang Huang
t; > > has a fixed producer
> > > > name, this will make the message deduplication work properly.
> > > >
> > > > The test introduced in https://github.com/apache/pulsar/pull/17154
> will
> > > > check the message
> > > > replication ordering. Without the message deduplication enabled, the
> test
> > > > is flaky with received
> > > > duplicated messages. After enabling, everything is fine.
> > > >
> > > > Best,
> > > > Penghui
> > > >
> > > > [0]
> https://github.com/apache/pulsar/pull/17154#discussion_r948736894
> > > >
> > >
>
--
BR,
Qiang Huang
t; Apache Kvrocks (Incubating)[2] and I believe the INFRA team would be
> happy
> > to see an explicit community consensus.
> >
> > Best,
> > tison.
> >
> > [1]
> >
> https://github.blog/changelog/2022-02-03-more-ways-to-keep-your-pull-request-branch-up-to-date/
> > [2] https://issues.apache.org/jira/browse/INFRA-23432
> >
--
BR,
Qiang Huang
quest-in-sync-with-the-base-branch
> >
> > This is an example where I activated the button in my own Pulsar fork:
> > https://github.com/nicoloboschi/pulsar/pull/4
> >
> > Thanks,
> > Nicolò Boschi
> >
--
BR,
Qiang Huang
> > > Zixuan
> > >
> > > Jun M 于2022年8月19日周五 10:16写道：
> > >
> > > > Congrats to Jiwei!
> > > >
> > > >
> > > > Cheers,
> > > > Jun
> > > >
> > >
> >
>
--
BR,
Qiang Huang
broker] PIP-198: Support xx
> >
> > - Cherry pick changes [4]
> > Choice A: [fix][broker][branch-2.9] xxx
> > Choice B: [fix][broker] xxx. And add "cherry pick xxx to branch-2.9" in
> the
> > PR description.
> >
> > ~~
> >
> > Feel free to comment and make your voice heard. Go vote! Thank you!
> >
> > [1]
> >
> https://docs.google.com/document/d/1sJlUNAHnYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit
> > [2] https://lists.apache.org/thread/90rcjf1dv0fbkb5hm31kmgr65fj0nfnn
> > [3]
> >
> https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
> > [4]
> >
> https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=kix.849jztd92uk7
> >
> > Yu
>
>
--
BR,
Qiang Huang
> > Because I'm still unfamiliar with the latter two topics yet and I'd
> prefer
> > to implement these improvements one by one since they're naturally
> > independent. If I try to make a completed proposal at once, it's highly
> > possible I give up halfway.
> >
> > Anything else?
> > ===
> >
> > Previous discussion:
> >
> > [DISCUSS] Move Pulsar SQL to a separated repository?
> > https://lists.apache.org/thread/mflm0pb5235jjk80vol0vs7v0hvowkq8
>
--
BR,
Qiang Huang
perimental-spring-support-for-apache-pulsar
> >
> > Looking forward to any feedback, feature request and PR contributions!!
> >
> > Best Regards,
> > Soby Chacko
> >
> --
> Best,
> tison.
>
--
BR,
Qiang Huang
we haven't any action to request to refresh
>> the original authentication data, so we need to add an auth data const to
>> request to refresh the original authentication data, so like
>> `AuthData.REFRESH_AUTH_DATA`.
>>
>> Once most people agree with this, I'll make a PIP.
>>
>> References:
>>
>> - https://github.com/apache/pulsar/pull/13339
>> - https://github.com/apache/pulsar/issues/10816
>>
>> Thanks,
>> Zixuan
>>
>>
--
BR,
Qiang Huang
original motivation and PR here:
> > > https://github.com/apache/pulsar/pull/10754
> > >
> > > IMO, we can also apply it to pulsar-proxy, because when a large
> > > number of proxy accesses under the same IP (maybe due to some wrong
> > > operations) will cause the proxy to accept too much wrong traffic and
> > > cause service unstable.
> > >
> > > WDYT?
> > >
> > > Best,
> > > Mattison
> > >
>
--
BR,
Qiang Huang
discussion thread at
> > > > > https://lists.apache.org/thread/qn59jwn47w9ngxpkvq3kswbl1y882jth.
> > > > >
> > > > > The vote will stay open for at least 48 hours.
> > > > >
> > > > > Best regards.
> > > > >
> > > > > Christophe Bornet
> > > > >
> > >
> >
> >
> > --
> > Best Regards,
> > Neng
> >
>
--
BR,
Qiang Huang
s direction.
> >
> > PIP-157 [3] assumes "Pulsar is able to manage millions of topics but the
> > number of topics within a single namespace is limited by metadata
> > storage.". Does this assumption hold?
> >
> > For example, "3) Scalability issue: all metadata changes are broadcasted
> > to all brokers" will become a challenge in a large system with a high
> > number of brokers. Together with the other Metadata consistency
> challenges
> > ( 1 and 2 above), I have a doubt that after PIP-157 is implemented, the
> > bottlenecks will move to these areas. In that sense, it might be a
> band-aid
> > that won't address the root cause of the Pulsar Metadata handling
> > scalability challenges.
> >
> > Let's discuss and address the challenges together!
> >
> > Regards,
> >
> > -Lari
> >
> > [1] - analysis about Metadata consistency from user's point of view -
> > https://github.com/apache/pulsar/issues/12555#issuecomment-955748744
> > [2] - MetadataStore interface:
> >
> https://github.com/apache/pulsar/blob/master/pulsar-metadata/src/main/java/org/apache/pulsar/metadata/api/MetadataStore.java
> > [3] - PIP-157: Bucketing topic metadata to allow more topics per
> namespace
> > - https://github.com/apache/pulsar/issues/15254
> > [4] - PIP-45: Pluggable metadata interface -
> >
> https://github.com/apache/pulsar/wiki/PIP-45%3A-Pluggable-metadata-interface
> >
> > [5] - StreamNative's blog "Moving Toward a ZooKeeper-Less Apache Pulsar"
> -
> >
> https://streamnative.io/blog/release/2022-01-25-moving-toward-a-zookeeperless-apache-pulsar/
> >
>
--
BR,
Qiang Huang
t;
> Voting will stay open for at least 48h.
>
> [0] https://github.com/apache/pulsar/issues/16569
> [1] https://lists.apache.org/thread/ftr7qhxhglso3bnsv8lvlgoxmx419ymg
>
> Thanks.
>
--
BR,
Qiang Huang
ng will stay open for at least 48h.
>
> [0] https://github.com/apache/pulsar/issues/16680
> [1] https://lists.apache.org/thread/cdw5c2lpj5nwzl2zqyv8mphsqqv9vozj
>
> Thanks,
> Xiaoyu
>
--
BR,
Qiang Huang
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 写道：
> >
> > +
0:45写道：
> > I suggest to include 'topic' in the flag, we have too many entities in
> > Pulsar
>
> Thanks, change it to `topicTwoPhaseDeletionEnabled`.
>
--
BR,
Qiang Huang
t; > >>> And more detail in [2].
> > >>>
> > >>> Please take a look and feel free to comment on it.
> > >>>
> > >>> Regarding the current Pulsar CI, I have a question. Why do we need to
> > >>> add doc_only check at each step when skipping code tests instead of
> > >>> just skipping the whole job for PR with only doc changes? [3] Is
> there
> > >>> any concern?
> > >>>
> > >>> Please let me know what you think. Thanks!
> > >>>
> > >>>
> > >>> [0] https://github.com/apache/pulsar/pull/16988
> > >>> [1] https://github.com/RobertIndie/pulsar-ci-test/pull/1
> > >>> [2]
> > >> https://github.com/RobertIndie/pulsar-ci-test/actions/runs/2829525510
> > >>> [3]
> > >>
> https://github.com/apache/pulsar/blob/master/.github/workflows/pulsar-ci.yaml#L380
> > >>>
> > >>> Best,
> > >>> Zike Yang
> > >>
> > >>
> >
>
--
BR,
Qiang Huang
I agree that the customized one is better. +1 on the customized one.
Jun M 于2022年8月12日周五 10:51写道：
> +1 on the customized one.
>
>
> Cheers
> momo-jun
>
>
--
BR,
Qiang Huang
> I noticed we are using OpenJDK in our Docker image, I suggest that we
> > > switch to the Temurin JDK, because our CI runs on the Temurin JDK, we
> > need
> > > to keep the same JDK everywhere to avoid unexpected problems. Thanks,
> > > Zixuan
> > >
> >
>
--
BR,
Qiang Huang
ar/pull/17038 to
> > > add the PRs and issues
> > > with `flaky-tests` label to this project automatically.
> > >
> > > BTW, I also have some questions about the Github Project automation. As
> > > the description of
> > > column `Review in progress, it said the PR with request changes would
> go
> > > to this column
> > > automatically. But it doesn't work. I'm not sure why.
> > > [image: image.png]
> > >
> > > Best,
> > > Penghui
> > >
> > >
> >
>
--
BR,
Qiang Huang
[
https://issues.apache.org/jira/browse/PULSAR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579311#comment-17579311
]
Qiang Huang commented on PULSAR-22:
---
Could you please submit an issue in [h
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
se 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
pulsar/issues/16691
> >
> > Thank you,
> > -Heesung
> >
>
--
BR,
Qiang Huang
a vote on PIP 198: Standardize PR Naming
> > Convention
> > > > using GitHub Actions [3].
> > > >
> > > >
> > > > This proposal contains:
> > > >
> > > > - Why do this?
> > > >
> > > > - How do this?
> > > >
> > > > - Pre-discussions and other thoughts
> > > >
> > > > Feel free to comment, thank you!
> > > >
> > > > [1] https://lists.apache.org/thread/sk9ops3t94jmzc5tndk08y9khf7pj6so
> > > >
> > > > [2] https://github.com/apache/pulsar/pulls
> > > >
> > > > [3]
> > > >
> > > >
> >
> https://docs.google.com/document/d/1sJlUNAHnYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit?pli=1#
> > > >
> > > >
> > > > Yu, Max, mangoGoForward
> > > >
> >
>
--
BR,
Qiang Huang
new consumer with new epoch.
>
> The consumer will reconnect to the broker during the seek operation.
> And this will change the existing behavior. It doesn't seem to make
> sense. Please correct me if I have misunderstood.
>
> Thanks,
> Zike Yang
>
> On Wed, Jul 27, 2022
d the
> discussion thread is available at [1].
> Voting will stay open for at least 48h.
>
> [0] https://github.com/apache/pulsar/issues/16153
> [1] https://lists.apache.org/thread/o9k7trfmxrz89b0woybnshonpkq8ybw1
>
> Thanks,
> Haiting Jiang
>
--
BR,
Qiang Huang
Thanks Zike.
> > - stage 1: Check the current cursor status when handling flowPermits
from
> > the server side.
> > Could you explain more details on this step? It looks like there is
not much described above. What kind of status needs to be checked, and
what kind of behavior will the broker take?
Congratulations, Micheal !!!
Max Xu 于2022年7月27日周三 14:08写道：
> Congratulations, Michael !
>
> Best,
> Max Xu
>
>
> On Wed, Jul 27, 2022 at 2:04 PM Kai Wang
> wrote:
>
> > Congratulations Michael!
> >
> > Thanks,
> > Kai
> >
>
--
BR,
Qiang Huang
+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
> wrote:
> >
> > +1
> > Thanks,
> > Haiting
> >
> > On 2022/07/25 02:23:20 Anon
None yet.
## Note
1. Consumer reconnect need reset epoch.
--
BR,
Qiang Huang
batchMessageContainer.hasSameTxn(msg);
> }
>
> ```
>
>
> ## Reject Alternatives
>
> - Implement a `AbstractBatchMessageContainer` , saying
> `BatchMessagePropertiesBasedContainer`, keeping messages with same
> properties in a single `hashmap` entry, like
> `BatchMessageKeyBasedContainer`.
>
> Rejection reason: This will publish messages out of order
>
>
>
> Thanks,
> Xiaoyu Hou
>
--
BR,
Qiang Huang
sion", 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
> > > >
> >
>
--
BR,
Qiang Huang
roducer, to make it produce a
> > regular message instead of a batch message if the batch contains only
> > 1 message
> >
> > Thoughts ?
> >
> > Enrico
> >
>
--
BR,
Qiang Huang
itter enables easier contribution to the
> > > > project since there is no need to go via the patch
> > > > submission process. This should enable better productivity.
> > > >
> > > > Welcome and congratulations, Zixuan Liu!
> > > >
> > > > Please join us in congratulating and welcoming Zixuan Liu onboard!
> > > >
> > > > Best Regards,
> > > > Yu on behalf of the Pulsar PMC
> > > >
> > >
> >
>
--
BR,
Qiang Huang
ontaining 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
```
> >>>>
> >>>> * Suggest to do like this:
> >>>> ```
> >>>> for (int i = 0; i < partitionMetadata.partitions; i++) {
> >>>> TopicName topicNamePartition =
> topicName.getPartition(i);
> >>>>topicStatsFutureList.add(
> >>>>
> >>>> pulsar().getNamespaceService().isServiceUnitOwnedAsync(topicName)
> >>>>.thenCompose(owned -> {
> >>>>if (owned) {
> >>>>// local call
> >>>>return
> >>>> getTopicReferenceAsync(topicNamePartition)
> >>>>.thenCompose(topic ->
> >>>>
> >>>> topic.asyncGetStats(getPreciseBacklog, subscriptionBacklogSize,
> >>>>getEarliestTimeInBacklog));
> >>>>} else {
> >>>>// call from admin client
> >>>>try {
> >>>>
> >>>>
> pulsar().getAdminClient().topics().getStatsAsync(topicNamePartition.toString()),
> >>>>getPreciseBacklog,
> >>>> subscriptionBacklogSize, getEarliestTimeInBacklog)
> >>>>} catch (PulsarServerException e) {
> >>>>throw new RestException(e);
> >>>>}
> >>>>}
> >>>>})
> >>>>);
> >>>> ```
> >>>>
> >>>> Thanks,
> >>>> Xiaoyu Hou
> >>>>
> >>>>
> >>>>
>
>
--
BR,
Qiang Huang
/16281
and the discussion thread is available at
https://lists.apache.org/thread/36vyyhndr4og175k2bz3mfdf5ctd2xky
Voting will stay open for at least 48h.
--
BR,
Qiang Huang
roker for assignning bundle ?
> > - select a broker based on which one has the least resource usage with
> > weight.
> >
> > ### New configuration options
> > The existing cache implementation will not be removed at this point.
> Users
> > will
> > be able to configure the old implementation in `broker.conf`.
> > This option will be helpful in case of performance regressions would be
> > seen for
> > some use cases with the new strategy implementation.
> > ```
> > # load assignment strategy, support LeastLongTermMessageRate and
> > LeastResourceUsageWithWeight, default is LeastLongTermMessageRate
> >
> >
> loadBalancerLoadAssignmentStrategy=org.apache.pulsar.broker.loadbalance.impl.LeastResourceUsageWithWeight
> > ```
> >
> > Below are screenshots of the effect of the new strategy with less time
> and
> > fewer load balancing times.
> > https://user-images.githubusercontent.com/4970972/176346492-f2ccdfda-b011-406d-88fe-df73d8bb839b.png
> > ">
> > https://user-images.githubusercontent.com/4970972/176346531-63a9b8b0-ef7b-4f74-a904-37d7c07c1793.png
> > ">
> >
> > ## Reject Alternatives
> > None yet.
> >
> > ## Reference
> > [1] https://github.com/apache/pulsar/pull/16059
> > [2] https://github.com/apache/pulsar/issues/16274
> > [3] https://github.com/apache/pulsar/pull/16281
> >
> > --
> > BR,
> > Qiang Huang
> >
>
--
BR,
Qiang Huang
discussion thread is available at
> https://lists.apache.org/thread/m8vkxl46njm7sh0r1mqsn25jggq9v8kb
>
> Voting will stay open for at least 48h.
>
> Thanks
> Yubiao Feng
>
--
BR,
Qiang Huang
64 matches
Mail list logo
