Please vote so that we can get the Apache Pulsar Helm Chart released with
Pulsar 3.0.3 that contains the fixes for the security advisories [1] published
a week ago.
Thanks!
-Lari
1 - https://pulsar.apache.org/security/
On 2024/03/15 12:34:18 Lari Hotari wrote:
> Hello Apache Pulsar Community,
Thanks for the comments, Yunze.
On 2024/03/18 05:48:39 Yunze Xu wrote:
> I'm afraid many people don't have patience to read all the contents.
I agree. However, in async work, people should have more patience to read and
write. Synchronous meetings aren't a good solution either. The lack of patie
Making a change to formatting is a broad change that cause more harm than
benefit to the Pulsar project currently.
We can reconsider after the maintenance strategy has been revisited.
The discussion about the maintenance strategy is in a separate thread [1].
Even with a different type of mainten
Comment with better formatting on GitHub:
https://github.com/apache/pulsar/issues/22277#issuecomment-2002553745
• Deprecate java label. Pulsar is written in Java and most PRs update Java
code.
• Instead of removing labels, deprecate them by renaming them to
deprecated/. Probably pick an
Hi all,
I'd like to start a discussion about improving Pulsar broker cache design.
In the Pulsar broker, there are two main scenarios for message
dispatching to consumers: tailing (hot) reads and catch-up (cold)
reads. In both scenarios consumers can be fast or slow which also
impacts the scenari
Top
tison 于2023年6月30日周五 09:58写道：
> Hi,
>
> I'd like to propose applying a consistent code style (especially whitespace
> and indent) with an autotool Spotless.
>
> // Background
>
> Over and over we argue contributors reformat their patch manually for
> checkstyle violations, or even whitespace
