sijie opened a new pull request #1:
URL: https://github.com/apache/pulsar-connectors/pull/1
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 t
eolivelli commented on pull request #1:
URL: https://github.com/apache/pulsar-connectors/pull/1#issuecomment-725327145
@sijie it is not clear to me which version of Pulsar we are using for tests.
`image: apachepulsar/pulsar-build:latest`
what does this tag mean ?
Probably it wou
Hi everyone,
Please review and vote on the release candidate #1 for the version 0.3.0, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This is the first release candidate for Apache Pulsar Go client, version 0.3.0.
It fixes the follo
Hi all,
After taking a deeper look at Confluent's benchmark, we noticed a number of
issues with the setup, framework, and methodology. Penghui Li fixed those
issues, reran this benchmark in order to provide knowledge, insights, and
transparency into Pulsar’s true performance capabilities. In additi
sijie merged pull request #2:
URL: https://github.com/apache/pulsar-adapters/pull/2
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
sijie commented on pull request #1:
URL: https://github.com/apache/pulsar-connectors/pull/1#issuecomment-725539224
@eolivelli `apachepulsar/pulsar-build:latest` is not a test image. It is a
build image for building pulsar release.
--
eolivelli commented on pull request #1:
URL: https://github.com/apache/pulsar-connectors/pull/1#issuecomment-725540938
```
name: Clone Pulsar
uses: actions/checkout@v2
with:
fetch-depth: 1
repository: apache/pulsar
ref: master
sijie merged pull request #76:
URL: https://github.com/apache/pulsar-helm-chart/pull/76
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
sijie commented on a change in pull request #80:
URL: https://github.com/apache/pulsar-helm-chart/pull/80#discussion_r521568693
##
File path: charts/pulsar/templates/bookkeeper-configmap.yaml
##
@@ -22,7 +22,7 @@ apiVersion: v1
kind: ConfigMap
metadata:
name: "{{ template
sijie commented on pull request #80:
URL: https://github.com/apache/pulsar-helm-chart/pull/80#issuecomment-725598100
regarding the CI, can you rebase your pull request to latest master to
include the fix in #76 ?
This is an
sijie commented on pull request #81:
URL: https://github.com/apache/pulsar-helm-chart/pull/81#issuecomment-725598386
@wolfstudy Can you rebase the pull request to latest master to include the
fix in #76 ?
This is an automate
jeantil commented on a change in pull request #80:
URL: https://github.com/apache/pulsar-helm-chart/pull/80#discussion_r521587737
##
File path: charts/pulsar/templates/bookkeeper-configmap.yaml
##
@@ -22,7 +22,7 @@ apiVersion: v1
kind: ConfigMap
metadata:
name: "{{ templat
jeantil commented on pull request #80:
URL: https://github.com/apache/pulsar-helm-chart/pull/80#issuecomment-725615956
I switched to the template function and rebased on master
This is an automated message from the Apache Gi
jeantil commented on pull request #80:
URL: https://github.com/apache/pulsar-helm-chart/pull/80#issuecomment-725622231
I'm not familiar with charts linting, it appears the error is
```
✖︎ pulsar => (version: "2.6.1-3", path: "charts/pulsar") > Error validating
maintainer 'The Apache
sijie commented on a change in pull request #80:
URL: https://github.com/apache/pulsar-helm-chart/pull/80#discussion_r521624691
##
File path: charts/pulsar/Chart.yaml
##
@@ -21,11 +21,11 @@ apiVersion: v1
appVersion: "2.6.1"
description: Apache Pulsar Helm chart for Kubernete
sijie opened a new pull request #3:
URL: https://github.com/apache/pulsar-adapters/pull/3
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
sijie opened a new pull request #1:
URL: https://github.com/apache/pulsar-presto/pull/1
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
Hi team,
I'd like to raise a discussion on adopting BookKeeper's interface taxonomy
to classify the audience and stability for Pulsar interfaces. The main
reasons are:
1) Pulsar provides extensibility through different interfaces. Some of the
implementations are included in main repo repositories
codelipenghui merged pull request #1:
URL: https://github.com/apache/pulsar-presto/pull/1
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
codelipenghui merged pull request #3:
URL: https://github.com/apache/pulsar-adapters/pull/3
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 t
sijie merged pull request #1:
URL: https://github.com/apache/pulsar-connectors/pull/1
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 t
tuteng merged pull request #352:
URL: https://github.com/apache/pulsar-manager/pull/352
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
tuteng closed issue #341:
URL: https://github.com/apache/pulsar-manager/issues/341
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 t
tuteng closed issue #347:
URL: https://github.com/apache/pulsar-manager/issues/347
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 t
tuteng merged pull request #351:
URL: https://github.com/apache/pulsar-manager/pull/351
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
+1(non-binding)
Verify checksum
Verify gpg key
Thanks,
Guangning
xiaolong ran 于2020年11月11日周三 下午6:53写道：
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version 0.3.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide s
+1 (non-binding)
- Verify checksum
- Run producer/consumer
Thank you.
Best Regards,
Yuto
--
Yuto Furuta
yfur...@yahoo-corp.jp
差出人: xiaolong ran
送信日時: 2020年11月11日 19:53
宛先: dev@pulsar.apache.org
件名: [VOTE] Pulsar Client Go Release 0.3.0 Candidate 1
Hi everyon
+1 (binding)
- Verify checksum
- Verify gpg key
- Run producer and consumer
Regards,
Hiroyuki
From: xiaolong ran
Sent: Wednesday, November 11, 2020 19:53
To: dev@pulsar.apache.org
Subject: [VOTE] Pulsar Client Go Release 0.3.0 Candidate 1
Hi everyone,
Pleas
28 matches
Mail list logo
