Re: [DISCUSS] PIP-124: Pulsar Client Shared State API

Matteo, Il Mer 29 Dic 2021, 02:57 Matteo Merli ha scritto: > > * Add an API to the Java client that makes it easier to maintain a > consistent Share State between instances of an application. > > * Provide some ready to use recipes, like a simple key-value store > > > > It is not a goal to

Re: [VOTE] PIP 131: Resolve produce chunk messages failed when topic level maxMessageSize is set

+1 Thanks, Zike On Wed, Dec 29, 2021 at 11:26 AM PengHui Li wrote: > > +1 > > Thanks, > Penghui > > On Wed, Dec 29, 2021 at 10:29 AM Haiting Jiang > wrote: > > > This is the voting thread for PIP-131. It will stay open for at least 48h. > > > > https://github.com/apache/pulsar/issues/13544 > >

[GitHub] [pulsar-manager] sourabhaggrawal opened a new pull request #437: Set read/write access to resource for each role

sourabhaggrawal opened a new pull request #437: URL: https://github.com/apache/pulsar-manager/pull/437 ### Motivation Assign resource level read/write access to each role of a user. This way we can assign multiple resources to a user with read/write permission. * A user may

Re: [DISCUSSION] PIP-128: Add new command STOP_PRODUCER and STOP_CONSUMER

What is the background of the requirement? Usually, we will not force to close the producer and consumer at the server-side, because we don't if the client-side can handle this case well. Or, if the topic will retire, and you don't want the clients to connect to it, you can just terminate the

Re: [VOTE] PIP 131: Resolve produce chunk messages failed when topic level maxMessageSize is set

+1 Thanks, Penghui On Wed, Dec 29, 2021 at 10:29 AM Haiting Jiang wrote: > This is the voting thread for PIP-131. It will stay open for at least 48h. > > https://github.com/apache/pulsar/issues/13544 > > The discussion thread is >

Re: [DISCUSSION] PIP-128: Add new command STOP_PRODUCER and STOP_CONSUMER

Issue: https://github.com/apache/pulsar/issues/13488 > 2021年12月29日 10:3812，包子 写道： > > ## Motivation > > Broker send `CLOSE_PRODUCER/CLOSE_CONSUMER` to client when delete topic, But > client will be reconnect. If config `allowAutoTopicCreation=true` will > trigger create topic again. > >

[DISCUSSION] PIP-128: Add new command STOP_PRODUCER and STOP_CONSUMER

## Motivation Broker send `CLOSE_PRODUCER/CLOSE_CONSUMER` to client when delete topic, But client will be reconnect. If config `allowAutoTopicCreation=true` will trigger create topic again.

[VOTE] PIP 131: Resolve produce chunk messages failed when topic level maxMessageSize is set

This is the voting thread for PIP-131. It will stay open for at least 48h. https://github.com/apache/pulsar/issues/13544 The discussion thread is https://lists.apache.org/thread/c63d9s73j9x1m3dkqr3r38gyp8s7cwzf ## Motivation Currently, chunk messages producing fails if topic level

Re: [DISCUSSION] PIP-124: Create init subscription before sending message to DLQ

> Oh, that's a very interesting point. I think it'd be easy to add that > as "internal" feature, though I'm a bit puzzled on how to add that to > the producer API I think we can add a field `String initialSubscriptionName` to the Producer Configuration. And add a new field `optional string

Re: [DISCUSS] PIP-124: Pulsar Client Shared State API

> * Add an API to the Java client that makes it easier to maintain a consistent > Share State between instances of an application. > * Provide some ready to use recipes, like a simple key-value store > > It is not a goal to implement a Pulsar backed Database system While the first use case for

[GitHub] [pulsar-adapters] eolivelli commented on a change in pull request #31: [Issue #29] [pulsar-spark] Adding SparkPulsarReliableReceiver

eolivelli commented on a change in pull request #31: URL: https://github.com/apache/pulsar-adapters/pull/31#discussion_r776054579 ## File path: pulsar-spark/src/main/scala/org/apache/pulsar/spark/SparkStreamingReliablePulsarReceiver.scala ## @@ -0,0 +1,158 @@ +package

[GitHub] [pulsar-adapters] michaeljmarshall commented on issue #29: Pulsar - Spark adapter for scala 2.11

michaeljmarshall commented on issue #29: URL: https://github.com/apache/pulsar-adapters/issues/29#issuecomment-1002236797 @aditiwari01 - try running `mvn initialize license:format` from the base directory of the project. Let me know if that doesn't work. -- This is an automated message

Re: [DISCUSSION] PIP-130: Apply redelivery backoff policy for ack timeout

+1 I missed that we haven't cherry picked that change to 2.9. Thanks for your confirmation Enrico Il Mar 28 Dic 2021, 12:44 PengHui Li ha scritto: > Enrico > > > What do you mean with 'redelivery backorder has not been released yet'? > > I think you mean "redelivery backoff has not been

Re: [DISCUSSION] PIP-130: Apply redelivery backoff policy for ack timeout

Enrico > What do you mean with 'redelivery backorder has not been released yet'? I think you mean "redelivery backoff has not been released yet"? This proposal changed the public APIs, but the changed APIs are introduced by https://github.com/apache/pulsar/pull/12566, we don't have a release

[DISCUSSION] Support custom and pluggable consumer selector

Hi Pulsar Community, When we try to Introduce pulsar to our existing system, compatibility is our first consideration. Firstly, our production system uses jump consistent hash algorithm to select consumers, but pulsar uses range consistent hash algorithm natively. It's impossible for us to