lhotari merged pull request #189:
URL: https://github.com/apache/pulsar-helm-chart/pull/189
--
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-un
thomasechen commented on pull request #161:
URL:
https://github.com/apache/pulsar-helm-chart/pull/161#issuecomment-1002887755
Pulasr 2.9.1 was released, could we have the helm that support these two
releases?
--
This is an automated message from the Apache Git Service.
To respond to the
Technoboy- commented on a change in pull request #189:
URL: https://github.com/apache/pulsar-helm-chart/pull/189#discussion_r776559787
##
File path: charts/pulsar/Chart.yaml
##
@@ -18,7 +18,7 @@
#
apiVersion: v1
-appVersion: "2.7.2"
+appVersion: "2.7.4"
description: Apache
Technoboy- commented on a change in pull request #189:
URL: https://github.com/apache/pulsar-helm-chart/pull/189#discussion_r776559018
##
File path: charts/pulsar/Chart.yaml
##
@@ -18,7 +18,7 @@
#
apiVersion: v1
-appVersion: "2.7.2"
+appVersion: "2.7.4"
description: Apache
Hi All,
We have a usecase for pulsar with spark streaming and for the same I was
looking at the pulsar-spark receiver (SparkStreamingPulsarReceiver.java).
This does not provide features like reliability, ratelimit, backpressure
considerations, pulsar message metadata, etc. Hence I ended up writin
Thanks reply, `terminate the topic` is useful
> 2021年12月29日 11:3113，PengHui Li 写道：
>
> What is the background of the requirement?
> Usually, we will not force to close the producer and consumer at the
> server-side,
> because we don't if the client-side can handle this case well.
>
> Or, if the
aditiwari01 commented on a change in pull request #31:
URL: https://github.com/apache/pulsar-adapters/pull/31#discussion_r776248456
##
File path:
pulsar-spark/src/main/scala/org/apache/pulsar/spark/SparkStreamingReliablePulsarReceiver.scala
##
@@ -0,0 +1,158 @@
+package org.ap
qq516249940 commented on issue #23:
URL:
https://github.com/apache/pulsar-helm-chart/issues/23#issuecomment-1002485188
in china how to use prepare_helm_release.sh ？？？
```bash
curl: (7) Failed to connect to raw.githubusercontent.com port 443: 拒绝连接
generate the token for admin
Ge
lhotari commented on a change in pull request #189:
URL: https://github.com/apache/pulsar-helm-chart/pull/189#discussion_r776227429
##
File path: charts/pulsar/Chart.yaml
##
@@ -18,7 +18,7 @@
#
apiVersion: v1
-appVersion: "2.7.2"
+appVersion: "2.7.4"
description: Apache Pu
