SignorMercurio commented on PR #160:
URL: https://github.com/apache/pulsar-site/pull/160#issuecomment-1214340328
In addition, a minor fix of an old problem (#134, #142) is committed here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
You can see
https://lists.apache.org/thread/rg1g083c06ozm5go6zo1jophg9y9zl2f
for more details about the LTS release.
Thanks,
Yunze
> 2022年8月14日 11:00，Qiang Huang 写道：
>
> +1 (non-binding)
> Is 2.8.4 a long term support release?
>
> Yunze Xu 于2022年8月12日周五 16:20写道：
>
>> This is the first rel
Technically, the regexp of both conventions are:
* Angular convention - /^(\w*)(?:\((.*)\))?!?: (.*)$/
* Customized conventions - /^\[(\w*)\](?:\[(.*)\])?: (.*)$/
So, there're technically equal from the customized convention perspective,
or the Angular convention contains all expressiveness of th
To clarify, I don't have a strong feeling about either convention.
According to the reason above, I'd prefer the Angular convention, while +0
for the customized convention.
Best,
tison.
tison 于2022年8月14日周日 23:40写道：
> Technically, the regexp of both conventions are:
>
> * Angular convention - /
urfreespace commented on PR #160:
URL: https://github.com/apache/pulsar-site/pull/160#issuecomment-1214503274
thanks @SignorMercurio, good job, LGTM
--
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
urfreespace merged PR #160:
URL: https://github.com/apache/pulsar-site/pull/160
--
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
SignorMercurio opened a new pull request, #161:
URL: https://github.com/apache/pulsar-site/pull/161
Add execute permission on pulsar-config-doc-gen.sh. @urfreespace
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
Got it. Thx.
Yunze Xu 于2022年8月14日周日 23:22写道：
> You can see
> https://lists.apache.org/thread/rg1g083c06ozm5go6zo1jophg9y9zl2f
> for more details about the LTS release.
>
> Thanks,
> Yunze
>
>
>
>
> > 2022年8月14日 11:00，Qiang Huang 写道：
> >
> > +1 (non-binding)
> > Is 2.8.4 a long term support rele
I support this motivation. We should avoid any cases which
might break the at-least-one delivery semantic from the user's perspective.
Thanks,
Penghui
On Thu, Aug 11, 2022 at 1:36 PM Michael Marshall
wrote:
> Hi Pulsar Community,
>
> In Pulsar 2.5.0, the semantics for a message's redeliveryCoun
Great idea, Michael
> 1. A new producer connecting to a topic that has exceeded its quota.
> This case is trivial because the broker tells the producer it is
> connected but it cannot send any messages (i.e. producer_ready=false),
> and the client holds the producer's future until the broker sends
Thank Qiang for your explanation!
Qiang Huang 于2022年8月14日周日 12:15写道：
> LGTM. They are very similar.
> The OpenJDK provides source-code, and the Temurin JDK provides builds of
> the source code.
> I would like to point out that they have different licenses.
> - The OpenJDK implementation is licen
Good idea.
> Good idea. I suggest the naming endings with `Seconds` like
> sendDelayOfTwoPhaseDeletionInSeconds,`
> reconsumeLaterOfTwoPhaseDeletionInSeconds`.
> >private int sendDelaySecondsOfTwoPhaseDeletion = 60;
> >private int reconsumeLaterSecondsOfTwoPhaseDeletion = 600;
urfreespace merged PR #161:
URL: https://github.com/apache/pulsar-site/pull/161
--
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
13 matches
Mail list logo
