tisonkun commented on PR #184:
URL: https://github.com/apache/pulsar-site/pull/184#issuecomment-1231241190
It seems this patch causes build failed: +
/pulsar/site2/tools/pulsar-admin-doc-gen.sh /pulsar/site2/website-next
--
This is an automated message from the Apache Git Service.
To
tisonkun commented on PR #184:
URL: https://github.com/apache/pulsar-site/pull/184#issuecomment-1231241530
@urfreespace we may revert this patch first to unblock site build and
digging what cause the failure later.
--
This is an automated message from the Apache Git Service.
To respond to
Hi Michael,
Thanks for your verification.
I tried to recreate the issue, but I can't reproduce this.
Here is my steps:
- wget
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.5-candidate-3/apache-pulsar-2.7.5-src.tar.gz
- tar -xvf apache-pulsar-2.7.5-src.tar.gz
- cd apache-pulsar-2.7.5
- m
+1
Reactive is a perfect fit for streaming platforms.
Le lun. 29 août 2022 à 15:11, Lari Hotari a écrit :
> I updated it to be PIP-205 since there was a previous reference of
> PIP-204. :)
>
> -Lari
>
> On 2022/08/29 12:55:43 Lari Hotari wrote:
> > Hi all,
> >
> > I have drafted PIP-204: Reactiv
I support the initiative, especially because I guess we will need someday
to build a new native Java client and do not wrap the existing one.
Also, Pulsar must be on that ecosystem with a strong presence.
Enrico
Il Lun 29 Ago 2022, 15:11 Lari Hotari ha scritto:
> I updated it to be PIP-205 sinc
Hi Lari,
No specific reason that compares to the separated repo solution.
IMO, it depends on the number of proposals to be processed.
If we have more than 200 proposals per year,
I will say `don't use the Pulsar main repo` with certainty
I also have no objection to the separated repo solution.
>
Hi Michael,
I also couldn't reproduce it with the same steps Haiting provided.
Here is my local environment info with `mvn -v`
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /Users/didi/Documents/apache-maven-3.6.3
Java version: 1.8.0_291, vendor: Oracle Corporation,
labuladong opened a new pull request, #188:
URL: https://github.com/apache/pulsar-site/pull/188
Two style improvements:
**1. Improve dark mode table view:**
Original:
https://user-images.githubusercontent.com/37220920/187413231-71732844-72f6-4149-91a4-b6a0a4736cb9.png";>
labuladong commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1231474877
Maybe this light-style table can be improved:
https://user-images.githubusercontent.com/37220920/187413231-71732844-72f6-4149-91a4-b6a0a4736cb9.png";>
This dark-styl
tisonkun commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1231480563
@labuladong this change looks good :)
--
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 devs,
This is the VOTE thread for PIP-204 Extensions for BrokerInterceptor.
PIP issue: https://github.com/apache/pulsar/issues/17267
Discussion thread:
https://lists.apache.org/thread/3zgpbxffo7gzsb5mdh0sk2rq27bgw2bo
This voting will open for at least 72h.
Best,
Aloys
labuladong commented on PR #188:
URL: https://github.com/apache/pulsar-site/pull/188#issuecomment-1231524446
PTAL @urfreespace
--
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 commen
+1
Aloys Zhang 于2022年8月30日周二 19:02写道：
> Hi devs,
>
> This is the VOTE thread for PIP-204 Extensions for BrokerInterceptor.
>
> PIP issue: https://github.com/apache/pulsar/issues/17267
>
> Discussion thread:
> https://lists.apache.org/thread/3zgpbxffo7gzsb5mdh0sk2rq27bgw2bo
>
> This voting will
claudio-vellage opened a new pull request, #286:
URL: https://github.com/apache/pulsar-helm-chart/pull/286
### Motivation
Currently it's not possible to use selectors with volumeClaimTemplates which
makes it hard/impossible to bind statically provisioned PVs.
### Modifications
>
> I think they merged all the approved proposals?
So only approved PIPs will be merged - like they do in Rust.
Unapproved PIPs can be shown with a query like they do in Rust:
https://github.com/rust-lang/rfcs/issues?q=is%3Aclosed+is%3Aunmerged
And I can also find the md files
https://github.
>
> The problem I thought of not merging the PR proposal is the proposal looks
> like the proposed changes never end. The author can continue to update
> after approved. I don't want to say all the changes to the proposal need to
> be voted on
> the mailing list, but we should get a chance to revie
SignorMercurio commented on PR #184:
URL: https://github.com/apache/pulsar-site/pull/184#issuecomment-123196
I see. I'll fix this soon.
--
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 spe
Anonymitaet commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1231563414
@labuladong +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 to the specific comm
>
> I'd like to add a new aspect to the proposal: there might be other
> solutions that would be useful in the case of large amount of topics in a
> Pulsar cluster.
> Rate limiting on the /metrics endpoint doesn't sound like the correct
> approach.
>
> When there's a huge about of metrics, instead
+1 (binding)
Enrico
Il giorno mar 30 ago 2022 alle ore 13:24 lin chen
ha scritto:
>
> +1
>
> Aloys Zhang 于2022年8月30日周二 19:02写道：
>
> > Hi devs,
> >
> > This is the VOTE thread for PIP-204 Extensions for BrokerInterceptor.
> >
> > PIP issue: https://github.com/apache/pulsar/issues/17267
> >
> >
Pulsar CI continues to be congested, and the build queue is long.
I would strongly advice everyone to use "personal CI" to mitigate the issue of
the long delay of CI feedback. You can simply open a PR to your own personal
fork of apache/pulsar to run the builds in your "personal CI". There's mor
mendonk closed pull request #186: [fix][doc]Fix Elasticsearch compatibilityMode
configurations
URL: https://github.com/apache/pulsar-site/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 th
tisonkun commented on PR #188:
URL: https://github.com/apache/pulsar-site/pull/188#issuecomment-1231633215
cc @Anonymitaet this is the patch for
https://github.com/apache/pulsar-site/issues/173#issuecomment-1231474877
--
This is an automated message from the Apache Git Service.
To respond
SignorMercurio opened a new pull request, #189:
URL: https://github.com/apache/pulsar-site/pull/189
Fix website build error caused by #184.
The reason is currently under investigation.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
+1
Having a reactive client for Pulsar would be very useful and would
strengthen Pulsar as a project going forward.
Best,
Alexander
On Tue, Aug 30, 2022 at 9:42 AM Enrico Olivelli wrote:
> I support the initiative, especially because I guess we will need someday
> to build a new native Java cli
I agree with that PUSH/PULL/REMOTE_WRITE are requires Flow-Control.
I don’t if the broker has the problem when there are more than 10K topics,
but, if we need expose serval hundred MBs metrics data, It will definitely lead
to network usage sudden increase.
Thanks,
Tao Jiuming
> 下面是被转发的邮件：
>
> 发
dave2wave opened a new issue, #190:
URL: https://github.com/apache/pulsar-site/issues/190
The page fails with
https://user-images.githubusercontent.com/29803617/187482644-1981ebaa-a4cb-4235-b0f2-09fcc887bfe2.png";>
```
Refused to apply style from
'https://fonts.googleapis.com/cs
zebehringer commented on issue #87:
URL:
https://github.com/apache/pulsar-client-node/issues/87#issuecomment-1231856933
this fixed me:
```
export LDFLAGS=-L/opt/homebrew/lib
export CFLAGS=-I/opt/homebrew/include
export CPPFLAGS=-I/opt/homebrew/include
```
--
This is an auto
+1 for a native reactive client for Pulsar. This would enable downstream
libraries (such as Spring for e.g.) to provide a choice between regular and
reactive Java clients. Looking forward to this addition.
Best regards,
Soby Chacko
On Tue, Aug 30, 2022 at 9:45 AM Alexander Preuss
wrote:
> +1
>
+1
--
Matteo Merli
On Mon, Aug 29, 2022 at 5:56 AM Lari Hotari wrote:
>
> Hi all,
>
> I have drafted PIP-204: Reactive Java client for Apache Pulsar.
>
> PIP link:
> https://github.com/apache/pulsar/issues/17335
>
> Here's a copy of the contents of the GH issue for your references:
>
> Motivat
gurleen-gks closed pull request #485: Bug fixes for mtls support
URL: https://github.com/apache/pulsar-manager/pull/485
--
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 unsub
+1
On Tue, Aug 30, 2022 at 9:37 AM Matteo Merli wrote:
> +1
>
>
> --
> Matteo Merli
>
>
> On Mon, Aug 29, 2022 at 5:56 AM Lari Hotari wrote:
> >
> > Hi all,
> >
> > I have drafted PIP-204: Reactive Java client for Apache Pulsar.
> >
> > PIP link:
> > https://github.com/apache/pulsar/issues/173
urfreespace merged PR #188:
URL: https://github.com/apache/pulsar-site/pull/188
--
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.a
urfreespace commented on PR #187:
URL: https://github.com/apache/pulsar-site/pull/187#issuecomment-1232332755
> @urfreespace can answer definitively, but I think that this PR needs to be
made in https://github.com/apache/pulsar/tree/master/site2/docs which is
synchronized to this repository
urfreespace merged PR #187:
URL: https://github.com/apache/pulsar-site/pull/187
--
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.a
urfreespace commented on issue #190:
URL: https://github.com/apache/pulsar-site/issues/190#issuecomment-1232335455
![Uploading image.png…]()
@dave2wave seems it working well now. could you have the test again?
--
This is an automated message from the Apache Git Service.
To respond t
urfreespace merged PR #189:
URL: https://github.com/apache/pulsar-site/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-unsubscr...@pulsar.a
tisonkun opened a new pull request, #192:
URL: https://github.com/apache/pulsar-site/pull/192
This file is removed from the main repo by
https://github.com/apache/pulsar/pull/17306.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
urfreespace merged PR #191:
URL: https://github.com/apache/pulsar-site/pull/191
--
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.a
+1
Thanks,
Haiting
On Tue, Aug 30, 2022 at 8:26 PM Enrico Olivelli wrote:
> +1 (binding)
>
>
> Enrico
>
> Il giorno mar 30 ago 2022 alle ore 13:24 lin chen
> ha scritto:
> >
> > +1
> >
> > Aloys Zhang 于2022年8月30日周二 19:02写道：
> >
> > > Hi devs,
> > >
> > > This is the VOTE thread for PIP-204 E
+1
Best regards,
Zixuan
Joe F 于2022年8月31日周三 08:53写道：
> +1
>
> On Tue, Aug 30, 2022 at 9:37 AM Matteo Merli
> wrote:
>
> > +1
> >
> >
> > --
> > Matteo Merli
> >
> >
> > On Mon, Aug 29, 2022 at 5:56 AM Lari Hotari wrote:
> > >
> > > Hi all,
> > >
> > > I have drafted PIP-204: Reactive Java cl
+1
Regards
Jiwei Guo (Tboy)
On Wed, Aug 31, 2022 at 10:22 AM Zixuan Liu wrote:
> +1
>
> Best regards,
> Zixuan
>
> Joe F 于2022年8月31日周三 08:53写道：
>
> > +1
> >
> > On Tue, Aug 30, 2022 at 9:37 AM Matteo Merli
> > wrote:
> >
> > > +1
> > >
> > >
> > > --
> > > Matteo Merli
> > >
> > >
> > > On
I made a PR for this idea, see https://github.com/apache/pulsar/pull/17129
Please help review if you have time, thanks!
Zixuan
Zixuan Liu 于2022年8月15日周一 13:18写道：
> Thank Qiang for your explanation!
>
> Qiang Huang 于2022年8月14日周日 12:15写道：
>
>> LGTM. They are very similar.
>> The OpenJDK provides
urfreespace merged PR #193:
URL: https://github.com/apache/pulsar-site/pull/193
--
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.a
> What you mean by that?
I just want to confirm the rfc is merged to the codebase :)
> I guess that by converting the PIP from issue to PR you're forcing a
review
of any changes, right, especially PIPs that were already approved there by
making sure no drastic changes are being made.
Yes, correc
Hi Lin,
For the producer_request_hold policy, users should set the infinite publish
timeout.
It is not like moving the create producer timeout to publish message
timeout.
The key point that we want to improve is to provide consistent behavior to
users.
For example, we have a producer that has bee
Thank you both for verifying it on your end. After debugging this for
a way too long tonight, I discovered my mistake was using Java 11
instead of Java 8. It didn't occur to me that the different versions
could/would result in a different set of dependencies.
When I use Java 8, this command passes
This is an interesting result. It would be great if the download page after
this release is made would indicate JDK versions.
Thanks!
Dave
Sent from my iPhone
> On Aug 30, 2022, at 10:46 PM, Michael Marshall wrote:
>
> Thank you both for verifying it on your end. After debugging this for
> a
48 matches
Mail list logo
