-1 from my side.
Explanation: I didn't notice until now that the "lookup service address" (now
brokerId ) was modified for 3.2.0 in this PR
https://github.com/apache/pulsar/pull/21015 based on this issue report
https://github.com/apache/pulsar/issues/21012 .
I'm waiting for answers on the ques
Hi,
Currently we are able to peek at any number of messages using the Pulsar
Java Admin API.
However, we are only able to view these messages starting from the most
recent message. If we want to view the 100th message, we have to peek at
all the top 100 messages.
We want to display these message
Close this vote with three bindings.
- Jiwei Guo (Tboy)
- Penghui
- Yubiao Feng
On Fri, Jan 19, 2024 at 6:31 PM Yubiao Feng
wrote:
> +1 (binding)
>
> Thanks
> Yubiao Feng
>
> On Tue, Jan 16, 2024 at 2:41 PM Xiangying Meng
> wrote:
>
> > Dear Pulsar community,
> >
> > I am initiating a voting t
+1 (binding)
Thanks
Yubiao Feng
On Tue, Jan 16, 2024 at 2:41 PM Xiangying Meng wrote:
> Dear Pulsar community,
>
> I am initiating a voting thread for "PIP-321: Split the responsibilities of
> namespace replication-clusters".
>
> Here is the pull request for PIP-321:
> https://github.com/apache
The VERSION file is still 0.11.1, which is not updated. But it seems
that this VERSION file is not used anywhere. I checked the stats and
found the "clientVersion" is "Pulsar Go v0.12.0-candidate-2", which is
expected.
I see https://github.com/apache/pulsar-client-go/pull/856 supports
getting the
