Re: [DISCUSS] Subscription Naming Rules

+1 Add a subscription name naming rule, for example: can only contain these characters "a-zA-Z_0-9" or "-=:.%". I think the subscription name should not contain special characters. It should keep the same naming rule with the topic. lordcheng10 于2022年10月1日周六 11:12写道： > Corresponding PR: >

Re: [DISCUSS] Subscription Naming Rules

Corresponding PR: https://github.com/apache/pulsar/pull/17151 lordcheng10 于2022年10月1日周六 11:10写道： > Hello, Pulsar community: > When creating a subscription, pulsar does not verify the name of the > subscription, so the subscription name may contain some invisible > characters in the created

[DISCUSS] Subscription Naming Rules

Hello, Pulsar community: When creating a subscription, pulsar does not verify the name of the subscription, so the subscription name may contain some invisible characters in the created subscription. If the subscription name contains some invisible characters, when we delete the subscription by

Re: [DISCUSS] Changed pulsar-go-client minimum Go SDK version from 1.15 to 1.16

I thought about this a bit more and realized that ldflags doesn't really make sense in this case because this is a library, and we don't control the user's build environment. It might work fine for the pulsar-perf binary, but doesn't really make sense in the context of users who are consuming the

[GitHub] [pulsar-dotpulsar] blankensteiner commented on pull request #110: modified the "hello world" to fix first run issue

blankensteiner commented on PR #110: URL: https://github.com/apache/pulsar-dotpulsar/pull/110#issuecomment-1264043353 Thanks! :-) -- 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 specific

[GitHub] [pulsar-dotpulsar] blankensteiner merged pull request #110: modified the "hello world" to fix first run issue

blankensteiner merged PR #110: URL: https://github.com/apache/pulsar-dotpulsar/pull/110 -- 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 specific comment. To unsubscribe, e-mail:

[GitHub] [pulsar-dotpulsar] aintJoshinya commented on pull request #110: modified the "hello world" to fix first run issue

aintJoshinya commented on PR #110: URL: https://github.com/apache/pulsar-dotpulsar/pull/110#issuecomment-1263815938 @blankensteiner gotcha! Thanks for the feedback! I've revised the update. -- This is an automated message from the Apache Git Service. To respond to the message, please log

[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. The issue got resolved. I upgraded it to 2.10.1 (the latest version) And basically, the issue was, I was setting some custom properties which had a key and a value, but the value was

[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. I suggest you can open an issue to describe this issue with more details, including broker version 2.8.x?, sample code to reproduce this. GitHub link:

Broken link on Docker Hub

On the page https://hub.docker.com/r/apachepulsar/pulsar, there is a link to "run Pulsar in standalone mode", https://pulsar.apache.org/docs/en/standalone-docker/ which directs to a 404. I think the other links are working correctly. Niclas Hedhman

[GitHub] [pulsar-dotpulsar] blankensteiner commented on pull request #110: modified the "hello world" to fix first run issue

blankensteiner commented on PR #110: URL: https://github.com/apache/pulsar-dotpulsar/pull/110#issuecomment-1263140651 Hi @aintJoshinya Thanks for the PR! I agree with the minimal optional configuration, but setting the initial position is the right solution and one I find people