[GitHub] [pulsar] raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level. 1. If I just set` enableRetry(true)`, how much time does it wait to confirm whether an acknowledgement is done or not and replay the message? Because we are not using any timeout here.

[GitHub] [pulsar] Jason918 added a comment to the discussion: Need max redelivery count at message level.

GitHub user Jason918 added a comment to the discussion: Need max redelivery count at message level. > .enableRetry(true) Please notice: This will set the dead letter policy implicitly with `maxRedeliverCount=16`, so if you calls `reconsumeLater` on the same message over 16 times, it will goe

Re: [DISCUSS] PIP-209: Separate C++/Python clients to own repositories

Sent from my iPhone > On Sep 19, 2022, at 7:29 PM, Baodi Shi wrote: > > Hi, @merlimat. Looks good to me. > >> Both C++ and Python clients will continue with their own individual >> versioning. >> >> In order to not break anything or cause more confusion, we would need to use >> a new ver

Pulsar Summit Asia 2022 CFP is Open Now!

Hi Apache Pulsar community members, Pulsar Summit Asia 2022 will be hosted virtually on November 19th and 20th, 2022. It is expected to cover the pivotal topics and technologies at the core of Apache Pulsar. The CFP is open now

Re: [DISCUSS] PIP-209: Separate C++/Python clients to own repositories

