aditiwari01 opened a new issue #29:
URL: https://github.com/apache/pulsar-adapters/issues/29
The pulsar-spark adapter available seems to be using spark-streaming-2_10.
Is there any plan for adapter for spark_2_11?
--
This is an automated message from the Apache Git Service.
To respond
sourabhaggrawal commented on pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420#issuecomment-990661272
Hello @eolivelli @tuteng, please approve the test workflow run.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
+1
Thanks,
Hang
Li Li 于2021年12月10日周五 09:24写道：
>
> +1
>
> > On Dec 10, 2021, at 8:45 AM, Sijie Guo wrote:
> >
> > +1
> >
> > On Thu, Dec 9, 2021 at 6:27 AM Narayanan, Madhavan
> > wrote:
> >
> >> Hi Pulsar Community,
> >>
> >>
> >>
> >> I would like to start a VOTE on the Pulsar Broker extensio
+1
> On Dec 10, 2021, at 8:45 AM, Sijie Guo wrote:
>
> +1
>
> On Thu, Dec 9, 2021 at 6:27 AM Narayanan, Madhavan
> wrote:
>
>> Hi Pulsar Community,
>>
>>
>>
>> I would like to start a VOTE on the Pulsar Broker extensions for operators
>> (PIP 106).
>>
>>
>>
>> The issue for PIP 106 is h
+1
On Thu, Dec 9, 2021 at 6:27 AM Narayanan, Madhavan
wrote:
> Hi Pulsar Community,
>
>
>
> I would like to start a VOTE on the Pulsar Broker extensions for operators
> (PIP 106).
>
>
>
> The issue for PIP 106 is here:
> https://github.com/apache/pulsar/issues/12858
>
> And the prototype impleme
+1
Penghui
Narayanan, Madhavan 于2021年12月9日
周四22:27写道：
> Hi Pulsar Community,
>
>
>
> I would like to start a VOTE on the Pulsar Broker extensions for operators
> (PIP 106).
>
>
>
> The issue for PIP 106 is here:
> https://github.com/apache/pulsar/issues/12858
>
> And the prototype implementatio
hrsakai merged pull request #186:
URL: https://github.com/apache/pulsar-client-node/pull/186
--
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-u
hrsakai merged pull request #185:
URL: https://github.com/apache/pulsar-client-node/pull/185
--
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-u
Dave - I don't think SN presents the community. We just shared out insights
on community progress. Also, if you looked into our past blog posts, we
have been pointing people to the Pulsar website and Slack channel.
- Sijie
On Thu, Dec 9, 2021 at 12:13 PM Dave Fisher wrote:
> OK. I see the new
+1
On 2021/12/09 15:29:55 Michael Marshall wrote:
> Hello Pulsar Community,
>
> I'd like to propose that we release 2.7.4. We have merged several
> important fixes since we released 2.7.3 in August.
>
> I am happy to volunteer to be the release manager.
>
> Here [0] you can find the list of 36
Hi All,
The VOTE passed with total 8 +1s and no -1.
6 binding +1 from:
Matteo Merli
Enrico Olivelli
Jerry Peng
Guangning E
Penghui Li
Hang Chen
2 non-binding +1 from:
Michael Marshall
Li Li
I'll mark the PR as ready for review and let's push this feature : )
Thank you for all your help.
Best r
OK. I see the new name.
My concern is about SN posting blogs that are about community news without
telling readers where the whole Pulsar community can be found.
> On Dec 9, 2021, at 6:18 AM, Dianjin Wang
> wrote:
>
> I want to sync the blog status, the update has been done.
>
> Best,
> Dia
frankjkelly opened a new issue #185:
URL: https://github.com/apache/pulsar-helm-chart/issues/185
**Is your feature request related to a problem? Please describe.**
The problem is each helm chart version is deployed once. See
https://github.com/apache/pulsar-helm-chart/releases
So
+1
--
Matteo Merli
On Thu, Dec 9, 2021 at 7:30 AM Michael Marshall wrote:
>
> Hello Pulsar Community,
>
> I'd like to propose that we release 2.7.4. We have merged several
> important fixes since we released 2.7.3 in August.
>
> I am happy to volunteer to be the release manager.
>
> Here [0] you
Hello Pulsar Community,
I'd like to propose that we release 2.7.4. We have merged several
important fixes since we released 2.7.3 in August.
I am happy to volunteer to be the release manager.
Here [0] you can find the list of 36 commits cherry-picked to
branch-2.7 since 2.7.3 release. It looks l
Hi Pulsar Community,
I would like to start a VOTE on the Pulsar Broker extensions for operators (PIP
106).
The issue for PIP 106 is here: https://github.com/apache/pulsar/issues/12858
And the prototype implementation is here:
https://github.com/apache/pulsar/pull/12536
Kindly VOTE as ea
I want to sync the blog status, the update has been done.
Best,
Dianjin Wang
On Thu, Dec 9, 2021 at 2:34 PM Sijie Guo wrote:
> Hi Dave,
>
> Will follow up tomorrow morning (Pacific Time).
>
> - Sijie
>
> On Wed, Dec 8, 2021 at 9:35 PM Dave Fisher wrote:
>
> > Hi Sijie,
> >
> > Thanks for hand
SapnaGirdhani1 opened a new issue #184:
URL: https://github.com/apache/pulsar-helm-chart/issues/184
I used Helm Chart to install Pulsar on my Kubernetes Cluster. It installs
Pulsar Manager V1 ( apachepulsar/pulsar-manager:v0.1.0) by default. I want to
have Pulsar manager V2. Not finding an
shiv4289 commented on a change in pull request #434:
URL: https://github.com/apache/pulsar-manager/pull/434#discussion_r765586155
##
File path: src/main/java/org/apache/pulsar/manager/controller/SSOController.java
##
@@ -0,0 +1,131 @@
+/**
+ * Licensed under the Apache License,
+1
Enrico
Il giorno gio 9 dic 2021 alle ore 05:54 Sijie Guo ha
scritto:
> +1
>
> On Wed, Dec 8, 2021 at 8:37 PM Masahiro Sakamoto
> wrote:
>
> > Hi Team,
> >
> > I'm planning to release v1.5.0 of the Pulsar Node.js client next week as
> > some bug fixes have been merged to master.
> > If you h
20 matches
Mail list logo
