Thanks for submitting this PIP. I agree there is a gap in the existing
feature offering, but I think we'll need a more nuanced approach for
compatibility with existing clusters.
Here is some relevant historical context that anyone evaluating this
PIP might find motivating.
https://github.com/apac
@PengHui
The test `BrokerServiceTest.testBrokerStatsTopicLoadFailed` that was
introduced by https://github.com/apache/pulsar/pull/19236 always fails, and
https://github.com/apache/pulsar/pull/20494 disabled it.
We need to fix it before cherry-picking it into other branches. Please
review the PR h
+1 (non-binding)
> Can we please close this VOTE thread as it's been more than 8 days to this
> thread and 4 months since we created a PIP.
The condition for PIP to pass is 3 bindings. Let's wait a moment.
Thanks,
Zixuan
Rajan Dhabalia 于2024年4月25日周四 02:51写道：
> Hi,
>
> Can we please close this
+1
In the future, I think we should maintain the client LTS version page here:
https://pulsar.apache.org/docs/next/client-libraries/
The original page is so hard to find that I guess users won't find it
easily: https://pulsar.apache.org/contribute/release-policy/
Thanks,
Baodi Shi
On Apr 25, 2
Hi,
Can we please close this VOTE thread as it's been more than 8 days to this
thread and 4 months since we created a PIP. Please let me know if we have
any concern and can we close the VOTE so we can move forward with this PIP.
Thanks,
Rajan
On Tue, Apr 16, 2024 at 7:09 PM Rajan Dhabalia
wrote
???The Apache Pulsar team is proud to announce DotPulsar version 3.2.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
subscr
https://github.com/apache/pulsar/pull/22578
---
# PIP-347: Extend LTS release process to client SDKs
## Motivation
PIP-175 [1] has introduced the concept of LTS releases in Pulsar, with a
defined cadence of feature and LTS release and setting a clear expectation
in terms of support window for
The vote to release Apache DotPulsar 3.2.1 has passed.
The vote PASSED with 3 binding +1 and 0 -1 votes:
Binding votes:
- tison
- Daniel Blankensteiner
- Lari Hotar
Vote thread:
https://lists.apache.org/thread/z2p8vpk9of4w0on1tdrbxlqq26wndg25
Thank you to all the above members for helping us to
+1 (binding)
David Jensen
On 2024/04/19 08:43:06 David Jensen wrote:
> Hi everyone,
>
> Please review and vote on the release candidate for the version 3.2.1, as
> follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> DotPulsar's
bump
太上玄元道君 于2024年4月11日周四 18:20写道：
> Hi, Pulsar community,
>
> I'm opening this thread to discuss the retention policy for managed
> ledgers.
>
> Currently, the retention policy is defined as a time/size-based policy to
> retain messages in the ledger, but there is a difference between the
> off
+1, It's great for LTS versions.
Thanks
Haiting
On Tue, Apr 23, 2024 at 9:07 PM Yubiao Feng
wrote:
>
> Hi Penghui
>
> Agree with you
>
> Thanks
> Yubiao Feng
>
> On Mon, Apr 22, 2024 at 5:40 PM PengHui Li wrote:
>
> > Hi, all
> >
> > I would like to start a discussion to cherry-pick
> > https:/
+1 (binding)
- ran tests
Using dotnet sdk 8.0.204 (dotnet --version) on Windows 10.
/db
David Jensen skrev den 2024-04-19 10:43:
Hi everyone,
Please review and vote on the release candidate for the version 3.2.1,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (pl
+1 (binding)
- verified source release file hash and signature
- ran build
- validated the Nuget package using a simple Pulsar app
Using dotnet sdk 8.0.204 (dotnet --version) on MacOS arm64.
Used the documented validation process on MacOS:
https://github.com/apache/pulsar-dotpulsar/blob/master/do
13 matches
Mail list logo
