date:20210727

Re: Moving questions from Slack to Stack Overflow

2021-07-27 Thread Devin Bost

What are some of the most commonly asked questions or kinds of questions?

--
Devin G. Bost

On Mon, Jul 26, 2021, 1:34 AM Anonymitaet _ 
wrote:

> Hi all,
>
> Great idea.
>
> For the "contact" page, we can add "Pulsar community meeting info" (
> https://github.com/apache/pulsar/wiki/Community-Meetings) there as well.
>
> Here is a good example of the "community" page:
> https://cassandra.apache.org/community/.
> 
> From: r...@apache.org 
> Sent: Monday, July 26, 2021 11:08
> To: Dev 
> Subject: Re: Moving questions from Slack to Stack Overflow
>
> Good ideas, we had the same idea before, but for some reason, we stagnated.
> It would be a very good job to reopen here.
>
> We already have a tag tracking related issues before, refer to:
> https://stackoverflow.com/questions/tagged/apache-pulsar. We can consider
> continuing to use this tag.
>
> --
>
> Thanks
> Xiaolong Ran
>
> Chris Latimer  于2021年7月24日周六 上午6:54写道：
>
> > I've also noticed that most Pulsar-related questions on StackOverflow are
> > tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want to
> > recommend one tag over the other?
> >
> > On Fri, Jul 23, 2021 at 4:01 PM Neng Lu  wrote:
> >
> > > +1
> > >
> > > On 2021/07/23 16:48:42 Aaron Williams wrote:
> > > > Hello Apache Pulsar Community,
> > > >
> > > > Many of us community members were having a conversation about Slack
> and
> > > how
> > > > it is not working very well as a tool to answer questions from the
> > wider
> > > > community and we should try to push more of the questions to Stack
> > > > Overflow.
> > > >
> > > > We would like to suggest-
> > > >
> > > >1.
> > > >
> > > >Add a link to stack overflow to the contact page of the website:
> > > >https://pulsar.apache.org/en/contact/
> > > >2.
> > > >
> > > >Add text to the webpage stating that we recommend that if you
> have a
> > > >technical question, please ask it on Stack Overflow
> > > >3.
> > > >
> > > >On Slack, we encourage them to post their question to Stack
> Overflow
> > > >
> > > >
> > > > Reasons:
> > > >
> > > >-
> > > >
> > > >We are on the free version of Slack and thus all questions/answers
> > > >before the middle of June are lost (10k messages max).
> > > >-
> > > >
> > > >We answer the same question over and over.
> > > >-
> > > >
> > > >   We want to make it easier for our community to find the
> answers.
> > > >   -
> > > >
> > > >Developers expect answers to be on Stack Overflow
> > > >-
> > > >
> > > >It is easier to copy and paste an error message into Google and if
> > it
> > > >has been posted to Stack Overflow, then the questioner will find
> the
> > > answer
> > > >quickly.
> > > >-
> > > >
> > > >   Slack is not searchable by Google, plus we won’t lose the
> > > >   question/answer after 5 weeks
> > > >
> > > >
> > > > Thoughts?
> > > >
> > > > Thanks,
> > > >
> > > > Aaron Williams
> > > >
> > >
> >
>

Re: [Doc] Upgrade Docusuraus

2021-07-27 Thread Guangning E

If content from both the REST API and CLI are being folded into docs, then
we would only need to create one design template for docs vs. 3 templates -
1 for docs (Docusaurus), 1 for REST-API (is this in Docusaurus?), 1 for CLI
is this Redoc, Docusaurus or something else?). Does that help?

Yes, there are currently three page styles, the rest-api uses redoc, the
cli uses a style similar to kubectl, and the main site's docusuraus style,
but we will consider unifying their styles, and I think in the future they
will use a unified style



Melissa Logan  于2021年7月27日周二 上午11:23写道：

> REST API and CLI docs are automatically generated from code, what kind of
> "template" for them do you refer to?
> > By “template” I mean a design template to create a uniform look and
> feel for the site. The REST API and CLI docs each have their own look and
> feel with Redoc being used for the API pages. Our aim would be to create a
> unified look and feel throughout the site, including those pages.
> If content from both the REST API and CLI are being folded into docs, then
> we would only need to create one design template for docs vs. 3 templates -
> 1 for docs (Docusaurus), 1 for REST-API (is this in Docusaurus?), 1 for CLI
> is this Redoc, Docusaurus or something else?). Does that help?
>
> Agree. SEO is important as it improves user experience, making it more
> likely for users to become repeat buyers. So any plan for the research?
> > Our team will conduct an SEO audit to understand what needs improvement
> and make suggestions.
>
> On Mon, Jul 26, 2021 at 5:53 AM Anonymitaet _ 
> wrote:
>
>> Hi Melissa,
>>
>> Many thanks for your suggestions! I've replied to you in the google doc,
>> PTAL.
>>
>> #1
>>
>> *Based on what we see today, there would be 8-10 new templates to create*
>> * (homepage, landing, general, library, events, blog landing, blog, and
>> docs -- and possibly a template for REST API and CLI Pulsar Admin, unless
>> the latter two will be merged into docs) -- for which we could contribute
>> design and development.*
>>
>> REST API and CLI docs are automatically generated from code, what kind of
>> "template" for them do you refer to?
>>
>>
>>- REST API doc example:
>>https://pulsar.apache.org/admin-rest-api/?version=2.8.0&apiversion=v2
>>-
>>- CLI doc example:
>>https://pulsar.apache.org/tools/pulsar-admin/2.8.0-SNAPSHOT/
>>
>>
>> #2
>>
>>
>> *One consideration brought up on a previous thread [3] was SEO. We would
>> conduct research on keywords and update content to be relevant (with the
>> priority being meaningful content to end users first, SEO second).*
>>
>> Agree. SEO is important as it improves user experience, making it more
>> likely for users to become repeat buyers. So any plan for the research?
>>
>> #3
>>
>>
>>
>>
>>
>> *Wonderful! Agree with what you say here. I have added a suggested
>> navigation to the doc though still have a few questions about if/whether it
>> makes sense to merge the REST-API section and/or the CLI>Pulsar-Admin
>> section into docs. That can be determined later, but wanted to mention as
>> an open question. Please note these recommendations are in absence of
>> seeing the analytics, which may affect page orders.*
>>
>> We're re-structuring the information architecture of docs and planning to
>> put "REST API" and "CLI" docs to the "Reference" chapter. We'll send it out
>> for discussion once we finalize it.
>>
>> #4
>>
>>
>>
>>
>> *Absolutely, our team will work with Docusauraus as the
>> community-approved framework. It also looked like something called Redoc
>> might be in use (mentioned in the REST-API section). Is this framework also
>> being used or should that be brought into Docusaurus? Are both front-end
>> and back-end design/development needed? We can do either/or.*
>>
>> @Guangning E , any thoughts on this?
>>
>>
>>
>> --
>> *From:* Aaron Williams 
>> *Sent:* Saturday, July 24, 2021 03:03
>> *To:* Dev 
>> *Subject:* Re: [Doc] Upgrade Docusuraus
>>
>> One of the missing pieces to the design of the current website is the
>> journey of the visitor.  Is this their first time, if so what do they
>> need?  Is this their 10th time and they are looking for documentation?
>>
>> We need a better, cleaner, easier to use website.
>>
>> The above is a longer version of saying
>>
>> +10!
>>
>>
>>
>> >
>> >
>> > Hi,
>> >
>> > I'm a new contributor to the Pulsar community. My team and I recently
>> > rebuilt the Apache Cassandra website [1] with the aim of improving user
>> > experience and SEO to help visitors more easily understand and use
>> > Cassandra. Based on recent threads here [2] and here [3], it appears the
>> > Pulsar community has similar aims.
>> >
>> > My team and I have decades of experience building sites with expertise
>> > working with open source projects. We are offering to contribute 2-3
>> design
>> > concepts for the community to vote on that will create a uniform design
>> > pattern to the site.
>> >
>> >

