+1. Performance optimization requires observation first.
On 2025/02/24 06:37:56 WenZhi Feng wrote:
> Totally agree with this. No more unnecessary complexity into the code base.
> Wenzhi Feng.
>
> On 2025/02/22 09:01:55 Yunze Xu wrote:
> > Bump this thread again.
> >
> > I really suffered from th
Bumping this thread again to remind Pulsar PMC members that we urgently need
binding votes to publish releases containing a critical severity CVE-2025-24970
fix (details in the thread).
These are the active release voting threads:
* [VOTE] Release Apache Pulsar 3.0.10 based on 3.0.10-candidate-1
Hi all,
I noticed two PRs were merged recently and cherry-picked into
branch-3.0 and branch-4.0, where 3.0 and 4.0 are LTS releases.
https://github.com/apache/pulsar/pull/24012 fixes a bug for the
implementation of PIP-322. However, it adds a new configuration
without a new PIP or change on the e
Creating a PIP could emphasize that new configs are added and explain
why these configs are introduced. While with a regular PR, especially
for many recent PRs that have thousands lines of changes, the
configuration changes are easy to be ignored. Your question can be
applied for all changes requir
Same confusion about the criterion of PIP.
Wenzhi Feng.
On 2025/02/26 04:42:27 Yunze Xu wrote:
> Hi all,
>
> I noticed two PRs were merged recently and cherry-picked into
> branch-3.0 and branch-4.0, where 3.0 and 4.0 are LTS releases.
>
> https://github.com/apache/pulsar/pull/24012 fixes a bug
I opened a PR to clean up some recent config changes:
https://github.com/apache/pulsar/pull/24027
Pulsar's configuration is like a trashbox, to which everyone throws
trash without any consideration. Some configs are hard to understand
without looking into the implementation details. The PIP requir
The changes to broker configs can be shown by the following command:
```
git log --pretty=oneline
pulsar-broker-common/src/main/java/org/apache/pulsar/broker/ServiceConfiguration.java
```
Then I found some other PRs.
https://github.com/apache/pulsar/pull/23709 adds an
`allowAclChangesOnNonExiste
For some of the added configurations, you are right that PIPs are needed.
Most configurables are settings for internal implementation details
that don't need to be changed. The reason why configurable options are
added is that it's useful if the value can be modified when a user
faces an issue tha
Hello Apache Pulsar Community,
This is a call for the vote to release the Apache Pulsar version 3.3.5
based on 3.3.5-candidate-2.
Included changes since the previous release:
https://github.com/apache/pulsar/compare/v3.3.4...v3.3.5-candidate-2
*** Please download, test and vote on this release.
3.3.5-candidate-2 and 4.0.3-candidate-2 have now been made ready for voting.
3.0.10-candidate-1 voting continues.
Please vote on the 3.0.10, 3.3.5 and 4.0.3 releases so that we get the CVE fix
published:
* [VOTE] Release Apache Pulsar 3.0.10 based on 3.0.10-candidate-1
- https://lists.apache.org
+1 (binding)
-Lari
On 2025/02/24 15:33:16 Alexandre DUVAL wrote:
> Hi, I'd like to start the voting thread for PIP-402: Role Anonymizer for
> Pulsar LoggingProposal PR: https://github.com/apache/pulsar/pull/23592
> Rendered PIP
> document:
> https://github.com/KannarFr/pulsar/blob/31d4e2ff1cd
Hello Apache Pulsar Community,
This is a call for the vote to release the Apache Pulsar version 4.0.3
based on 4.0.3-candidate-2.
Included changes since the previous release:
https://github.com/apache/pulsar/compare/v4.0.2...v4.0.3-candidate-2
*** Please download, test and vote on this release.
12 matches
Mail list logo
