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
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
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 a
+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
>
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
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.
>
>
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
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 multipl
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: Pr
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
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 mes
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 rea
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 t
+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 ?
>
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 str
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
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, the
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-Meet
18 matches
Mail list logo