Re: Moving questions from Slack to Stack Overflow

2021-07-27 Thread Christophe Bornet

Hi all,

A very important point that hasn't been mentioned yet about moving to SoF :
the number of issues on SoF is regularly used as a metric of the maturity
of a project.
And maturity of the project is a point that is often taken against Pulsar
compared to other competing technologies. I know it first hand since it has
been an argument that was opposed to me in my previous company by people
who wanted to stay on Kafka (despite all the operating issues we had...).
So +100 to go to SoF !

Best regards.

Christophe

Le mar. 27 juil. 2021 à 10:59, Devin Bost  a écrit :

> What are some of the most commonly asked questions or kinds of questions?
>
> --
> Devin G. Bost
>
> On Mon, Jul 26, 2021, 1:34 AM Anonymitaet _ 
> wrote:
>
> > Hi all,
> >
> > Great idea.
> >
> > For the "contact" page, we can add "Pulsar community meeting info" (
> > https://github.com/apache/pulsar/wiki/Community-Meetings) there as well.
> >
> > Here is a good example of the "community" page:
> > https://cassandra.apache.org/community/.
> > 
> > From: r...@apache.org 
> > Sent: Monday, July 26, 2021 11:08
> > To: Dev 
> > Subject: Re: Moving questions from Slack to Stack Overflow
> >
> > Good ideas, we had the same idea before, but for some reason, we
> stagnated.
> > It would be a very good job to reopen here.
> >
> > We already have a tag tracking related issues before, refer to:
> > https://stackoverflow.com/questions/tagged/apache-pulsar. We can
> consider
> > continuing to use this tag.
> >
> > --
> >
> > Thanks
> > Xiaolong Ran
> >
> > Chris Latimer  于2021年7月24日周六 上午6:54写道：
> >
> > > I've also noticed that most Pulsar-related questions on StackOverflow
> are
> > > tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want to
> > > recommend one tag over the other?
> > >
> > > On Fri, Jul 23, 2021 at 4:01 PM Neng Lu  wrote:
> > >
> > > > +1
> > > >
> > > > On 2021/07/23 16:48:42 Aaron Williams wrote:
> > > > > Hello Apache Pulsar Community,
> > > > >
> > > > > Many of us community members were having a conversation about Slack
> > and
> > > > how
> > > > > it is not working very well as a tool to answer questions from the
> > > wider
> > > > > community and we should try to push more of the questions to Stack
> > > > > Overflow.
> > > > >
> > > > > We would like to suggest-
> > > > >
> > > > >1.
> > > > >
> > > > >Add a link to stack overflow to the contact page of the website:
> > > > >https://pulsar.apache.org/en/contact/
> > > > >2.
> > > > >
> > > > >Add text to the webpage stating that we recommend that if you
> > have a
> > > > >technical question, please ask it on Stack Overflow
> > > > >3.
> > > > >
> > > > >On Slack, we encourage them to post their question to Stack
> > Overflow
> > > > >
> > > > >
> > > > > Reasons:
> > > > >
> > > > >-
> > > > >
> > > > >We are on the free version of Slack and thus all
> questions/answers
> > > > >before the middle of June are lost (10k messages max).
> > > > >-
> > > > >
> > > > >We answer the same question over and over.
> > > > >-
> > > > >
> > > > >   We want to make it easier for our community to find the
> > answers.
> > > > >   -
> > > > >
> > > > >Developers expect answers to be on Stack Overflow
> > > > >-
> > > > >
> > > > >It is easier to copy and paste an error message into Google and
> if
> > > it
> > > > >has been posted to Stack Overflow, then the questioner will find
> > the
> > > > answer
> > > > >quickly.
> > > > >-
> > > > >
> > > > >   Slack is not searchable by Google, plus we won’t lose the
> > > > >   question/answer after 5 weeks
> > > > >
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Aaron Williams
> > > > >
> > > >
> > >
> >
>

gRPC protocol handler

2021-07-27 Thread Christophe Bornet

Hi Apache Pulsar community,

I’m a huge fan of the potential that the pluggable protocol handlers
introduced in Pulsar 2.5 unlock for increasing Pulsar popularity by
reducing the friction to adopt it. This includes both general-purpose APIs
like REST and gRPC, and compatibility layers for other streaming products
like Kafka and AMQP.

I’ve created a PIP
 and
an implementation of a gRPC protocol handler, but review of the pull
request stalled out  so I moved
my implementation to my own repository
 while I finished it.

With development and testing effectively complete, I’d like to reopen the
discussion:


   1.

   How can I move forward with contributing my gRPC protocol handler to
   Apache Pulsar? Is this something that is interesting and useful to the
   broader community?
   2.

   More broadly, what policy do we want to establish for Pulsar protocol
   handlers and other compatibility layers?  As indicated above, I think that
   we should provide Pulsar with “batteries included” to make it as easy as
   possible for new users to get started.


Best regards.

Christophe

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

2021-07-27 Thread PengHui Li

+1 (binding)

- check the signature and checksum
- run the standalone to produce and consume messages
- run the Cassandra-connector
- run the state function

Thanks,
Penghui

On Mon, Jul 26, 2021 at 10:55 PM Enrico Olivelli 
wrote:

> Hi,
> are you able to run the tests from the source packages ?
> If I run the pulsar-broker test at a certain point (I am still not able to
> see where) my machines starts to use 100% CPU and it is blocked and I need
> to reboot
>
>
> Enrico
>
> Il giorno lun 26 lug 2021 alle ore 09:37 Nozomi Kurihara <
> nkuri...@apache.org> ha scritto:
>
> > +1 (binding)
> >
> > - check signatures/checksums
> > - compile the source
> > - standalone/producer/consumer worked
> > - function/cassandra-connector worked
> >
> > Best Regards,
> > Nozomi
> >
> > 2021年7月26日(月) 16:07 Masahiro Sakamoto :
> >
> > > +1 (binding)
> > >
> > > - Checked checksums and signatures
> > > - Compiled the source
> > > - Ran the standalone server
> > > - Confirmed that producer and consumer work properly
> > > - Confirmed that the sample function works properly
> > >
> > > Regards,
> > >
> > > Masahiro Sakamoto
> > > Yahoo Japan Corp.
> > > E-mail: massa...@yahoo-corp.jp
> > >
> > > -Original Message-
> > > From: 丛搏 
> > > Sent: Wednesday, July 21, 2021 9:00 PM
> > > To: dev@pulsar.apache.org
> > > Subject: [VOTE] Pulsar Release 2.7.3 Candidate 2
> > >
> > > This is the second release candidate for Apache Pulsar, version 2.7.3.
> > >
> > > It fixes the following issues:
> > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.3+is%3Apr+
> > >
> > > *** 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.7.3-candidate-2/
> > >
> > > SHA-512 checksums:
> > >
> > >
> > >
> >
> 323e896bebb2981cc99178e9584273908d5fd9427fa8e907027e8b7c59946cb04a3821af0e70b1a29b0ba166120c493a432fd4d5920e71ccef11e4095f5f30c6
> > >  apache-pulsar-2.7.3-bin.tar.gz
> > >
> > >
> > >
> >
> 4eb2ff4a058fc5f0c0f1352aff926e6125c833c509901a16f93a118540a79a1fc575225b224f1f8ab7ff77c5aeea2a20fe8fedea1717ea249c27c9bbfbb4aae8
> > >  apache-pulsar-2.7.3-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1093/
> > >
> > > The tag to be voted upon:
> > > v2.7.3-candidate-2 (d6c2667ea05339efd8aabf56fe667835b4fe76e9)
> > > https://github.com/apache/pulsar/releases/tag/v2.7.3-candidate-2
> > >
> > > 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 the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> >
>

Re: Moving questions from Slack to Stack Overflow

2021-07-27 Thread Chris Latimer

That's a really good point, Christophe. That was called out in a recent
article on TheNewStack comparing Pulsar and Kafka:
https://thenewstack.io/pulsar-takes-on-kafka-with-uniform-architecture-speed/

On Tue, Jul 27, 2021 at 7:09 AM Christophe Bornet 
wrote:

> Hi all,
>
> A very important point that hasn't been mentioned yet about moving to SoF :
> the number of issues on SoF is regularly used as a metric of the maturity
> of a project.
> And maturity of the project is a point that is often taken against Pulsar
> compared to other competing technologies. I know it first hand since it has
> been an argument that was opposed to me in my previous company by people
> who wanted to stay on Kafka (despite all the operating issues we had...).
> So +100 to go to SoF !
>
> Best regards.
>
> Christophe
>
> Le mar. 27 juil. 2021 à 10:59, Devin Bost  a écrit :
>
> > What are some of the most commonly asked questions or kinds of questions?
> >
> > --
> > Devin G. Bost
> >
> > On Mon, Jul 26, 2021, 1:34 AM Anonymitaet _ 
> > wrote:
> >
> > > Hi all,
> > >
> > > Great idea.
> > >
> > > For the "contact" page, we can add "Pulsar community meeting info" (
> > > https://github.com/apache/pulsar/wiki/Community-Meetings) there as
> well.
> > >
> > > Here is a good example of the "community" page:
> > > https://cassandra.apache.org/community/.
> > > 
> > > From: r...@apache.org 
> > > Sent: Monday, July 26, 2021 11:08
> > > To: Dev 
> > > Subject: Re: Moving questions from Slack to Stack Overflow
> > >
> > > Good ideas, we had the same idea before, but for some reason, we
> > stagnated.
> > > It would be a very good job to reopen here.
> > >
> > > We already have a tag tracking related issues before, refer to:
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_tagged_apache-2Dpulsar&d=DwIFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=hXwUo08MMkKWtyhXcYk5QTdO0d5mkkcEe-LpcFU05mA&m=oBdrA2No1uLVrl0768xKcblT8WGwaOdBLaud73RXraI&s=1jkBk-oHCTrVEa5fJIYm8JTB-s2a0e-vuz_iRnr9kTU&e=
> . We can
> > consider
> > > continuing to use this tag.
> > >
> > > --
> > >
> > > Thanks
> > > Xiaolong Ran
> > >
> > > Chris Latimer  于2021年7月24日周六 上午6:54写道：
> > >
> > > > I've also noticed that most Pulsar-related questions on StackOverflow
> > are
> > > > tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want to
> > > > recommend one tag over the other?
> > > >
> > > > On Fri, Jul 23, 2021 at 4:01 PM Neng Lu  wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On 2021/07/23 16:48:42 Aaron Williams wrote:
> > > > > > Hello Apache Pulsar Community,
> > > > > >
> > > > > > Many of us community members were having a conversation about
> Slack
> > > and
> > > > > how
> > > > > > it is not working very well as a tool to answer questions from
> the
> > > > wider
> > > > > > community and we should try to push more of the questions to
> Stack
> > > > > > Overflow.
> > > > > >
> > > > > > We would like to suggest-
> > > > > >
> > > > > >1.
> > > > > >
> > > > > >Add a link to stack overflow to the contact page of the
> website:
> > > > > >https://pulsar.apache.org/en/contact/
> > > > > >2.
> > > > > >
> > > > > >Add text to the webpage stating that we recommend that if you
> > > have a
> > > > > >technical question, please ask it on Stack Overflow
> > > > > >3.
> > > > > >
> > > > > >On Slack, we encourage them to post their question to Stack
> > > Overflow
> > > > > >
> > > > > >
> > > > > > Reasons:
> > > > > >
> > > > > >-
> > > > > >
> > > > > >We are on the free version of Slack and thus all
> > questions/answers
> > > > > >before the middle of June are lost (10k messages max).
> > > > > >-
> > > > > >
> > > > > >We answer the same question over and over.
> > > > > >-
> > > > > >
> > > > > >   We want to make it easier for our community to find the
> > > answers.
> > > > > >   -
> > > > > >
> > > > > >Developers expect answers to be on Stack Overflow
> > > > > >-
> > > > > >
> > > > > >It is easier to copy and paste an error message into Google
> and
> > if
> > > > it
> > > > > >has been posted to Stack Overflow, then the questioner will
> find
> > > the
> > > > > answer
> > > > > >quickly.
> > > > > >-
> > > > > >
> > > > > >   Slack is not searchable by Google, plus we won’t lose the
> > > > > >   question/answer after 5 weeks
> > > > > >
> > > > > >
> > > > > > Thoughts?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Aaron Williams
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Moving questions from Slack to Stack Overflow

2021-07-27 Thread Chris Herzog

I agree as well - we need to be cognizant of perception and this is a good
step in a positive direction towards addressing that.

Pulsar *is* competitive with Kafka in many ways but Kafka tends to suck up
a lot of the oxygen...

On Tue, Jul 27, 2021 at 10:09 AM Chris Latimer 
wrote:

> That's a really good point, Christophe. That was called out in a recent
> article on TheNewStack comparing Pulsar and Kafka:
>
> https://thenewstack.io/pulsar-takes-on-kafka-with-uniform-architecture-speed/
>
> On Tue, Jul 27, 2021 at 7:09 AM Christophe Bornet 
> wrote:
>
> > Hi all,
> >
> > A very important point that hasn't been mentioned yet about moving to
> SoF :
> > the number of issues on SoF is regularly used as a metric of the maturity
> > of a project.
> > And maturity of the project is a point that is often taken against Pulsar
> > compared to other competing technologies. I know it first hand since it
> has
> > been an argument that was opposed to me in my previous company by people
> > who wanted to stay on Kafka (despite all the operating issues we had...).
> > So +100 to go to SoF !
> >
> > Best regards.
> >
> > Christophe
> >
> > Le mar. 27 juil. 2021 à 10:59, Devin Bost  a
> écrit :
> >
> > > What are some of the most commonly asked questions or kinds of
> questions?
> > >
> > > --
> > > Devin G. Bost
> > >
> > > On Mon, Jul 26, 2021, 1:34 AM Anonymitaet _ 
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > Great idea.
> > > >
> > > > For the "contact" page, we can add "Pulsar community meeting info" (
> > > > https://github.com/apache/pulsar/wiki/Community-Meetings) there as
> > well.
> > > >
> > > > Here is a good example of the "community" page:
> > > > https://cassandra.apache.org/community/.
> > > > 
> > > > From: r...@apache.org 
> > > > Sent: Monday, July 26, 2021 11:08
> > > > To: Dev 
> > > > Subject: Re: Moving questions from Slack to Stack Overflow
> > > >
> > > > Good ideas, we had the same idea before, but for some reason, we
> > > stagnated.
> > > > It would be a very good job to reopen here.
> > > >
> > > > We already have a tag tracking related issues before, refer to:
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_tagged_apache-2Dpulsar&d=DwIFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=hXwUo08MMkKWtyhXcYk5QTdO0d5mkkcEe-LpcFU05mA&m=oBdrA2No1uLVrl0768xKcblT8WGwaOdBLaud73RXraI&s=1jkBk-oHCTrVEa5fJIYm8JTB-s2a0e-vuz_iRnr9kTU&e=
> > . We can
> > > consider
> > > > continuing to use this tag.
> > > >
> > > > --
> > > >
> > > > Thanks
> > > > Xiaolong Ran
> > > >
> > > > Chris Latimer  于2021年7月24日周六 上午6:54写道：
> > > >
> > > > > I've also noticed that most Pulsar-related questions on
> StackOverflow
> > > are
> > > > > tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want
> to
> > > > > recommend one tag over the other?
> > > > >
> > > > > On Fri, Jul 23, 2021 at 4:01 PM Neng Lu  wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On 2021/07/23 16:48:42 Aaron Williams wrote:
> > > > > > > Hello Apache Pulsar Community,
> > > > > > >
> > > > > > > Many of us community members were having a conversation about
> > Slack
> > > > and
> > > > > > how
> > > > > > > it is not working very well as a tool to answer questions from
> > the
> > > > > wider
> > > > > > > community and we should try to push more of the questions to
> > Stack
> > > > > > > Overflow.
> > > > > > >
> > > > > > > We would like to suggest-
> > > > > > >
> > > > > > >1.
> > > > > > >
> > > > > > >Add a link to stack overflow to the contact page of the
> > website:
> > > > > > >https://pulsar.apache.org/en/contact/
> > > > > > >2.
> > > > > > >
> > > > > > >Add text to the webpage stating that we recommend that if
> you
> > > > have a
> > > > > > >technical question, please ask it on Stack Overflow
> > > > > > >3.
> > > > > > >
> > > > > > >On Slack, we encourage them to post their question to Stack
> > > > Overflow
> > > > > > >
> > > > > > >
> > > > > > > Reasons:
> > > > > > >
> > > > > > >-
> > > > > > >
> > > > > > >We are on the free version of Slack and thus all
> > > questions/answers
> > > > > > >before the middle of June are lost (10k messages max).
> > > > > > >-
> > > > > > >
> > > > > > >We answer the same question over and over.
> > > > > > >-
> > > > > > >
> > > > > > >   We want to make it easier for our community to find the
> > > > answers.
> > > > > > >   -
> > > > > > >
> > > > > > >Developers expect answers to be on Stack Overflow
> > > > > > >-
> > > > > > >
> > > > > > >It is easier to copy and paste an error message into Google
> > and
> > > if
> > > > > it
> > > > > > >has been posted to Stack Overflow, then the questioner will
> > find
> > > > the
> > > > > > answer
> > > > > > >quickly.
> > > > > > >-
> > > > > > >
> > > > > > >   Slack is not searchable by Google, plus we won’t lose the
> > > > > > >   question/answer after 5 weeks
> > >

[GitHub] [pulsar-client-node] hrsakai opened a new pull request #167: Bump the master version to 1.5.0

2021-07-27 Thread GitBox



hrsakai opened a new pull request #167:
URL: https://github.com/apache/pulsar-client-node/pull/167


   I have already created branch-1.4 to perform the release, so I will bump the 
master version to 1.5.0-rc.0.


-- 
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

[VOTE] Pulsar Node.js Client Release 1.4.0 Candidate 1

2021-07-27 Thread Hiroyuki Sakai

This is the first release candidate for Apache Pulsar Node.js client, version 
1.4.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/milestone/6?closed=1

*** 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), the npm package is provided
for convenience.

The tag to be voted upon:
v1.4.0-rc.1
https://github.com/apache/pulsar-client-node/releases/tag/v1.4.0-rc.1

The npm package:
https://www.npmjs.com/package/pulsar-client/v/1.4.0-rc.1

Please download the source files, and follow the README to build
and run the Pulsar Node.js client.

==
Hiroyuki Sakai
Yahoo Japan Corp.
E-mail: hsa...@yahoo-corp.jp

[PIP] PIP for the Topic policy across multiple clusters

2021-07-27 Thread linlin

Hi, All

I have prepared a PIP for the Topic policy across multiple clusters.
Please take a look and let me know what you think.

I would really appreciate it.

Best Regards,
Lin Lin

===
Topic policy across multiple clusters


   -

   Status: Proposal
   -

   Authors: Penghui Li、Chen Hang、 Lin Lin
   -

   Pull Request:
   -

   Mailing List discussion:
   -

   Release:

Motivation

When setting the topic policy for a geo-replicated cluster, some policies
want to affect the whole geo-replicated cluster but some only want to
affect the local cluster. So the proposal is to support global topic policy
and local topic policy.
Approach

Currently, we are using the TopicPolicies construction to store the topic
policy for a topic. An easy way to achieve different topic policies for
multiple clusters is to add a global flag to TopicPolicies .Replicator will
replicate policies with a global flag to other clusters

```

public class TopicPolicies {

 bBoolean isGlobal = false

}

```

We only cache one local Topic Policies in the memory before. Now it will
become two, one is Local and the other is Global.

After adding the global topic policy, the topic applied priority is:


   1.

   Local cluster topic policy
   2.

   Global topic policy
   3.

   Namespace policy
   4.

   Broker default configuration


When setting a global topic policy, we can use the `--global` option, it
should be:

```

bin/pulsar-admin topics set-retention -s 1G -t 1d --global my-topic

```

If the --global option is not added, the behavior is consistent with
before, and only updates the local policies.

Topic policies are stored in System Topic, we can directly use Replicator
to replicate data to other Clusters. We need to add a new API to the
Replicator interface, which can set the Filter Function. Then add a
Function to filter out the data with isGlobal = false

Delete a cluster?

Deleting a cluster will now delete local topic policies and will not affect
other clusters, because only global policies will be replicated to other
clusters
Changes

   -

   Every topic policy API adds the `--global` option. Including broker REST
   API, Admin SDK, CMD.



   -

   Add API `public void setFilterFunction(Function)`. If
   Function returns false, then filter out the input message.


Compatibility

The solution does not introduce any compatibility issues, `isGlobal` in
TopicPolicies is false by default in existing Policies.

Test Plan

   1.

   Existing TopicPolicies will not be affected
   2.

   Only replicate Global Topic Policies, FilterFunction can run as expected
   3.

   Priority of Topic Policies matches our setting

Re: [PIP] PIP for the Topic policy across multiple clusters

2021-07-27 Thread Sijie Guo

Hi Linlin,

Thank you for bringing this proposal to the community!

Since you are a committer, you should be able to create a wiki page on
Pulsar wiki. Can you do that?

- Sijie

On Tue, Jul 27, 2021 at 9:03 PM linlin  wrote:
>
> Hi, All
>
> I have prepared a PIP for the Topic policy across multiple clusters.
> Please take a look and let me know what you think.
>
> I would really appreciate it.
>
> Best Regards,
> Lin Lin
>
> ===
> Topic policy across multiple clusters
>
>
>-
>
>Status: Proposal
>-
>
>Authors: Penghui Li、Chen Hang、 Lin Lin
>-
>
>Pull Request:
>-
>
>Mailing List discussion:
>-
>
>Release:
>
> Motivation
>
> When setting the topic policy for a geo-replicated cluster, some policies
> want to affect the whole geo-replicated cluster but some only want to
> affect the local cluster. So the proposal is to support global topic policy
> and local topic policy.
> Approach
>
> Currently, we are using the TopicPolicies construction to store the topic
> policy for a topic. An easy way to achieve different topic policies for
> multiple clusters is to add a global flag to TopicPolicies .Replicator will
> replicate policies with a global flag to other clusters
>
> ```
>
> public class TopicPolicies {
>
>  bBoolean isGlobal = false
>
> }
>
> ```
>
> We only cache one local Topic Policies in the memory before. Now it will
> become two, one is Local and the other is Global.
>
> After adding the global topic policy, the topic applied priority is:
>
>
>1.
>
>Local cluster topic policy
>2.
>
>Global topic policy
>3.
>
>Namespace policy
>4.
>
>Broker default configuration
>
>
> When setting a global topic policy, we can use the `--global` option, it
> should be:
>
> ```
>
> bin/pulsar-admin topics set-retention -s 1G -t 1d --global my-topic
>
> ```
>
> If the --global option is not added, the behavior is consistent with
> before, and only updates the local policies.
>
> Topic policies are stored in System Topic, we can directly use Replicator
> to replicate data to other Clusters. We need to add a new API to the
> Replicator interface, which can set the Filter Function. Then add a
> Function to filter out the data with isGlobal = false
>
> Delete a cluster?
>
> Deleting a cluster will now delete local topic policies and will not affect
> other clusters, because only global policies will be replicated to other
> clusters
> Changes
>
>-
>
>Every topic policy API adds the `--global` option. Including broker REST
>API, Admin SDK, CMD.
>
>
>
>-
>
>Add API `public void setFilterFunction(Function)`. If
>Function returns false, then filter out the input message.
>
>
> Compatibility
>
> The solution does not introduce any compatibility issues, `isGlobal` in
> TopicPolicies is false by default in existing Policies.
>
> Test Plan
>
>1.
>
>Existing TopicPolicies will not be affected
>2.
>
>Only replicate Global Topic Policies, FilterFunction can run as expected
>3.
>
>Priority of Topic Policies matches our setting

Re: Moving questions from Slack to Stack Overflow

2021-07-27 Thread Sijie Guo

apache-pulsar would be preferred.

On Fri, Jul 23, 2021 at 3:54 PM Chris Latimer
 wrote:
>
> I've also noticed that most Pulsar-related questions on StackOverflow are
> tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want to
> recommend one tag over the other?
>
> On Fri, Jul 23, 2021 at 4:01 PM Neng Lu  wrote:
>
> > +1
> >
> > On 2021/07/23 16:48:42 Aaron Williams wrote:
> > > Hello Apache Pulsar Community,
> > >
> > > Many of us community members were having a conversation about Slack and
> > how
> > > it is not working very well as a tool to answer questions from the wider
> > > community and we should try to push more of the questions to Stack
> > > Overflow.
> > >
> > > We would like to suggest-
> > >
> > >1.
> > >
> > >Add a link to stack overflow to the contact page of the website:
> > >https://pulsar.apache.org/en/contact/
> > >2.
> > >
> > >Add text to the webpage stating that we recommend that if you have a
> > >technical question, please ask it on Stack Overflow
> > >3.
> > >
> > >On Slack, we encourage them to post their question to Stack Overflow
> > >
> > >
> > > Reasons:
> > >
> > >-
> > >
> > >We are on the free version of Slack and thus all questions/answers
> > >before the middle of June are lost (10k messages max).
> > >-
> > >
> > >We answer the same question over and over.
> > >-
> > >
> > >   We want to make it easier for our community to find the answers.
> > >   -
> > >
> > >Developers expect answers to be on Stack Overflow
> > >-
> > >
> > >It is easier to copy and paste an error message into Google and if it
> > >has been posted to Stack Overflow, then the questioner will find the
> > answer
> > >quickly.
> > >-
> > >
> > >   Slack is not searchable by Google, plus we won’t lose the
> > >   question/answer after 5 weeks
> > >
> > >
> > > Thoughts?
> > >
> > > Thanks,
> > >
> > > Aaron Williams
> > >
> >

Re: Moving questions from Slack to Stack Overflow

2021-07-27 Thread Sijie Guo

Yu,

Do you want to submit PRs to update those pages?

- Sijie

On Mon, Jul 26, 2021 at 12:34 AM Anonymitaet _  wrote:
>
> Hi all,
>
> Great idea.
>
> For the "contact" page, we can add "Pulsar community meeting info" 
> (https://github.com/apache/pulsar/wiki/Community-Meetings) there as well.
>
> Here is a good example of the "community" page: 
> https://cassandra.apache.org/community/.
> 
> From: r...@apache.org 
> Sent: Monday, July 26, 2021 11:08
> To: Dev 
> Subject: Re: Moving questions from Slack to Stack Overflow
>
> Good ideas, we had the same idea before, but for some reason, we stagnated.
> It would be a very good job to reopen here.
>
> We already have a tag tracking related issues before, refer to:
> https://stackoverflow.com/questions/tagged/apache-pulsar. We can consider
> continuing to use this tag.
>
> --
>
> Thanks
> Xiaolong Ran
>
> Chris Latimer  于2021年7月24日周六 上午6:54写道：
>
> > I've also noticed that most Pulsar-related questions on StackOverflow are
> > tagged as [apache-pulsar] and sometimes also [pulsar]. Do we want to
> > recommend one tag over the other?
> >
> > On Fri, Jul 23, 2021 at 4:01 PM Neng Lu  wrote:
> >
> > > +1
> > >
> > > On 2021/07/23 16:48:42 Aaron Williams wrote:
> > > > Hello Apache Pulsar Community,
> > > >
> > > > Many of us community members were having a conversation about Slack and
> > > how
> > > > it is not working very well as a tool to answer questions from the
> > wider
> > > > community and we should try to push more of the questions to Stack
> > > > Overflow.
> > > >
> > > > We would like to suggest-
> > > >
> > > >1.
> > > >
> > > >Add a link to stack overflow to the contact page of the website:
> > > >https://pulsar.apache.org/en/contact/
> > > >2.
> > > >
> > > >Add text to the webpage stating that we recommend that if you have a
> > > >technical question, please ask it on Stack Overflow
> > > >3.
> > > >
> > > >On Slack, we encourage them to post their question to Stack Overflow
> > > >
> > > >
> > > > Reasons:
> > > >
> > > >-
> > > >
> > > >We are on the free version of Slack and thus all questions/answers
> > > >before the middle of June are lost (10k messages max).
> > > >-
> > > >
> > > >We answer the same question over and over.
> > > >-
> > > >
> > > >   We want to make it easier for our community to find the answers.
> > > >   -
> > > >
> > > >Developers expect answers to be on Stack Overflow
> > > >-
> > > >
> > > >It is easier to copy and paste an error message into Google and if
> > it
> > > >has been posted to Stack Overflow, then the questioner will find the
> > > answer
> > > >quickly.
> > > >-
> > > >
> > > >   Slack is not searchable by Google, plus we won’t lose the
> > > >   question/answer after 5 weeks
> > > >
> > > >
> > > > Thoughts?
> > > >
> > > > Thanks,
> > > >
> > > > Aaron Williams
> > > >
> > >
> >

Re: gRPC protocol handler

2021-07-27 Thread Sijie Guo

Here are my two cents.

It is great to have more protocol handlers. I'd encourage people to
maintain the protocol handler themselves rather than pushing to the
upstream.

1. It is very hard for the community to maintain all protocol handlers
upstream and keep them updated. Similar situations happen to
connectors. It is also commonly seen in other projects like Spark and
Flink. The creator of the protocol handler is the best person to
maintain the protocol handler. You can grow the community for a given
protocol handler as well. It is how we build and maintain KoP, AoP,
and MoP.

2. gRPC isn't a zero-copy protocol. It is not well suited for
implementing high-throughput streaming services.

3. Unlike KoP, MoP and AoP which are implementing well-known messaging
protocols, the gRPC protocol handler is not an extension to support a
different protocol. It is essentially re-implementing Pulsar's
protocol in gRPC. This leads to a serious problem as it is competing
with the original protocol.  It will confuse the community on what to
use. Instead of introducing another protocol handler to re-implement
Pulsar's protocol, I would suggest discussing whether gRPC is suitable
for Pulsar or how we can involve Pulsar's current protocol.

4. If you want to implement a gRPC based service, an alternative would
be adding a Google Pub/Sub protocol handler to support the protocol of
Google Pub/Sub.

-  Sijie

On Tue, Jul 27, 2021 at 6:56 AM Christophe Bornet
 wrote:
>
> Hi Apache Pulsar community,
>
> I’m a huge fan of the potential that the pluggable protocol handlers
> introduced in Pulsar 2.5 unlock for increasing Pulsar popularity by
> reducing the friction to adopt it. This includes both general-purpose APIs
> like REST and gRPC, and compatibility layers for other streaming products
> like Kafka and AMQP.
>
> I’ve created a PIP
>  and
> an implementation of a gRPC protocol handler, but review of the pull
> request stalled out  so I moved
> my implementation to my own repository
>  while I finished it.
>
> With development and testing effectively complete, I’d like to reopen the
> discussion:
>
>
>1.
>
>How can I move forward with contributing my gRPC protocol handler to
>Apache Pulsar? Is this something that is interesting and useful to the
>broader community?
>2.
>
>More broadly, what policy do we want to establish for Pulsar protocol
>handlers and other compatibility layers?  As indicated above, I think that
>we should provide Pulsar with “batteries included” to make it as easy as
>possible for new users to get started.
>
>
> Best regards.
>
> Christophe

Re: [DISCUSS] Apache Pulsar 2.8.1 Release

2021-07-27 Thread Sijie Guo

+1

On Sat, Jul 24, 2021 at 7:29 AM Hang Chen  wrote:
>
> Hi all,
>
> I hope you've all been doing well. It has been more than one month since we
> released the Apache Pulsar 2.8.0. We have a lot of fixes already merged. So
> I would like to start to prepare our next patch release in the next few
> days.
>
> You can find the whole change list of the 2.8.1 release from:
> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.8.1
>
> If I missed some features, please let me know. And if some PRs can't be
> completed in a few days, the owner can help check if we should include them
> in 2.8.1 or push them to the next release version.
>
> Thanks,
> Hang

Re: [ANNOUNCE] Apache Pulsar Go Client 0.6.0 released

2021-07-27 Thread Sijie Guo

Xiaolong - Congratulations!

Thanks to every contributor for making this happen!

- Sijie

On Sun, Jul 25, 2021 at 10:56 PM Dianjin Wang  wrote:
>
> Congratulations!
>
> Best,
> Dianjin Wang
>
>
> On Mon, Jul 26, 2021 at 11:02 AM r...@apache.org  
> wrote:
>>
>> The Apache Pulsar team is proud to announce Apache Pulsar Go Client version
>> 0.6.0.
>>
>> Pulsar is a highly scalable, low latency messaging platform running on
>> commodity hardware. It provides simple pub-sub semantics over topics,
>> guaranteed at-least-once delivery of messages, automatic cursor management
>> for
>> subscribers, and cross-datacenter replication.
>>
>> For Pulsar release details and downloads, visit:
>> https://github.com/apache/pulsar-client-go/releases/tag/v0.6.0
>>
>> Release Notes are at:
>> https://github.com/apache/pulsar-client-go/blob/master/CHANGELOG.md
>>
>> We would like to thank the contributors that made the release possible.
>>
>> Regards,
>>
>> The Pulsar Team

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

2021-07-27 Thread 丛搏

Hi
Is it a blocker of 2.7.3 release? If not, we can release first, and then
solve this problem later.

Thanks,
Bo

Enrico Olivelli  于2021年7月26日周一 下午10:55写道：

> Hi,
> are you able to run the tests from the source packages ?
> If I run the pulsar-broker test at a certain point (I am still not able to
> see where) my machines starts to use 100% CPU and it is blocked and I need
> to reboot
>
>
> Enrico
>
> Il giorno lun 26 lug 2021 alle ore 09:37 Nozomi Kurihara <
> nkuri...@apache.org> ha scritto:
>
> > +1 (binding)
> >
> > - check signatures/checksums
> > - compile the source
> > - standalone/producer/consumer worked
> > - function/cassandra-connector worked
> >
> > Best Regards,
> > Nozomi
> >
> > 2021年7月26日(月) 16:07 Masahiro Sakamoto :
> >
> > > +1 (binding)
> > >
> > > - Checked checksums and signatures
> > > - Compiled the source
> > > - Ran the standalone server
> > > - Confirmed that producer and consumer work properly
> > > - Confirmed that the sample function works properly
> > >
> > > Regards,
> > >
> > > Masahiro Sakamoto
> > > Yahoo Japan Corp.
> > > E-mail: massa...@yahoo-corp.jp
> > >
> > > -Original Message-
> > > From: 丛搏 
> > > Sent: Wednesday, July 21, 2021 9:00 PM
> > > To: dev@pulsar.apache.org
> > > Subject: [VOTE] Pulsar Release 2.7.3 Candidate 2
> > >
> > > This is the second release candidate for Apache Pulsar, version 2.7.3.
> > >
> > > It fixes the following issues:
> > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.3+is%3Apr+
> > >
> > > *** 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.7.3-candidate-2/
> > >
> > > SHA-512 checksums:
> > >
> > >
> > >
> >
> 323e896bebb2981cc99178e9584273908d5fd9427fa8e907027e8b7c59946cb04a3821af0e70b1a29b0ba166120c493a432fd4d5920e71ccef11e4095f5f30c6
> > >  apache-pulsar-2.7.3-bin.tar.gz
> > >
> > >
> > >
> >
> 4eb2ff4a058fc5f0c0f1352aff926e6125c833c509901a16f93a118540a79a1fc575225b224f1f8ab7ff77c5aeea2a20fe8fedea1717ea249c27c9bbfbb4aae8
> > >  apache-pulsar-2.7.3-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1093/
> > >
> > > The tag to be voted upon:
> > > v2.7.3-candidate-2 (d6c2667ea05339efd8aabf56fe667835b4fe76e9)
> > > https://github.com/apache/pulsar/releases/tag/v2.7.3-candidate-2
> > >
> > > 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 the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > >
> >
>

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

2021-07-27 Thread Enrico Olivelli

Il giorno mer 28 lug 2021 alle ore 06:36 丛搏  ha
scritto:

> Hi
> Is it a blocker of 2.7.3 release? If not, we can release first, and then
> solve this problem later.
>

If tests are not passing then maybe something is broken.
I am not talking about a "flaky test" but something that is blocking the
machine.

for instance recently (a couple of weeks ago), while running the tests on
branch-2.7 I found that delayed delivery was totally broken
https://github.com/apache/pulsar/pull/11374

unfortunately we are cherry-picking commits to branch-2.7 without
validating the patch against CI so every cherry-pick, especially the ones
which do not apply cleanly
may break the stability of the system

I suggest to investigate the problem, and hopefully qualify it as "not a
problem", before closing the VOTE

Pulsar is becoming more and more popular, we must not release something
that we are not sure that cannot be validated.
Unfortunately on 2.7 there are still many flaky tests, but AFAIK the test
suite used to eventually pass

Enrico


>
> Thanks,
> Bo
>
> Enrico Olivelli  于2021年7月26日周一 下午10:55写道：
>
> > Hi,
> > are you able to run the tests from the source packages ?
> > If I run the pulsar-broker test at a certain point (I am still not able
> to
> > see where) my machines starts to use 100% CPU and it is blocked and I
> need
> > to reboot
> >
> >
> > Enrico
> >
> > Il giorno lun 26 lug 2021 alle ore 09:37 Nozomi Kurihara <
> > nkuri...@apache.org> ha scritto:
> >
> > > +1 (binding)
> > >
> > > - check signatures/checksums
> > > - compile the source
> > > - standalone/producer/consumer worked
> > > - function/cassandra-connector worked
> > >
> > > Best Regards,
> > > Nozomi
> > >
> > > 2021年7月26日(月) 16:07 Masahiro Sakamoto :
> > >
> > > > +1 (binding)
> > > >
> > > > - Checked checksums and signatures
> > > > - Compiled the source
> > > > - Ran the standalone server
> > > > - Confirmed that producer and consumer work properly
> > > > - Confirmed that the sample function works properly
> > > >
> > > > Regards,
> > > >
> > > > Masahiro Sakamoto
> > > > Yahoo Japan Corp.
> > > > E-mail: massa...@yahoo-corp.jp
> > > >
> > > > -Original Message-
> > > > From: 丛搏 
> > > > Sent: Wednesday, July 21, 2021 9:00 PM
> > > > To: dev@pulsar.apache.org
> > > > Subject: [VOTE] Pulsar Release 2.7.3 Candidate 2
> > > >
> > > > This is the second release candidate for Apache Pulsar, version
> 2.7.3.
> > > >
> > > > It fixes the following issues:
> > > >
> > > >
> > >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.3+is%3Apr+
> > > >
> > > > *** 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.7.3-candidate-2/
> > > >
> > > > SHA-512 checksums:
> > > >
> > > >
> > > >
> > >
> >
> 323e896bebb2981cc99178e9584273908d5fd9427fa8e907027e8b7c59946cb04a3821af0e70b1a29b0ba166120c493a432fd4d5920e71ccef11e4095f5f30c6
> > > >  apache-pulsar-2.7.3-bin.tar.gz
> > > >
> > > >
> > > >
> > >
> >
> 4eb2ff4a058fc5f0c0f1352aff926e6125c833c509901a16f93a118540a79a1fc575225b224f1f8ab7ff77c5aeea2a20fe8fedea1717ea249c27c9bbfbb4aae8
> > > >  apache-pulsar-2.7.3-src.tar.gz
> > > >
> > > > Maven staging repo:
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1093/
> > > >
> > > > The tag to be voted upon:
> > > > v2.7.3-candidate-2 (d6c2667ea05339efd8aabf56fe667835b4fe76e9)
> > > > https://github.com/apache/pulsar/releases/tag/v2.7.3-candidate-2
> > > >
> > > > 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 the source package, and follow the README to
> build
> > > > and run the Pulsar standalone service.
> > > >
> > >
> >
>

Re: Moving questions from Slack to Stack Overflow

Re: [Doc] Upgrade Docusuraus

Re: Moving questions from Slack to Stack Overflow

gRPC protocol handler

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

Re: Moving questions from Slack to Stack Overflow

Re: Moving questions from Slack to Stack Overflow

[GitHub] [pulsar-client-node] hrsakai opened a new pull request #167: Bump the master version to 1.5.0

[VOTE] Pulsar Node.js Client Release 1.4.0 Candidate 1

[PIP] PIP for the Topic policy across multiple clusters

Re: [PIP] PIP for the Topic policy across multiple clusters

Re: Moving questions from Slack to Stack Overflow

Re: Moving questions from Slack to Stack Overflow

Re: gRPC protocol handler

Re: [DISCUSS] Apache Pulsar 2.8.1 Release

Re: [ANNOUNCE] Apache Pulsar Go Client 0.6.0 released

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

18 matches

Site Navigation

Mail list logo

Footer information