New Feature Proposal: flag to require a non-partitioned topic on Producer/Consumer Builder
Hello, I have a use case in which my application MUST use a non-partitioned topic to work properly, but the topic name is (of course) configurable by the user. If I am not using a non-partitioned topic, I do not have string guarantees on the ordering of the message (because messages will be spread across multiple partitions). Currently there is no way to require that the topic IS a NON-PARTITIONED topic. Especially when the topic does not exist yet, you configured the namespace to create partitioned topics by default. Using a PulsarAdmin preliminary call is not a good workaround because it is expensive, and ideally I want to be able to create the Producer (or the Consumer) and see that everything works automatically, failing in case of a partitioned topic. Thoughts ? Enrico
Re: [ANNOUNCE] New Committer: Aloys Zhang
Congratulations! Best, Dianjin Wang On Thu, Feb 10, 2022 at 10:46 AM linlin wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Aloys > Zhang > > (https://github.com/aloyszhang) to become a committer and we are pleased > to > > announce that he has accepted. > > Aloys Zhang joined the Pulsar community in June 2020 and contributed a lot > of commits > to the community, including PIP-70 which brings lightweight broker entry > metadata > to Pulsar and some other pull requests: > https://github.com/apache/pulsar/pulls?q=is%3Apr+assignee%3Aaloyszhang+. > > Welcome and Congratulations, Aloys Zhang! Please enjoy the journey as a > committer :) > > Please join us in congratulating and welcoming Aloys Zhang onboard! > > Best Regards, > Lin Lin on behalf of the Pulsar PMC >
