+1
Best,
Max Xu
On Thu, Jul 28, 2022 at 9:35 AM Yu wrote:
> +1 since it improves the efficiency of managing docs.
>
> On Thu, Jul 28, 2022 at 8:16 AM M Jun wrote:
>
> > Hi, Pulsar community,
> >
> > I'd like to start a vote on PIP-190: Simplify Pulsar documentation
> release
> > and mainten
+1 (non-binding)
This will greatly reduce the amount of work that contributors have to
do to update and maintain the documentation.
Thanks
Zike Yang
On Thu, Jul 28, 2022 at 4:04 PM Max Xu wrote:
>
> +1
>
>
> Best,
>
> Max Xu
>
>
> On Thu, Jul 28, 2022 at 9:35 AM Yu wrote:
>
> > +1 since it impr
MonicaMagoniCom opened a new issue, #283:
URL: https://github.com/apache/pulsar-helm-chart/issues/283
Why in the template broker-statefulset.yaml the value for
`podManagementPolicy` if fixed to `Parallel`? Couldn't it be taken from
values.yaml?
--
This is an automated message from th
Hi, Pulsar community,
I'd like to start a vote on PIP-193 : Sink preprocessing Function
You can find the proposal at https://github.com/apache/pulsar/issues/16739 and
the discussion thread at
https://lists.apache.org/thread/qn59jwn47w9ngxpkvq3kswbl1y882jth.
The vote will stay open for at least 4
Nice feature!
-- Original --
From: "Yunze Xu"https://github.com/apache/pulsar/pull/6796 for discussion.
Currently, the Java client acknowledges the specific partition of the
message ID, while the C++ client just fails when calling
`acknowledgeCumulative` on a pa
SignorMercurio opened a new pull request, #154:
URL: https://github.com/apache/pulsar-site/pull/154
Improve brodocs style to work with apache/pulsar#16853.
--
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
SignorMercurio commented on PR #154:
URL: https://github.com/apache/pulsar-site/pull/154#issuecomment-1198129310
@urfreespace PTAL
--
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 com
+1 (binding)
Thank you
I am sure that this feature will have a huge impact on Pulsar IO users
Enrico
Il giorno gio 28 lug 2022 alle ore 12:39 Christophe Bornet
ha scritto:
>
> Hi, Pulsar community,
>
> I'd like to start a vote on PIP-193 : Sink preprocessing Function
>
> You can find the propo
IMHO a better solution would be to allow the bundles to be split into more
units in a single operation. Instead of splitting one bundle into 2, split it
into 4 or 8….. If we do that then we can make that configurable (with a
reasonable default).
On 2022/07/26 08:39:29 lordcheng10 wrote:
> When
corymacd opened a new pull request, #475:
URL: https://github.com/apache/pulsar-manager/pull/475
### Motivation
Attempting to use this section of the documentation, the intent of the
initial documented link to localhost was clear but the implementation failed to
include the port
iTech-dhananjay commented on issue #227:
URL:
https://github.com/apache/pulsar-client-node/issues/227#issuecomment-1198574681
+1 bump
--
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
michaeljmarshall merged PR #475:
URL: https://github.com/apache/pulsar-manager/pull/475
--
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...@
Hi, Qiang
> It is necessary to check the current cursor status when handling flowPermits
> request from the server side. If the server is handling seek request, it
> should ignore flowPermits request because the request is illegal.
Thanks for your explanation. I think it's better to add this
expl
> They can use `reconsumeLaterCumulative ` for non shared sub instead
It means this is a breaking change. Users have to be noticed during
upgrading.
IMO, what we have to be clear is if we should insist on message
order delivery
with the default exclusive subscription type. If it's true, we would
Sherlock113 opened a new pull request, #155:
URL: https://github.com/apache/pulsar-site/pull/155
Add the Qraft case study link.
Preview image:
![Screen Shot 2022-07-29 at 10 24
34](https://user-images.githubusercontent.com/65327072/181670024-4b9b07aa-2c22-4a4a-bc84-185dd24a2f63.png
I'd like to discuss the current behavior before making a decision.
First, note that it's currently valid for an exclusive consumer to
call `acknowledge` on an individual message. `reconsumeLater` is
essentially just `send` with a delay then `acknowledge`.
Second, the RetryTopicTest#testRetryTopic
michaeljmarshall merged PR #155:
URL: https://github.com/apache/pulsar-site/pull/155
--
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...@pul
+1
Penghui
On Jul 28, 2022, 20:14 +0800, lordcheng10 <1572139...@qq.com.invalid>, wrote:
> Nice feature!
>
>
>
>
> -- Original --
> From: "Yunze Xu" Date: 2022Äê7ÔÂ15ÈÕ(ÐÇÆÚÎå) ÍíÉÏ6:04
> To: "dev" Subject: [DISCUSS] User-friendly acknowledgeCumulative API on a part
+1 (binding)
Penghui
On Jul 28, 2022, 16:40 +0800, Zike Yang , wrote:
> +1 (non-binding)
> This will greatly reduce the amount of work that contributors have to
> do to update and maintain the documentation.
>
> Thanks
> Zike Yang
>
> On Thu, Jul 28, 2022 at 4:04 PM Max Xu wrote:
> >
> > +1
> >
>
Congrats, Micheal
Penghui
On Jul 28, 2022, 02:45 +0800, dev@pulsar.apache.org, wrote:
>
> Congratulations, Micheal !!!
We should also add a part for observability. Add some metrics to the delayed
index buckets and snapshots will help users to tune the
configurations.
And please add a section to describe the upgrade and downgrade.
+1 for the proposal
Penghui
On Jul 27, 2022, 23:50 +0800, Cong Zhao , wrote:
> Hi
Hi haiting,
I see #11992 was closed, and we’d better onboard #16326 in 2.7.5
For the merged PRs with label "release/2.7.6"
We should change them to "release/2.7.5"
Penghui
Thanks,
Penghui
On Jul 27, 2022, 19:13 +0800, Haiting Jiang , wrote:
> Hi all,
>
> > There are 4 closed PRs targeting 2.7.5
+1 (binding)
Penghui
On Jul 25, 2022, 13:42 +0800, mattison chao , wrote:
> +1(non-binding)
>
> Best,
> Mattison
>
> On Mon, 25 Jul 2022 at 13:19, guo jiwei wrote:
> >
> > +1
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Mon, Jul 18, 2022 at 10:54 AM PengHui Li wrote:
> >
> > > +1
> > >
>
Sound good to me.
Please also update the proposal for schema handling.
Thanks,
Penghui
Penghui
On Jul 24, 2022, 17:53 +0800, Haiting Jiang , wrote:
> Hi Penghui,
>
> > One question about the schema.
> > How can the consumer get the schema from the shadow topic during
> > consumption?
> > We shou
Thank you all! I really enjoy working on Pulsar with each of you, and
I look forward to contributing in a new way as a PMC member.
Thanks,
Michael
On Fri, Jul 29, 2022 at 12:03 AM PengHui Li wrote:
>
> Congrats, Micheal
>
> Penghui
> On Jul 28, 2022, 02:45 +0800, dev@pulsar.apache.org, wrote:
>
25 matches
Mail list logo
