Re: [VOTE] Pulsar Node.js Client Release 1.11.0 Candidate 4

+1 (binding) - Verified checksum and signature - Built from source on macOS arm64 and run the example - Installed from the npm registry using node 12,14,16,18,20 on ubuntu - Installed from the npm registry on macos - Ran the example BR, Zike Yang On Tue, Apr 16, 2024 at 8:38 AM 津田秀介 wrote: > >

Re: [VOTE] PIP-327 Support force topic loading for unrecoverable errors

Hi, This PIP allows system admin to skip any failures regardless of schema loss to avoid impact on business critical topics where availability is higher priority than schema. This PIP was created 4 months back and the same question was answered in the PIP discussion thread and PR as well. Thanks,

Re: [DISCUSS] Solution after missing schema

>> If the schema is lost and the automatic skip is selected (and there is no configuration to control whether this behavior is turned on, it is on by default) Skipping for any failure must be controlled by a flag to support fixing issues with bulk topic and that can be used by on-demand by the adm

Re: [VOTE] PIP-327 Support force topic loading for unrecoverable errors

Please go here first to discuss the solution after the schema is lost. We have some conflicts on the solution. (It is only related to the schema part of this PIP) https://lists.apache.org/thread/zbkpypb1yw89op510f7zg7cdkns1om0q Thanks, sinan Apurva Telang 于2024年4月17日 周三02:43写道： > +1 (non-bind

Re: [DISCUSS] Solution after missing schema

The two solutions are conflicting. If the schema is lost and the automatic skip is selected (and there is no configuration to control whether this behavior is turned on, it is on by default), the next time you use this topic, the schema must be the lost schema. If there are three versions of sch

Re: [VOTE] PIP-327 Support force topic loading for unrecoverable errors

+1 (non-binding) On Tue, Apr 16, 2024 at 10:11 AM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il Mar 16 Apr 2024, 19:08 Rajan Dhabalia ha > scritto: > > > Hi, > > > > I would like to start voting thread for PIP-327 which also addresses > issue > > # https://github.com/apache/pulsar/is

Re: [DISCUSS] Solution after missing schema

Hi, Broken schema ledgers and topic unavailability are the issues we have been trying to resolve for multiple years now and We have been trying to add lot of patches to fix but we still find different usecases which can make topic unavailable when schema ledger is not recoverable (ledger is delete

Re: [VOTE] PIP-327 Support force topic loading for unrecoverable errors

+1 (binding) Enrico Il Mar 16 Apr 2024, 19:08 Rajan Dhabalia ha scritto: > Hi, > > I would like to start voting thread for PIP-327 which also addresses issue > # https://github.com/apache/pulsar/issues/21751 > > PIP design PR: > https://github.com/apache/pulsar/pull/21752 >

[VOTE] PIP-327 Support force topic loading for unrecoverable errors

Hi, I would like to start voting thread for PIP-327 which also addresses issue # https://github.com/apache/pulsar/issues/21751 PIP design PR: https://github.com/apache/pulsar/pull/21752 Thread: https://lists.apache.org/thread/w7w91xztdyy07otw0dh71nl

Re: Re[2]: DotPulsar version 3.2.0

Thanks for looking into this Lari :) On 2024/04/16 07:29:46 Lari Hotari wrote: > It seems to match the issue. > > In this case, there were 2 emails that started a new thread with the same > subject. In the UI, > when you go to https://lists.apache.org/list.html?dev@pulsar.apache.org and > clic

[DISCUSS] Solution after missing schema

#17221 describes an environment when multiple bookie copies are corrupted, or a Ledger has been deleted. The loss of schema ledger results in new producers and consumers not even being created and working properly. At present, if the integrity of the

[DISCUSSION] Event time based compaction

Hello everyone, I'd like to initiate a discussion regarding the compaction feature in Pulsar topics. Currently, there are two types of compactors available: `TwoPhaseCompactor` and `StrategicTwoPhaseCompactor`. The latter is specifically utilized for internal load balancing purposes and is not empl

Re: [RESULT][VOTE] Apache Pulsar DotPulsar 3.2.0 released

Correct link to the voting thread is https://lists.apache.org/thread/grw25nklrgsrcr7pshy7zl4n0zslcj7s -Lari On 2024/04/08 17:36:56 David Jensen wrote: > [RESULT][VOTE] Release Apache DotPulsar 3.2.0 > > The vote to release Apache DotPulsar 3.2.0 has passed. > > The vote PASSED with xxx binding

Re: Re[2]: DotPulsar version 3.2.0

It seems to match the issue. In this case, there were 2 emails that started a new thread with the same subject. In the UI, when you go to https://lists.apache.org/list.html?dev@pulsar.apache.org and click on the thread, they will be shown as a single thread. However, with the permanent link, t

Re: Re[2]: DotPulsar version 3.2.0

The bug might have been already reported as this issue: https://github.com/apache/incubator-ponymail/issues/427 -Lari On 2024/04/16 07:20:57 Lari Hotari wrote: > Please report the issue to > https://github.com/apache/incubator-ponymail/issues . > > The "mail viewer" is called "Apache Pony Mail"

Re: Re[2]: DotPulsar version 3.2.0

Please report the issue to https://github.com/apache/incubator-ponymail/issues . The "mail viewer" is called "Apache Pony Mail" and here's the support page: https://ponymail.apache.org/support.html You can also join the #asfinfra channel on ASF slack (https://the-asf.slack.com/archives/CBX4TSBQ8