Hi all,
When I ran unit tests for the pulsar-client-cpp repo, which uses
`apachepulsar/pulsar:latest` image to start a standalone, I found the
tests failed and the following error [1]:
```
standalone The requested image's platform (linux/arm64) does not match
the detected host platform (linux/amd
Hi Rajan and Girish,
Thanks for your reply. About the question you mentioned, there is some
information I want to share with you.
>If anyone wants to setup different replication clusters then either
>those topics can be created under different namespaces or defined at topic
>level policy.
>And use
I found Matteo has updated 3.1.1 as the latest image:
https://hub.docker.com/layers/apachepulsar/pulsar/latest/images/sha256-21e8bf1571e4ab559a51b3f6e524d725cffabe3c6836101f9d7ea7eb1e2bf62c?context=explore
But the 3.0.2 still lacks the image for the amd64 platform.
Thanks,
Yunze
On Mon, Dec 4, 2
We need to use the following commands to push the images:
```sh
regctl image copy 9947090/pulsar:3.0.2-12c92fe apachepulsar/pulsar:3.0.2
regctl image copy 9947090/pulsar-all:3.0.2-12c92fe apachepulsar/pulsar-all:3.0.2
```
It's missing in the release doc. I will update it later.
Thanks,
Zike Yang
>if users want to change the replication policy for
topic-n and do not change the replication policy of other topics, they need
to change all the topic policy under this namespace.
This PIP unfortunately flows from attempting to solve bad application
design
A namespace is supposed to represent
Hi Rajan,
Thanks for sharing the link! I will follow the PR.
Best Regards,
Nikolai
On 2023/12/02 01:21:04 Rajan Dhabalia wrote:
> Hi Nikolai,
>
> I completely understand your concern and pain. But let's understand
> ordering semantics for exclusive/fail-over subscription. This
subscription
Hi all,
I would like to propose releasing the Pulsar Python client 3.4.0.
It's over three months since the release of 3.3.0, and there are 46 new commits:
https://github.com/apache/pulsar-client-python/compare/v3.0.0...main
The Pulsar C++ client 3.4.1 has been released. I have upgraded the C++
c
Hi,
We have a requirement where the message has been consumed from one topic,
processed it and written to another topic in single transaction.
Looks like transaction support related client APIs in C++ is still not
available and that is in roadmap of pulsar delivery.
Please let us know the de
