[GitHub] [pulsar-manager] karankardas opened a new issue #396: where is SPRING_CONFIGURATION_FILE: /pulsar-manager/pulsar-manager/application.properties

karankardas opened a new issue #396: URL: https://github.com/apache/pulsar-manager/issues/396 I have used docker-compose file. `version: "3.7" services: pulsar: image: apachepulsar/pulsar command: bin/pulsar standalone hostname: pulsar ports: -

Re: [VOTE] Pulsar Release 2.8.0 Candidate 2

+1 binding Checked: * Signatures * Bin distribution: - NOTICE, README, LICENSE - Start standalone service and producer/consumer test * Src distribution: - NOTICE, README, LICENSE - Compile and unit tests - Start standalone service * Checked staging maven repository ar

[GitHub] [pulsar-helm-chart] uiot-stack commented on issue #124: pulsar waiting to start: PodInitializing

uiot-stack commented on issue #124: URL: https://github.com/apache/pulsar-helm-chart/issues/124#issuecomment-857319583 I have the some issue -- 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

Re: [VOTE] Pulsar Release 2.8.0 Candidate 1

I agree that using 'fsGroup' is the proper solution.  If we are concerned about PR#10743 setting the permissions to 644 as a security risk, then why are we not also reverting it? If this is a legitimate problem, then are we not introducing a security risk in 2.8.0? Also, why not just revert it

Re: [VOTE] Pulsar Release 2.8.0 Candidate 2

Sorry for the typo, ``` 9f7304c3d35db97998a16a46362433c43c61d20eb3d2f51eb43175fa79728925175d4646c2cd72ad39fc614e425814af1b9a8a8635545cea291a28e28d57 apache-pulsar-2.8.0-SNAPSHOT-bin.tar.gz 8fe7e30c3cda0993114996dced0bf49986365a76bcc69b2e68160d6a9e52c9e9a2bc174eba7eb0c7467f6a62e009ee7d8a3457e0

[VOTE] Pulsar Release 2.8.0 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.8.0. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A2.8.0+-label%3Arelease%2F2.7.1+-label%3Arelease%2F2.7.2+is%3Aclosed *** Please download, test and vote on this release. This vote will

Re: [VOTE] Pulsar Release 2.8.0 Candidate 1

Il giorno mar 8 giu 2021 alle ore 09:22 Sijie Guo ha scritto: > > Enrico, > > PR#10743 doesn't fix the problem and it actually made things worse. I am a > bit surprised that the change was merged without a review from other > committers who are more familiar with the Pulsar Functions codebase. > >

Correct TopicName#getPartitionIndex implementation

Hi all, Currently the Java implementation to get the partition index of a topic name is not correct. See https://github.com/apache/pulsar/pull/8341/files#diff-445b0cfa56ca0c784df78e73d9294f2a37f079ca3c15c345b03c09d56f81ebff

Re: [VOTE] Pulsar Release 2.8.0 Candidate 1

Enrico, PR#10743 doesn't fix the problem and it actually made things worse. I am a bit surprised that the change was merged without a review from other committers who are more familiar with the Pulsar Functions codebase. 1) First of all, the problem can happen when you using an old version of a b