Hello,
How are you?
We have created a PIP.
PIP 92: Topic policy across multiple clusters
https://github.com/apache/pulsar/wiki/PIP-93%3A-Transaction-performance-tools
If you have any suggestions or ideas about this PIP, please discuss it
in this email
Thanks,
Bo Cong
k2la commented on issue #171:
URL:
https://github.com/apache/pulsar-client-node/issues/171#issuecomment-915795647
@alphara
We don't have no plans to implement native Node.js client at the moment.
There is a third party native Node.js Client called pulsar-flex.
https://github.c
Enrico, my initial comment when you brought up PH was in relation to the
larger question about proxying, rather than looking at this in a limited
fashion on how to make it easy to add new PH in the proxy.
But specifically with this, here are my comments. Two very
distinct abstractions are being
tuteng merged pull request #414:
URL: https://github.com/apache/pulsar-manager/pull/414
--
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-unsubs
tuteng closed issue #413:
URL: https://github.com/apache/pulsar-manager/issues/413
--
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...
beyondyinjl2 opened a new issue #418:
URL: https://github.com/apache/pulsar-manager/issues/418
Implemented a custom plug-in in pulsar, how to pass the certification in
pulsar-manager
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
Pulsar community:
As discussed on this thread (1), my team offered to develop new website
design concepts for the community that we would implement in collaboration
with others on that thread. We are pleased to share three concepts for your
consideration below.
Notes:
* This vote is for overall d
frankjkelly commented on pull request #159:
URL: https://github.com/apache/pulsar-helm-chart/pull/159#issuecomment-915497785
FYI closing this in favor of another PR #162
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
frankjkelly opened a new pull request #162:
URL: https://github.com/apache/pulsar-helm-chart/pull/162
Fixes #152
### Motivation
Support prefix in front of port names to abide by Istio protocol rules
### Modifications
Support adding a prefix
- pulsar -> tcp-pul
Resurrecting this thread. Two points to make:
First, it's completely fine for Apache projects to add someone as a
committer to maintain a specific part of the tree, and I believe Pulsar has
already done this for the .NET driver. So if we agree in principle that a
protocol handler or other piece
frankjkelly commented on a change in pull request #159:
URL: https://github.com/apache/pulsar-helm-chart/pull/159#discussion_r704418961
##
File path: charts/pulsar/templates/bookkeeper-service.yaml
##
@@ -33,7 +33,7 @@ metadata:
spec:
ports:
- name: bookie
-port: {{
lhotari commented on a change in pull request #159:
URL: https://github.com/apache/pulsar-helm-chart/pull/159#discussion_r704344911
##
File path: charts/pulsar/templates/bookkeeper-service.yaml
##
@@ -33,7 +33,7 @@ metadata:
spec:
ports:
- name: bookie
-port: {{ .Val
lhotari commented on a change in pull request #159:
URL: https://github.com/apache/pulsar-helm-chart/pull/159#discussion_r704343805
##
File path: charts/pulsar/templates/bookkeeper-service.yaml
##
@@ -33,7 +33,7 @@ metadata:
spec:
ports:
- name: bookie
-port: {{ .Val
lhotari commented on a change in pull request #159:
URL: https://github.com/apache/pulsar-helm-chart/pull/159#discussion_r704342473
##
File path: charts/pulsar/templates/bookkeeper-service.yaml
##
@@ -33,7 +33,7 @@ metadata:
spec:
ports:
- name: bookie
-port: {{ .Val
Thanks for the feedback.
> Why not take more time to develop the project and get the project into a
more mature stage first? There is no harm to develop the project in that
way.
Yes, that's what I'm planning to do. The plan is to move the project to
https://github.com/datastax/reactive-pulsar and
It seems that there are already interests in contributing to the project.
Why not take more time to develop the project and get the project into a
more mature stage first? There is no harm to develop the project in that
way.
- Sijie
On Thu, Sep 2, 2021 at 12:06 AM Lari Hotari wrote:
> On Thu, S
On Fri, Sep 3, 2021 at 5:07 AM Enrico Olivelli wrote:
> Sijie,
> Thanks for your questions, answers inline below.
>
> Il giorno gio 2 set 2021 alle ore 02:23 Sijie Guo ha
> scritto:
>
> > I would like to see the clarification between the broker protocol
> handlers
> > and proxy protocol handlers
bulolo opened a new issue #174:
URL: https://github.com/apache/pulsar-client-node/issues/174
i want to retry if the message is not ack or have error.
i find enableRetry in java version
but i did not find in node
is there any idea to retry msg
--
This is an automated message from
sijie commented on a change in pull request #159:
URL: https://github.com/apache/pulsar-helm-chart/pull/159#discussion_r704185333
##
File path: charts/pulsar/templates/bookkeeper-service.yaml
##
@@ -33,7 +33,7 @@ metadata:
spec:
ports:
- name: bookie
-port: {{ .Value
hangc0276 opened a new pull request #161:
URL: https://github.com/apache/pulsar-helm-chart/pull/161
### Motivation
Currently, Pulsar 2.8.1 has been released, we can update the pulsar version
in helm chart.
### Modifications
1. Bump Pulsar version to 2.8.1
### Verifying t
> I also share this problem, because if you want to efficiently implement
> message filtering you need to do it in the broker side.
>
> I am not sure that making the full Dispatcher pluggable is a good idea,
> because the code is too complex and also
> it really depends on the internals of the B
21 matches
Mail list logo
