Re: [VOTE] [PIP-182] Provide new load balance placement strategy implementation for ModularLoadManagerStrategy

[Kai Wang]

+1 (non-binding)

Thanks,
Kai

[GitHub] [pulsar-manager] whichdew opened a new issue, #471: login error!

[GitBox]

whichdew opened a new issue, #471:
URL: https://github.com/apache/pulsar-manager/issues/471

   after deploy pulsar with helm, i can't login pulsar-manager with default 
credencials! how to solve it?


-- 
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: dev-unsubscr...@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-manager] whichdew commented on issue #471: login error!

[GitBox]

whichdew commented on issue #471:
URL: https://github.com/apache/pulsar-manager/issues/471#issuecomment-1178753254

   ```shell
   CSRF_TOKEN=$(curl http://backend-service:7750/pulsar-manager/csrf-token)
   curl \
   -H "X-XSRF-TOKEN: $CSRF_TOKEN" \
   -H "Cookie: XSRF-TOKEN=$CSRF_TOKEN;" \
   -H 'Content-Type: application/json' \
   -X PUT http://backend-service:7750/pulsar-manager/users/superuser \
   -d '{"name": "admin", "password": "apachepulsar", "description": "test", 
"email": "usern...@test.org"}'
   ```


-- 
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: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-manager] whichdew closed issue #471: login error!

[GitBox]

whichdew closed issue #471: login error!
URL: https://github.com/apache/pulsar-manager/issues/471


-- 
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: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-client-node] HenriqueSerafim commented on issue #222: Installed pulsar-client-node successfully but when require the module throw "Error: The specified module could not be found."

[GitBox]

HenriqueSerafim commented on issue #222:
URL: 
https://github.com/apache/pulsar-client-node/issues/222#issuecomment-1178780237

   hey @HyperClockUp, any news on this? I'm stuck in the same error too.


-- 
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: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

[Enrico Olivelli]

+1 (binding)
- built from sources, with JDK11, run a couple of smoke tests
- verified RAT
- verified checksums and signatures
- run some JMS tests using Transactions (the JMS library bundles
2.10.x Java client)

Thanks for driving the release!

Enrico

Enrico

Il giorno mer 6 lug 2022 alle ore 10:26 mattison chao
 ha scritto:
