codelipenghui merged PR #255:
URL: https://github.com/apache/pulsar-helm-chart/pull/255
--
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...@
nkurihar merged PR #208:
URL: https://github.com/apache/pulsar-client-node/pull/208
--
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...@puls
Hi Pulsar community,
I create a PIP to optimize metadataPosition in MLPendingAckStore to use less
memory and avoid OOM.
The proposal can be
found: https://github.com/apache/pulsar/issues/15073 ;
Thanks,
xiangying Meng
+1
link : https://github.com/apache/pulsar/issues/15073
Thanks!
Bo
xiangying Meng <1984997...@qq.com.invalid> 于2022年4月11日周一 17:27写道:
>
> Hi Pulsar community,
>
>
> I create a PIP to optimize metadataPosition in MLPendingAckStore to use less
> memory and avoid OOM.
> The proposal can be
> found
jaggerwang opened a new issue, #256:
URL: https://github.com/apache/pulsar-helm-chart/issues/256
**Describe the bug**
When tried to login manager, it always shows "The username or password is
incorrect".
![image](https://user-images.githubusercontent.com/1255011/162713833-85b0882e-28a
For old version that doesn't support `start_message_id_inclusive`, should I
fix the client side?
You mean that call the hasMessageAvailable method in new consumer and
reader?
PengHui Li 于2022年4月11日周一 09:10写道:
> Hi zixuan,
>
> The proposal looks good,
> regarding the compatibility, should we ch
This way is right.
PengHui Li 于2022年4月11日周一 09:12写道:
> > regarding the compatibility, should we check the protocol version at the
> client side?
> The old version version doesn't support `start_message_id_inclusive` which
> means the
> client side still needs to do the seek operation while reque
michaeljmarshall commented on PR #205:
URL:
https://github.com/apache/pulsar-helm-chart/pull/205#issuecomment-1095662863
@pellicano @ckdarby - are you able to rebase and then take a look at the
failing status checks? Once that happens, I think we can merge this. Thanks!
--
This is an aut
+1
Looks like a very useful feature. Thank you.
Best,
Mattison
On Mon, 11 Apr 2022 at 08:55, PengHui Li wrote:
> +1
>
> Penghui
>
> On Sat, Apr 9, 2022 at 4:24 PM Haiting Jiang
> wrote:
>
> > Hi Pulsar community,
> >
> > I created a PIP to add support for subscription level dispatch rate
> >
+1
Zixuan
mattison chao 于2022年4月12日周二 09:24写道:
> +1
>
> Looks like a very useful feature. Thank you.
>
> Best,
> Mattison
>
> On Mon, 11 Apr 2022 at 08:55, PengHui Li wrote:
>
> > +1
> >
> > Penghui
> >
> > On Sat, Apr 9, 2022 at 4:24 PM Haiting Jiang
> > wrote:
> >
> > > Hi Pulsar community,
tuteng merged PR #448:
URL: https://github.com/apache/pulsar-manager/pull/448
--
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.apa
tuteng merged PR #444:
URL: https://github.com/apache/pulsar-manager/pull/444
--
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.apa
tuteng closed issue #443: Simplify the classpath in the bin/pulsar-manager
script
URL: https://github.com/apache/pulsar-manager/issues/443
--
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 specifi
13 matches
Mail list logo