Hi - This is great and I agree with the plan except for one missing discussion. The work needs to either include how to create documentation in the new repository and move it to the pulsar-site repository. (This might be better as a new PIP which could also include the go and node clients alrea

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. My consumer looks like this right now: > pulsarClient.newConsumer() .topic("my-topic") .subscriptionType(SubscriptionType.Shared)

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. My consumer looks like this right now: > pulsarClient.newConsumer() .topic("my-topic") .subscriptionType(SubscriptionType.Shared)

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. My consumer looks like this right now: > pulsarClient.newConsumer() .topic("my-topic") .subscriptionType(SubscriptionType.Shared)

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. My consumer looks like this right now: > pulsarClient.newConsumer() .topic("my-topic") .subscriptionType(SubscriptionType.Shared)

[GitHub] [pulsar] raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level. My consumer looks like this right now: `pulsarClient.newConsumer() .topic("my-topic") .subscriptionType(SubscriptionType.Shared)

Re: [DISCUSS] PIP-209: Separate C++/Python clients to own repositories

Hi, @merlimat. Looks good to me. > Both C++ and Python clients will continue with their own individual > versioning. > > In order to not break anything or cause more confusion, we would need to use > a new version that is bigger than the current version (2.11.x). > > The suggestion is to start

[GitHub] [pulsar] Jason918 added a comment to the discussion: Need max redelivery count at message level.

GitHub user Jason918 added a comment to the discussion: Need max redelivery count at message level. Have you set `deadLetterPolicy` in `ConsumerBuilder` ? It must be set before you can call `reconsumeLater()`. And once you do, it will create its own retry topic and DLQ with default settings. Y

[DISCUSS] PIP-209: Separate C++/Python clients to own repositories

https://github.com/apache/pulsar/issues/17724 ## Motivation Pulsar C++ code base is in the same main repository for the Pulsar project. While the decision was the right one at the time, there is a considerable overhead in keeping the C++ client in its current position. ### Issues with the cur

[GitHub] [pulsar-test-infra] merlimat closed issue #73: [pulsarbot] Bot should not comment on closed/merged PRs

merlimat closed issue #73: [pulsarbot] Bot should not comment on closed/merged PRs URL: https://github.com/apache/pulsar-test-infra/issues/73 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the spec

Re: [CI] Change to be made in Pulsar CI to mitigate CI resource consumption issues

I have pushed a fix in PR https://github.com/apache/pulsar/pull/17723 , please review. -Lari On 2022/09/19 15:26:14 Lari Hotari wrote: > Unfortunately a PR approval isn't currently detected by the solution > Until this is fixed, the reviewer will have to add a "ready-to-test" label > before add

[DISCUSS] PIP-208: HTTP Sink

Hi all, I have drafted PIP-208: HTTP Sink PIP link: https://github.com/apache/pulsar/issues/17719 Here's a copy of the contents of the GH issue for your references: ### Motivation Currently, when you want to consume from Pulsar topics in applications written in languages that don't have a Puls

Re: [CI] Change to be made in Pulsar CI to mitigate CI resource consumption issues

Unfortunately a PR approval isn't currently detected by the solution Until this is fixed, the reviewer will have to add a "ready-to-test" label before adding a comment "/pulsarbot rerun-failure-checks" to the PR so that the PR can be eventually merged. I'm sorry about this inconvenience. -Lari

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. Thanks for your reply @Jason918 . One last question, do we need a retry topic to implement reconsumeLater()? Or can it work without that? So, basically, I have a main topic which is subs

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. Thanks for your reply @Jason918 . One last question, do we need a retry topic to implement reconsumeLater()? Or can it work without that? So, basically, I have a main topic which is subs

[GitHub] [pulsar] raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level. Thanks for your reply @Jason918 . One last question, do we need a retry topic to implement reconsumeLater()? Or can it work without that? So, basically, I have a main topic which is subsc

[GitHub] [pulsar] Jason918 added a comment to the discussion: Need max redelivery count at message level.

GitHub user Jason918 added a comment to the discussion: Need max redelivery count at message level. > How does message gets removed from the main queue? You can manually ack this message from main queue after you send the message to DLQ successfully. GitHub link: https://github.com/apache/p

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. One question I have is, If I manually move the message to DLQ after my custom implementation for the number of retries, does that message gets acknowledged/removed from the main queue?

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. One question I have is, If I manually move the message to DLQ after my custom implementation for the number of retries, does that message gets acknowledged/removed from the main queue?

[GitHub] [pulsar] raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level. One question I have is, If I manually move the message to DLQ after my custom implementation for the number of retries, does that message gets acknowledged/removed from the main queue?

[GitHub] [pulsar-test-infra] nodece commented on a diff in pull request #71: Improve comment messages

nodece commented on code in PR #71: URL: https://github.com/apache/pulsar-test-infra/pull/71#discussion_r974019243 ## docbot/action.go: ## @@ -13,10 +13,7 @@ import ( ) const ( - MessageLabelMissing = `Please provide a correct documentation label for your PR. -Instruc

[ANNOUNCE] Apache Pulsar 2.8.4 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.8.4. 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 subsc

Re: [ANNOUNCE] Apache Pulsar 2.8.4 released

Sorry I should have sent the email in my Apache mail. I will send it again. Thanks, Yunze > On Sep 19, 2022, at 16:41, Yunze Xu wrote: > > The Apache Pulsar team is proud to announce Apache Pulsar version 2.8.4. > > Pulsar is a highly scalable, low latency messaging platform running on > co

[ANNOUNCE] Apache Pulsar 2.8.4 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.8.4. 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 subsc

[GitHub] [pulsar-helm-chart] astylos opened a new issue, #289: Support for kubernetes 1.25

astylos opened a new issue, #289: URL: https://github.com/apache/pulsar-helm-chart/issues/289 I am unable to upgrade Pulsar version after upgrading kubernetes to 1.25.0 ``` $ microk8s kubectl get nodes NAME STATUS ROLESAGEVERSION centos8vm02 Ready 34

[GitHub] [pulsar-test-infra] Anonymitaet commented on a diff in pull request #71: Improve comment messages

Anonymitaet commented on code in PR #71: URL: https://github.com/apache/pulsar-test-infra/pull/71#discussion_r973950108 ## docbot/action.go: ## @@ -13,10 +13,7 @@ import ( ) const ( - MessageLabelMissing = `Please provide a correct documentation label for your PR. -In