Re: [VOTE] PIP-315: Configurable max delay limit for delayed delivery

+1 (binding) Best, Mattison On 2023/11/15 03:59:46 Kevin Lu wrote: > Hi All, > > This thread is to start a vote for PIP-315. > > PIP: https://github.com/apache/pulsar/pull/21490 > Discussion thread: > https://lists.apache.org/thread/285nm08842or324rxc2zy83wxgqxtcjp > > Regards, > Kevin >

Re: [VOTE] PIP-280 : Refactor CLI Argument Parsing Logic for Measurement Units using JCommander's custom converter

+1(binding) Best, Mattison On 2023/07/07 09:25:22 Joo Hyuk Kim wrote: > Hi community, > > This PIP has received a couple of approvals in github PR link [1] > So I thought it's time to vote. > > ## Motivation > > In the current Pulsar codebase, the logic to parse CLI arguments for > measurement

Re: [DISCUSS] Allow the producer to connect to the topic with producer_request_hold backlog policy

eout is 30 > > > seconds. Therefore, many sends will likely timeout on the client side > > > before the broker updates the topic's state to "writable" and lets the > > > producer reconnect. To use this feature meaningfully, it might make > > > sens

Re: [DISCUSS] Allow the producer to connect to the topic with producer_request_hold backlog policy

Hi, Penghui I support your opinion. It looks like we do not support the `producer_request_hold` semantics. We just easily use the same behaviour like `producer_exception`. Maybe it's a missing feature. Best, Mattison On 2022/08/11 05:28:25 PengHui Li wrote: > Hi all, > > Pulsar has a backlo

Re: [DISCUSSION] PIP-156: Enable system topic by default

On 2022/04/26 12:07:32 guo jiwei wrote: > Hi community: >In PIP-39 > , > we have introduced namespace event to support topic level policy. This > feature was released in Pulsar 2.6. > >Then PIP-92 >