>
> This is the second release candidate for Apache Pulsar, version 2.9.3.
>
> It fixes the following issues:
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
>  
> 
>
> *** Please download, test and vote on this release. This vote will stay open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.3-candidate-2/
>
> SHA-512 checksums:
>
> 291eb3f9da234cf38fcd02de781def9a9354025bb4f98c78b160935a6a9c6721cc8280d80b93049656ee5a20e36ddc5d3446b7b034405c07d447833ff65e
>   ./apache-pulsar-2.9.3-bin.tar.gz
>
> d57fa3c8eae1f3ba60422a56288c99a472a671295e41573c884a9d9a71b5fcf622782732e9cfd5128e1b92304b3812cc877675384ac0dbc78109d7efb23681f4
>   ./apache-pulsar-2.9.3-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1163/
>
> The tag to be voted upon:
> v2.9.3-candidate-2 (dd9a5f1f91651b634600f66c53dcc6ad855fb669)
>
> https://github.com/apache/pulsar/releases/tag/v2.9.3-candidate-2
>
> The docker images:
>
> https://hub.docker.com/layers/248117318/mattison/pulsar/2.9.3-rc-2/images/sha256-a7ac6d5ffb2d77102ca6633313c9d0265c1c89c8b0fe859023fbaf3e0d0a7910?context=repo
>
> https://hub.docker.com/layers/247907545/mattison/pulsar-all/2.9.3-rc-2/images/sha256-00e6a886a9285107027afb4c3218c9340efb96627100ff2f1c95d1177bd8dbbe?context=repo
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS 
> 
>
> Please download the source package, and follow the Release Candidate
> Validation[1]
> to validate the release
>
> [1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation 
> 

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

[Qiang Huang]

+1

Enrico Olivelli  于2022年7月8日周五 19:42写道：

> +1 (binding)
> - built from sources, with JDK11, run a couple of smoke tests
> - verified RAT
> - verified checksums and signatures
> - run some JMS tests using Transactions (the JMS library bundles
> 2.10.x Java client)
>
> Thanks for driving the release!
>
> Enrico
>
> Enrico
>
> Il giorno mer 6 lug 2022 alle ore 10:26 mattison chao
>  ha scritto:
> >
> > This is the second release candidate for Apache Pulsar, version 2.9.3.
> >
> > It fixes the following issues:
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> <
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> >
> >
> > *** Please download, test and vote on this release. This vote will stay
> open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.3-candidate-2/
> >
> > SHA-512 checksums:
> >
> >
> 291eb3f9da234cf38fcd02de781def9a9354025bb4f98c78b160935a6a9c6721cc8280d80b93049656ee5a20e36ddc5d3446b7b034405c07d447833ff65e
> ./apache-pulsar-2.9.3-bin.tar.gz
> >
> >
> d57fa3c8eae1f3ba60422a56288c99a472a671295e41573c884a9d9a71b5fcf622782732e9cfd5128e1b92304b3812cc877675384ac0dbc78109d7efb23681f4
> ./apache-pulsar-2.9.3-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1163/
> >
> > The tag to be voted upon:
> > v2.9.3-candidate-2 (dd9a5f1f91651b634600f66c53dcc6ad855fb669)
> >
> > https://github.com/apache/pulsar/releases/tag/v2.9.3-candidate-2
> >
> > The docker images:
> >
> >
> https://hub.docker.com/layers/248117318/mattison/pulsar/2.9.3-rc-2/images/sha256-a7ac6d5ffb2d77102ca6633313c9d0265c1c89c8b0fe859023fbaf3e0d0a7910?context=repo
> >
> >
> https://hub.docker.com/layers/247907545/mattison/pulsar-all/2.9.3-rc-2/images/sha256-00e6a886a9285107027afb4c3218c9340efb96627100ff2f1c95d1177bd8dbbe?context=repo
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> >
> > Please download the source package, and follow the Release Candidate
> > Validation[1]
> > to validate the release
> >
> > [1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation <
> https://github.com/apache/pulsar/wiki/Release-Candidate-Validation>
>


-- 
BR,
Qiang Huang

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

[Nicolò Boschi]

+1 (non binding)

Checks:
- Checksum and signatures
- Apache Rat check passes
- Compile from source w JDK11
- Build docker image from source
- Run Pulsar standalone and produce-consume from CLI

Thank you!

Nicolò Boschi


Il giorno ven 8 lug 2022 alle ore 13:47 Qiang Huang <
qiang.huang1...@gmail.com> ha scritto:

> +1
>
> Enrico Olivelli  于2022年7月8日周五 19:42写道：
>
> > +1 (binding)
> > - built from sources, with JDK11, run a couple of smoke tests
> > - verified RAT
> > - verified checksums and signatures
> > - run some JMS tests using Transactions (the JMS library bundles
> > 2.10.x Java client)
> >
> > Thanks for driving the release!
> >
> > Enrico
> >
> > Enrico
> >
> > Il giorno mer 6 lug 2022 alle ore 10:26 mattison chao
> >  ha scritto:
> > >
> > > This is the second release candidate for Apache Pulsar, version 2.9.3.
> > >
> > > It fixes the following issues:
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> > <
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> > >
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > open
> > > for at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.3-candidate-2/
> > >
> > > SHA-512 checksums:
> > >
> > >
> >
> 291eb3f9da234cf38fcd02de781def9a9354025bb4f98c78b160935a6a9c6721cc8280d80b93049656ee5a20e36ddc5d3446b7b034405c07d447833ff65e
> > ./apache-pulsar-2.9.3-bin.tar.gz
> > >
> > >
> >
> d57fa3c8eae1f3ba60422a56288c99a472a671295e41573c884a9d9a71b5fcf622782732e9cfd5128e1b92304b3812cc877675384ac0dbc78109d7efb23681f4
> > ./apache-pulsar-2.9.3-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1163/
> > >
> > > The tag to be voted upon:
> > > v2.9.3-candidate-2 (dd9a5f1f91651b634600f66c53dcc6ad855fb669)
> > >
> > > https://github.com/apache/pulsar/releases/tag/v2.9.3-candidate-2
> > >
> > > The docker images:
> > >
> > >
> >
> https://hub.docker.com/layers/248117318/mattison/pulsar/2.9.3-rc-2/images/sha256-a7ac6d5ffb2d77102ca6633313c9d0265c1c89c8b0fe859023fbaf3e0d0a7910?context=repo
> > >
> > >
> >
> https://hub.docker.com/layers/247907545/mattison/pulsar-all/2.9.3-rc-2/images/sha256-00e6a886a9285107027afb4c3218c9340efb96627100ff2f1c95d1177bd8dbbe?context=repo
> > >
> > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> > >
> > > Please download the source package, and follow the Release Candidate
> > > Validation[1]
> > > to validate the release
> > >
> > > [1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
> <
> > https://github.com/apache/pulsar/wiki/Release-Candidate-Validation>
> >
>
>
> --
> BR,
> Qiang Huang
>

[DISCUSS] PIP-184: Topic specific consumer priorityLevel

[Dave Maughan]

Hi Pulsar community,

I've opened a PIP to discuss a new Java client option to allow setting
topic specific consumer priorityLevel.

Proposal Link: https://github.com/apache/pulsar/issues/16481

---

## Motivation

The Pulsar Java consumer supports setting a priority level for priority
message
dispatch in shared subscription consumers and priority assignment in
failover
subscription consumers. See the [ConsumerBuilder.html#priorityLevel(int)
Javadoc](
https://javadoc.io/static/org.apache.pulsar/pulsar-client-api/2.10.1/org/apache/pulsar/client/api/ConsumerBuilder.html#priorityLevel(int)
)
for a detailed functional description. The Pulsar Java consumer also
supports
consuming from multiple topics. However, it is not possible to set a
different
priority level for different topics in the same Consumer instance.

This behaviour is desirable in some use cases. For example, a consumer
processing region specific topics might wish to configure region stickiness
- A
multi-region application might be consuming from topics events-us-east-1 and
events-eu-west-1. Consumers in all regions should be configured to consume
all
topics to ensure data completeness. However, to ensure low latency, the
us-east-1 consumer would need to set a higher priority level for the
us-east-1
topic. Similarly, the eu-west-1 consumer would need to set a higher priority
level for the eu-west-1 topic.

## Goal

Update the Java client API to allow the configuration of different priority
levels for different topics.

Do so in such a way that supports the addition of other topic specific
configuration options or overrides in the future.

Issues will be created to track feature parity in the other client
implementations for this PIP.

## API Changes

In pulsar-client-api, update `ConsumerBuilder` to include two new methods:

```java
public interface ConsumerBuilder extends Cloneable {
...

TopicConsumerBuilder topicConfiguration(String topicNameOrPattern);

ConsumerBuilder topicConfiguration(String topicNameOrPattern,
java.util.function.Consumer>
builderConsumer);
}
```

Create a new interface:

```java
public interface TopicConsumerBuilder {
TopicConsumerBuilder priorityLevel(int priorityLevel);

ConsumerBuilder build();
}
```

In pulsar-client-original, update `ConsumerConfigurationData` to include a
new field:

```java
@Data
public class ConsumerConfigurationData implements Serializable,
Cloneable {
...

private List topicConfigurations = new
ArrayList<>();
}
```

Create a topic configuration class:

```java
@Data
public class TopicConsumerConfigurationData implements Serializable {
private static final long serialVersionUID = 1L;

private String topicNameOrPattern;
private int priorityLevel;

public boolean matchesTopicName(String topicName) {
return
Pattern.compile(topicNameOrPattern).matcher(topicName).matches();
}

public static TopicConsumerConfigurationData of(String
topicNameOrPattern,
ConsumerConfigurationData conf) {
return new TopicConsumerConfigurationData(topicNameOrPattern,
conf.getPriorityLevel());
}
}
```

Then, in `ConsumerImpl` the appropriate topic configuration can be selected
based on the topic being subscribed to. Since the topic configuration is
effectively keyed by a topic name or pattern, it’s possible for the user to
be
able configure multiple topic configurations that match the same concrete
topic
name. In this case the first topic name match should be selected.

```java
TopicConsumerConfigurationData getMatchingTopicConfiguration(String
topicName,
ConsumerConfigurationData conf) {
return topicConfigurations.stream()
.filter(topicConf -> topicConf.matchesTopicName(topicName))
.findFirst()
.orElseGet(() -> TopicConsumerConfigurationData.of(topicName,
conf));
}
```

Example Usage:

```java
pulsarClient.newConsumer()
.topicsPattern("events.*")
.priorityLevel(1)
.topicConfiguration(".*us-east-1", b -> b.priorityLevel(0))
.subscribe();
```

or

```java
pulsarClient.newConsumer()
.topicsPattern("events.*")
.priorityLevel(1)
.topicConfiguration(".*us-east-1")
.priorityLevel(0)
.build()
.subscribe();
```

## Rejected Alternatives

* Extend the existing `ConsumerBuilder` rather than introducing a nested,
topic specific builder class.

Rejection reason: Does not provide a clear API to discover and extend other
topic specific configuration options and overrides.

```java
public interface ConsumerBuilder extends Cloneable {
...

ConsumerBuilder topicPriorityLevel(String topicNameOrPattern, int
priorityLevel);
}
```

Example usage:

```java
pulsarClient.newConsumer()
.topicsPattern("events.*")
.priorityLevel(1)
.topicPriorityLevel(".*us-east-1", 0)
.subscribe();
```

* Provide a configurator interface to configure options and overrides at
runtime

Rejection reason: Not compatible with `ConsumerBuilder.loadConf`.

```java
@Data
clas

Re: [ANNOUNCE] New Committer: Zixuan Liu

[Max Xu]

Congratulations! Zixuan

Best
Max Xu



On Thu, Jul 7, 2022 at 8:55 PM Nicolò Boschi  wrote:

> Congrats!
>
> Nicolò Boschi
>
>
> Il giorno gio 7 lug 2022 alle ore 13:28 Haiting Jiang <
> jianghait...@apache.org> ha scritto:
>
> > Congratulates, Zixuan!
> >
> > BR,
> > Haiting
> >
> > On 2022/07/07 10:03:36 Yu wrote:
> > > Hi team,
> > >
> > > The Project Management Committee (PMC) for Apache Pulsar has invited
> > > Zixuan Liu (https://github.com/nodece) to become a committer
> > > and we are pleased to announce that he has accepted.
> > >
> > > Being a committer enables easier contribution to the
> > > project since there is no need to go via the patch
> > > submission process. This should enable better productivity.
> > >
> > > Welcome and congratulations, Zixuan Liu!
> > >
> > > Please join us in congratulating and welcoming Zixuan Liu onboard!
> > >
> > > Best Regards,
> > > Yu on behalf of the Pulsar PMC
> > >
> >
>

Re: [ANNOUNCE] New Committer: Zixuan Liu

[Qiang Huang]

Congratulations!!! Zixuan.

Max Xu  于2022年7月8日周五 21:36写道：

> Congratulations! Zixuan
>
> Best
> Max Xu
>
>
>
> On Thu, Jul 7, 2022 at 8:55 PM Nicolò Boschi  wrote:
>
> > Congrats!
> >
> > Nicolò Boschi
> >
> >
> > Il giorno gio 7 lug 2022 alle ore 13:28 Haiting Jiang <
> > jianghait...@apache.org> ha scritto:
> >
> > > Congratulates, Zixuan!
> > >
> > > BR,
> > > Haiting
> > >
> > > On 2022/07/07 10:03:36 Yu wrote:
> > > > Hi team,
> > > >
> > > > The Project Management Committee (PMC) for Apache Pulsar has invited
> > > > Zixuan Liu (https://github.com/nodece) to become a committer
> > > > and we are pleased to announce that he has accepted.
> > > >
> > > > Being a committer enables easier contribution to the
> > > > project since there is no need to go via the patch
> > > > submission process. This should enable better productivity.
> > > >
> > > > Welcome and congratulations, Zixuan Liu!
> > > >
> > > > Please join us in congratulating and welcoming Zixuan Liu onboard!
> > > >
> > > > Best Regards,
> > > > Yu on behalf of the Pulsar PMC
> > > >
> > >
> >
>


-- 
BR,
Qiang Huang

Re: [ANNOUNCE] New Committer: Zixuan Liu

[PengHui Li]

Congratulations! Zixuan

Penghui

On Fri, Jul 8, 2022 at 9:56 PM Qiang Huang 
wrote:

> Congratulations!!! Zixuan.
>
> Max Xu  于2022年7月8日周五 21:36写道：
>
> > Congratulations! Zixuan
> >
> > Best
> > Max Xu
> >
> >
> >
> > On Thu, Jul 7, 2022 at 8:55 PM Nicolò Boschi 
> wrote:
> >
> > > Congrats!
> > >
> > > Nicolò Boschi
> > >
> > >
> > > Il giorno gio 7 lug 2022 alle ore 13:28 Haiting Jiang <
> > > jianghait...@apache.org> ha scritto:
> > >
> > > > Congratulates, Zixuan!
> > > >
> > > > BR,
> > > > Haiting
> > > >
> > > > On 2022/07/07 10:03:36 Yu wrote:
> > > > > Hi team,
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Pulsar has
> invited
> > > > > Zixuan Liu (https://github.com/nodece) to become a committer
> > > > > and we are pleased to announce that he has accepted.
> > > > >
> > > > > Being a committer enables easier contribution to the
> > > > > project since there is no need to go via the patch
> > > > > submission process. This should enable better productivity.
> > > > >
> > > > > Welcome and congratulations, Zixuan Liu!
> > > > >
> > > > > Please join us in congratulating and welcoming Zixuan Liu onboard!
> > > > >
> > > > > Best Regards,
> > > > > Yu on behalf of the Pulsar PMC
> > > > >
> > > >
> > >
> >
>
>
> --
> BR,
> Qiang Huang
>

Re: [VOTE] [PIP-182] Provide new load balance placement strategy implementation for ModularLoadManagerStrategy

[PengHui Li]

+1 binding

Penghui

On Fri, Jul 8, 2022 at 3:13 PM Kai Wang  wrote:

> +1 (non-binding)
>
> Thanks,
> Kai
>

Re: [VOTE] Pulsar Release 2.9.3 Candidate 2

[PengHui Li]

+1 binding

- checked the signature
- run standalone and test produce/consume
- verified function and stateful function
- verified the Cassandra connector

Thanks,
Penghui

On Fri, Jul 8, 2022 at 8:16 PM Nicolò Boschi  wrote:

> +1 (non binding)
>
> Checks:
> - Checksum and signatures
> - Apache Rat check passes
> - Compile from source w JDK11
> - Build docker image from source
> - Run Pulsar standalone and produce-consume from CLI
>
> Thank you!
>
> Nicolò Boschi
>
>
> Il giorno ven 8 lug 2022 alle ore 13:47 Qiang Huang <
> qiang.huang1...@gmail.com> ha scritto:
>
> > +1
> >
> > Enrico Olivelli  于2022年7月8日周五 19:42写道：
> >
> > > +1 (binding)
> > > - built from sources, with JDK11, run a couple of smoke tests
> > > - verified RAT
> > > - verified checksums and signatures
> > > - run some JMS tests using Transactions (the JMS library bundles
> > > 2.10.x Java client)
> > >
> > > Thanks for driving the release!
> > >
> > > Enrico
> > >
> > > Enrico
> > >
> > > Il giorno mer 6 lug 2022 alle ore 10:26 mattison chao
> > >  ha scritto:
> > > >
> > > > This is the second release candidate for Apache Pulsar, version
> 2.9.3.
> > > >
> > > > It fixes the following issues:
> > > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> > > <
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+
> > > >
> > > >
> > > > *** Please download, test and vote on this release. This vote will
> stay
> > > open
> > > > for at least 72 hours ***
> > > >
> > > > Note that we are voting upon the source (tag), binaries are provided
> > for
> > > > convenience.
> > > >
> > > > Source and binary files:
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.3-candidate-2/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> > >
> >
> 291eb3f9da234cf38fcd02de781def9a9354025bb4f98c78b160935a6a9c6721cc8280d80b93049656ee5a20e36ddc5d3446b7b034405c07d447833ff65e
> > > ./apache-pulsar-2.9.3-bin.tar.gz
> > > >
> > > >
> > >
> >
> d57fa3c8eae1f3ba60422a56288c99a472a671295e41573c884a9d9a71b5fcf622782732e9cfd5128e1b92304b3812cc877675384ac0dbc78109d7efb23681f4
> > > ./apache-pulsar-2.9.3-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1163/
> > > >
> > > > The tag to be voted upon:
> > > > v2.9.3-candidate-2 (dd9a5f1f91651b634600f66c53dcc6ad855fb669)
> > > >
> > > > https://github.com/apache/pulsar/releases/tag/v2.9.3-candidate-2
> > > >
> > > > The docker images:
> > > >
> > > >
> > >
> >
> https://hub.docker.com/layers/248117318/mattison/pulsar/2.9.3-rc-2/images/sha256-a7ac6d5ffb2d77102ca6633313c9d0265c1c89c8b0fe859023fbaf3e0d0a7910?context=repo
> > > >
> > > >
> > >
> >
> https://hub.docker.com/layers/247907545/mattison/pulsar-all/2.9.3-rc-2/images/sha256-00e6a886a9285107027afb4c3218c9340efb96627100ff2f1c95d1177bd8dbbe?context=repo
> > > >
> > > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> > > >
> > > > Please download the source package, and follow the Release Candidate
> > > > Validation[1]
> > > > to validate the release
> > > >
> > > > [1]
> https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
> > <
> > > https://github.com/apache/pulsar/wiki/Release-Candidate-Validation>
> > >
> >
> >
> > --
> > BR,
> > Qiang Huang
> >
>

Re: [VOTE] [PIP-182] Provide new load balance placement strategy implementation for ModularLoadManagerStrategy

[Baodi Shi]

+1 (non-binding)

Thanks,
Baodi Shi

> On Jul 8, 2022, at 15:1235, Kai Wang  wrote:
> 
> +1 (non-binding)

Re: [DISCUSS] PIP-184: Topic specific consumer priorityLevel

[Enrico Olivelli]

Dave,
Why can't you create multiple independent Consumers ?
They will share the same resources (memory pools, thread pools)




Enrico

Il giorno ven 8 lug 2022 alle ore 15:00 Dave Maughan
 ha scritto:
>
> Hi Pulsar community,
>
> I've opened a PIP to discuss a new Java client option to allow setting
> topic specific consumer priorityLevel.
>
> Proposal Link: https://github.com/apache/pulsar/issues/16481
>
> ---
>
> ## Motivation
>
> The Pulsar Java consumer supports setting a priority level for priority
> message
> dispatch in shared subscription consumers and priority assignment in
> failover
> subscription consumers. See the [ConsumerBuilder.html#priorityLevel(int)
> Javadoc](
> https://javadoc.io/static/org.apache.pulsar/pulsar-client-api/2.10.1/org/apache/pulsar/client/api/ConsumerBuilder.html#priorityLevel(int)
> )
> for a detailed functional description. The Pulsar Java consumer also
> supports
> consuming from multiple topics. However, it is not possible to set a
> different
> priority level for different topics in the same Consumer instance.
>
> This behaviour is desirable in some use cases. For example, a consumer
> processing region specific topics might wish to configure region stickiness
> - A
> multi-region application might be consuming from topics events-us-east-1 and
> events-eu-west-1. Consumers in all regions should be configured to consume
> all
> topics to ensure data completeness. However, to ensure low latency, the
> us-east-1 consumer would need to set a higher priority level for the
> us-east-1
> topic. Similarly, the eu-west-1 consumer would need to set a higher priority
> level for the eu-west-1 topic.
>
> ## Goal
>
> Update the Java client API to allow the configuration of different priority
> levels for different topics.
>
> Do so in such a way that supports the addition of other topic specific
> configuration options or overrides in the future.
>
> Issues will be created to track feature parity in the other client
> implementations for this PIP.
>
> ## API Changes
>
> In pulsar-client-api, update `ConsumerBuilder` to include two new methods:
>
> ```java
> public interface ConsumerBuilder extends Cloneable {
> ...
>
> TopicConsumerBuilder topicConfiguration(String topicNameOrPattern);
>
> ConsumerBuilder topicConfiguration(String topicNameOrPattern,
> java.util.function.Consumer>
> builderConsumer);
> }
> ```
>
> Create a new interface:
>
> ```java
> public interface TopicConsumerBuilder {
> TopicConsumerBuilder priorityLevel(int priorityLevel);
>
> ConsumerBuilder build();
> }
> ```
>
> In pulsar-client-original, update `ConsumerConfigurationData` to include a
> new field:
>
> ```java
> @Data
> public class ConsumerConfigurationData implements Serializable,
> Cloneable {
> ...
>
> private List topicConfigurations = new
> ArrayList<>();
> }
> ```
>
> Create a topic configuration class:
>
> ```java
> @Data
> public class TopicConsumerConfigurationData implements Serializable {
> private static final long serialVersionUID = 1L;
>
> private String topicNameOrPattern;
> private int priorityLevel;
>
> public boolean matchesTopicName(String topicName) {
> return
> Pattern.compile(topicNameOrPattern).matcher(topicName).matches();
> }
>
> public static TopicConsumerConfigurationData of(String
> topicNameOrPattern,
> ConsumerConfigurationData conf) {
> return new TopicConsumerConfigurationData(topicNameOrPattern,
> conf.getPriorityLevel());
> }
> }
> ```
>
> Then, in `ConsumerImpl` the appropriate topic configuration can be selected
> based on the topic being subscribed to. Since the topic configuration is
> effectively keyed by a topic name or pattern, it’s possible for the user to
> be
> able configure multiple topic configurations that match the same concrete
> topic
> name. In this case the first topic name match should be selected.
>
> ```java
> TopicConsumerConfigurationData getMatchingTopicConfiguration(String
> topicName,
> ConsumerConfigurationData conf) {
> return topicConfigurations.stream()
> .filter(topicConf -> topicConf.matchesTopicName(topicName))
> .findFirst()
> .orElseGet(() -> TopicConsumerConfigurationData.of(topicName,
> conf));
> }
> ```
>
> Example Usage:
>
> ```java
> pulsarClient.newConsumer()
> .topicsPattern("events.*")
> .priorityLevel(1)
> .topicConfiguration(".*us-east-1", b -> b.priorityLevel(0))
> .subscribe();
> ```
>
> or
>
> ```java
> pulsarClient.newConsumer()
> .topicsPattern("events.*")
> .priorityLevel(1)
> .topicConfiguration(".*us-east-1")
> .priorityLevel(0)
> .build()
> .subscribe();
> ```
>
> ## Rejected Alternatives
>
> * Extend the existing `ConsumerBuilder` rather than introducing a nested,
> topic specific builder class.
>
> Rejection reason: Does not provide a clear API to discover and extend other
> topic specific configuration options and overrides.
>
> ```ja

Re: [DISCUSS] PIP-184: Topic specific consumer priorityLevel

[Dave Maughan]

Hi Enrico,

Why can't you create multiple independent Consumers ?
> They will share the same resources (memory pools, thread pools)


You can do that but it means the user has to manage the consumption from
each of the consumer instances manually. This is already solved in the
existing multi topic consumer. This change adds user convenience - to
continue consuming from multiple topics in a single consumer instance, but
allowing them to customise the configuration.

- Dave

On Fri, Jul 8, 2022 at 4:26 PM Enrico Olivelli  wrote:

> Dave,
> Why can't you create multiple independent Consumers ?
> They will share the same resources (memory pools, thread pools)
>
>
>
>
> Enrico
>
> Il giorno ven 8 lug 2022 alle ore 15:00 Dave Maughan
>  ha scritto:
> >
> > Hi Pulsar community,
> >
> > I've opened a PIP to discuss a new Java client option to allow setting
> > topic specific consumer priorityLevel.
> >
> > Proposal Link: https://github.com/apache/pulsar/issues/16481
> >
> > ---
> >
> > ## Motivation
> >
> > The Pulsar Java consumer supports setting a priority level for priority
> > message
> > dispatch in shared subscription consumers and priority assignment in
> > failover
> > subscription consumers. See the [ConsumerBuilder.html#priorityLevel(int)
> > Javadoc](
> >
> https://javadoc.io/static/org.apache.pulsar/pulsar-client-api/2.10.1/org/apache/pulsar/client/api/ConsumerBuilder.html#priorityLevel(int)
> > )
> > for a detailed functional description. The Pulsar Java consumer also
> > supports
> > consuming from multiple topics. However, it is not possible to set a
> > different
> > priority level for different topics in the same Consumer instance.
> >
> > This behaviour is desirable in some use cases. For example, a consumer
> > processing region specific topics might wish to configure region
> stickiness
> > - A
> > multi-region application might be consuming from topics events-us-east-1
> and
> > events-eu-west-1. Consumers in all regions should be configured to
> consume
> > all
> > topics to ensure data completeness. However, to ensure low latency, the
> > us-east-1 consumer would need to set a higher priority level for the
> > us-east-1
> > topic. Similarly, the eu-west-1 consumer would need to set a higher
> priority
> > level for the eu-west-1 topic.
> >
> > ## Goal
> >
> > Update the Java client API to allow the configuration of different
> priority
> > levels for different topics.
> >
> > Do so in such a way that supports the addition of other topic specific
> > configuration options or overrides in the future.
> >
> > Issues will be created to track feature parity in the other client
> > implementations for this PIP.
> >
> > ## API Changes
> >
> > In pulsar-client-api, update `ConsumerBuilder` to include two new
> methods:
> >
> > ```java
> > public interface ConsumerBuilder extends Cloneable {
> > ...
> >
> > TopicConsumerBuilder topicConfiguration(String
> topicNameOrPattern);
> >
> > ConsumerBuilder topicConfiguration(String topicNameOrPattern,
> > java.util.function.Consumer>
> > builderConsumer);
> > }
> > ```
> >
> > Create a new interface:
> >
> > ```java
> > public interface TopicConsumerBuilder {
> > TopicConsumerBuilder priorityLevel(int priorityLevel);
> >
> > ConsumerBuilder build();
> > }
> > ```
> >
> > In pulsar-client-original, update `ConsumerConfigurationData` to include
> a
> > new field:
> >
> > ```java
> > @Data
> > public class ConsumerConfigurationData implements Serializable,
> > Cloneable {
> > ...
> >
> > private List topicConfigurations =
> new
> > ArrayList<>();
> > }
> > ```
> >
> > Create a topic configuration class:
> >
> > ```java
> > @Data
> > public class TopicConsumerConfigurationData implements Serializable {
> > private static final long serialVersionUID = 1L;
> >
> > private String topicNameOrPattern;
> > private int priorityLevel;
> >
> > public boolean matchesTopicName(String topicName) {
> > return
> > Pattern.compile(topicNameOrPattern).matcher(topicName).matches();
> > }
> >
> > public static TopicConsumerConfigurationData of(String
> > topicNameOrPattern,
> > ConsumerConfigurationData conf) {
> > return new TopicConsumerConfigurationData(topicNameOrPattern,
> > conf.getPriorityLevel());
> > }
> > }
> > ```
> >
> > Then, in `ConsumerImpl` the appropriate topic configuration can be
> selected
> > based on the topic being subscribed to. Since the topic configuration is
> > effectively keyed by a topic name or pattern, it’s possible for the user
> to
> > be
> > able configure multiple topic configurations that match the same concrete
> > topic
> > name. In this case the first topic name match should be selected.
> >
> > ```java
> > TopicConsumerConfigurationData getMatchingTopicConfiguration(String
> > topicName,
> > ConsumerConfigurationData conf) {
> > return topicConfigurations.stream()
> > .filter(topicConf -> topicConf.matchesTopicName(topicNam

Re: [DISCUSS] Enable GitHub Discussions?

[Dave Fisher]

Hi -

If we add GitHub Discussions then I think that dev@ should be informed when a 
Discussion is started and closed while commits@ should get the comments. If we 
decide to add an issues@ mailing list then we need two volunteers for mailing 
list moderation.

https://infra.apache.org/mailing-list-moderation.html

I already moderate a large number of mailing lists. Mostly you will simply 
ignore some regular spammy phishing attacks.

Regards,
Dave

> On Jun 28, 2022, at 9:13 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> Now that the ASF has a notifier on GitHub Discussions I have no objection to 
> using discussions as long as these are visible on dev@pulsar.apache.org 
>  mailing list.
> 
>> From the previous thread it seems that the Pulsar community has already
>> multiple channels to catch up for contributors, while I only watch at
>> mailing list and GitHub issues & PRs
> 
> I think that where the notifications are sent is important. Pulsar 
> contributors are supposed to be watching dev@pulsar.apache.org 
>  and this should be the mailing list where 
> discussions are visible to the community. I recommend that discussion 
> notifications be sent there.
> 
>> Besides, currently dev@ is full of Git notifications while we may sort them
>> out to issues@ as in Apache Kvrocks[5].
> 
> Regarding other notifications: the project is inconsistent. Also, please note 
> that Pulsar does not have an issues@pulsar mailing list.
> 
> The main repository is using this default: 
> https://gitbox.apache.org/schemes.cgi?pulsar 
>  which differs from 
> https://gitbox.apache.org/schemes.cgi?pulsar-site 
> 
> 
> The overall notification scheme change is a new discussion which must be kept 
> separate.
> 
> Regards,
> Dave
> 
> 
>> On Jun 25, 2022, at 12:31 PM, tison  wrote:
>> 
>> Hi,
>> 
>> There is a previous discussion at
>> https://lists.apache.org/thread/83pst643h9cqcryo3zsjd240jmqzvn73.
>> 
>> I'd like to bump this thread since INFRA has implemented forward GitHub
>> Discussions activities to mailing list[1][2][3].
>> 
>> It may be a proper time we revisit this topic. My major argument is:
>> 
>>> GitHub Discussion is friendly for GitHub users and lower the bar to
>> participant in discussions. If we can sync all activities to mailing list,
>> it should be a nice supplement.
>> 
>> You may take a look at Apache SkyWalking's practice[4] where it holds an
>> easy-to-find entrypoint for participants while keeps all decisions in
>> mailing list - VOTE and RESULT threads should happen on mailing list as it
>> used to be.
>> 
>> At least, it can be a supplement of users@ with a Q&A category.
>> 
>> From the previous thread it seems that the Pulsar community has already
>> multiple channels to catch up for contributors, while I only watch at
>> mailing list and GitHub issues & PRs. If you find other channel as source
>> of truth, I'm glad to learn and see whether we can keep as less source of
>> truth as possible - ideally, single source (orthogonal sources) of truth.
>> 
>> Besides, currently dev@ is full of Git notifications while we may sort them
>> out to issues@ as in Apache Kvrocks[5].
>> 
>> Best,
>> tison.
>> 
>> [1] https://github.com/apache/infrastructure-p6/pull/1120
>> [2] https://github.com/apache/infrastructure-github-discussions-notifier/
>> [3]
>> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
>> [4] https://github.com/apache/skywalking/discussions
>> [5]
>> https://github.com/apache/incubator-kvrocks/blob/dde438f04c577050e299cce981a17018f056c3b3/.asf.yaml#L46-L50
> 

[DISCUSSION] Improvements to Release Process Management

[Dave Fisher]

Hi -

We need to tighten up our procedures around releases. There are several issues.

1. Maintaining the official KEYS file - 
https://dist.apache.org/repos/dist/release/pulsar/KEYS

During the pulsar-manager-0.3.0 release the KEYS were not updated from 
https://dist.apache.org/repos/dist/dev/pulsar/KEYS This was flagged by ASF 
Infra and I’ve updated the KEYS file to contain both urfree’s and 
mattisonchao’s keys. (We should be good for 2.9.3)

I suggest that we delete https://dist.apache.org/repos/dist/dev/pulsar/KEYS and 
only use the official https://dist.apache.org/repos/dist/release/pulsar/KEYS in 
all cases. We will need to rewrite our release docs.

2, We often leave old releases in the distribution directory. I’ve cleaned 
these up, but we need to make sure that this is documented for everything that 
is officially released.

./pulsar-client-node/pulsar-client-node-1.6.2
./pulsar-2.10.1
./pulsar-2.10.1/connectors
./pulsar-2.10.1/RPMS
./pulsar-2.10.1/RPMS/repodata
./pulsar-2.10.1/DEB
./pulsar-2.9.2
./pulsar-2.9.2/connectors
./pulsar-2.9.2/RPMS
./pulsar-2.9.2/RPMS/repodata
./pulsar-2.9.2/DEB
./pulsar-adapters-2.8.0
./pulsar-client-go-0.8.1
./pulsar-manager/pulsar-manager-0.3.0
./pulsar-2.8.3
./pulsar-2.8.3/connectors
./pulsar-2.8.3/RPMS
./pulsar-2.8.3/RPMS/repodata
./pulsar-2.8.3/DEB

3. Pulsar 2.7.4 was removed from the Release distribution on January 20, 2022. 
Did we announce the EOL of 2.7.x? I don’t recall, but it’s easy to miss 
activity.

4. If the Apache Pulsar Helm Chart and Apache Pulsar Docker Images are intended 
to be official convenience releases then they must be included into 
https://dist.apache.org/repos/dist/release/pulsar/.

a) The Helm Chart is not under any ASF process and there needs to be a whole 
separate discussion about properly handling it.

b) What is the deal with the docker images? What is the current process? Why 
can’t we add them in the release repository where anyone can downstream them to 
a convenient location.

All The Best,
Dave

Re: [ANNOUNCE] New Committer: Zixuan Liu

[Zike Yang]

Congratulations! Zixuan

Zike Yang

On Fri, Jul 8, 2022 at 10:47 PM PengHui Li  wrote:

> Congratulations! Zixuan
>
> Penghui
>
> On Fri, Jul 8, 2022 at 9:56 PM Qiang Huang 
> wrote:
>
> > Congratulations!!! Zixuan.
> >
> > Max Xu  于2022年7月8日周五 21:36写道：
> >
> > > Congratulations! Zixuan
> > >
> > > Best
> > > Max Xu
> > >
> > >
> > >
> > > On Thu, Jul 7, 2022 at 8:55 PM Nicolò Boschi 
> > wrote:
> > >
> > > > Congrats!
> > > >
> > > > Nicolò Boschi
> > > >
> > > >
> > > > Il giorno gio 7 lug 2022 alle ore 13:28 Haiting Jiang <
> > > > jianghait...@apache.org> ha scritto:
> > > >
> > > > > Congratulates, Zixuan!
> > > > >
> > > > > BR,
> > > > > Haiting
> > > > >
> > > > > On 2022/07/07 10:03:36 Yu wrote:
> > > > > > Hi team,
> > > > > >
> > > > > > The Project Management Committee (PMC) for Apache Pulsar has
> > invited
> > > > > > Zixuan Liu (https://github.com/nodece) to become a committer
> > > > > > and we are pleased to announce that he has accepted.
> > > > > >
> > > > > > Being a committer enables easier contribution to the
> > > > > > project since there is no need to go via the patch
> > > > > > submission process. This should enable better productivity.
> > > > > >
> > > > > > Welcome and congratulations, Zixuan Liu!
> > > > > >
> > > > > > Please join us in congratulating and welcoming Zixuan Liu
> onboard!
> > > > > >
> > > > > > Best Regards,
> > > > > > Yu on behalf of the Pulsar PMC
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > BR,
> > Qiang Huang
> >
>

[GitHub] [pulsar-site] michaeljmarshall merged pull request #133: Only generate Javadocs for released versions of Pulsar

[GitBox]

michaeljmarshall merged PR #133:
URL: https://github.com/apache/pulsar-site/pull/133


-- 
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: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSSION] Improvements to Release Process Management

[Michael Marshall]

Hi Dave,

Thank you for helping to bring us into compliance on these procedures.

> I suggest that we delete https://dist.apache.org/repos/dist/dev/pulsar/KEYS 
> and only use the official 
> https://dist.apache.org/repos/dist/release/pulsar/KEYS in all cases. We will 
> need to rewrite our release docs.

It seems easier to have a single KEYS file.

Regarding 2, I think we're missing the python client distribution. It
is currently hosted and distributed via pypi:
https://pypi.org/project/pulsar-client. Is it supposed to be hosted
https://dist.apache.org/repos/dist/release/pulsar/ as well?

> 3. Pulsar 2.7.4 was removed from the Release distribution on January 20, 
> 2022. Did we announce the EOL of 2.7.x? I don’t recall, but it’s easy to miss 
> activity.

Release line 2.7 has not been declared EOL. That is worth a separate
discussion. Our current PIP 47 indicates that it could (should?) be
EOL since it was released in December 2020 and has had 4 patch
releases. We started a 2.7.5 release, but it stopped with a single
failed RC (see 
https://lists.apache.org/thread/j7y82x98x3zlo1m5b1lc7ljy54p8zl8v).

> 4. If the Apache Pulsar Helm Chart and Apache Pulsar Docker Images are 
> intended to be official convenience releases then they must be included into 
> https://dist.apache.org/repos/dist/release/pulsar/.

I agree that we should host them here.

> a) The Helm Chart is not under any ASF process and there needs to be a whole 
> separate discussion about properly handling it.

I started research on a release process for the helm chart a couple
weeks ago, and distributing it via
https://dist.apache.org/repos/dist/release/pulsar/ will be easy to
implement, but I haven't had a chance to work through all of the
changes yet.

We currently host the index.yaml file on the Pulsar website
(https://pulsar.apache.org/charts/index.yaml), and that index points
helm to download the actual helm chart tarballs from github, as you
can see in the index.yaml.

Here is our documentation on adding the helm repo
(https://github.com/apache/pulsar-helm-chart/#add-to-local-helm-repository).
This essentially points helm to the index.yaml, which helm uses to
discover dependencies. Given that we have the general downloads page
on the pulsar website, I think it seems to leave this index.yaml on
the pulsar website.

> b) What is the deal with the docker images? What is the current process? Why 
> can’t we add them in the release repository where anyone can downstream them 
> to a convenient location.

The current process is to build the docker images on a committer's
machine, and then push it to docker hub. The `apachepulsar` DockerHub
account has a limited number of accounts, so only certain committers
can push to the repo. As an alternative to hosting the image in the
release repository, I wonder why we don't distribute our docker images
via the Apache repo: https://hub.docker.com/u/apache. That repo is a
member of the Docker OSS Program
(https://www.docker.com/community/open-source/application/). The
program removes the Docker Hub rate limiting on downloads, which could
be a great win for our users. The Apache Bookkeeper docker image is
already stored in the apache repo
(https://hub.docker.com/r/apache/bookkeeper).

Thanks,
Michael

On Fri, Jul 8, 2022 at 2:04 PM Dave Fisher  wrote:
>
> Hi -
>
> We need to tighten up our procedures around releases. There are several 
> issues.
>
> 1. Maintaining the official KEYS file - 
> https://dist.apache.org/repos/dist/release/pulsar/KEYS
>
> During the pulsar-manager-0.3.0 release the KEYS were not updated from 
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS This was flagged by ASF 
> Infra and I’ve updated the KEYS file to contain both urfree’s and 
> mattisonchao’s keys. (We should be good for 2.9.3)
>
> I suggest that we delete https://dist.apache.org/repos/dist/dev/pulsar/KEYS 
> and only use the official 
> https://dist.apache.org/repos/dist/release/pulsar/KEYS in all cases. We will 
> need to rewrite our release docs.
>
> 2, We often leave old releases in the distribution directory. I’ve cleaned 
> these up, but we need to make sure that this is documented for everything 
> that is officially released.
>
> ./pulsar-client-node/pulsar-client-node-1.6.2
> ./pulsar-2.10.1
> ./pulsar-2.10.1/connectors
> ./pulsar-2.10.1/RPMS
> ./pulsar-2.10.1/RPMS/repodata
> ./pulsar-2.10.1/DEB
> ./pulsar-2.9.2
> ./pulsar-2.9.2/connectors
> ./pulsar-2.9.2/RPMS
> ./pulsar-2.9.2/RPMS/repodata
> ./pulsar-2.9.2/DEB
> ./pulsar-adapters-2.8.0
> ./pulsar-client-go-0.8.1
> ./pulsar-manager/pulsar-manager-0.3.0
> ./pulsar-2.8.3
> ./pulsar-2.8.3/connectors
> ./pulsar-2.8.3/RPMS
> ./pulsar-2.8.3/RPMS/repodata
> ./pulsar-2.8.3/DEB
>
> 3. Pulsar 2.7.4 was removed from the Release distribution on January 20, 
> 2022. Did we announce the EOL of 2.7.x? I don’t recall, but it’s easy to miss 
> activity.
>
> 4. If the Apache Pulsar Helm Chart and Apache Pulsar Docker Images are 
> intended to be official convenience releases

[GitHub] [pulsar-test-infra] michaeljmarshall merged pull request #54: [pulsarbot] trim whitespaces in comments

[GitBox]

michaeljmarshall merged PR #54:
URL: https://github.com/apache/pulsar-test-infra/pull/54


-- 
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: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org