Hi Penghui,
It's caused by the relative path and I explained it that issue. Here
is an improvement for tests:
https://github.com/apache/pulsar-client-cpp/pull/340.
Thanks,
Yunze
that the
localhost should be mapped to 127.0.0.1, while on my macOS localhost
was mapped to IPv6 ::1 first. The test passed after I modified the
/etc/hosts file.
Thanks,
Yunze
On Thu, Nov 9, 2023 at 11:42 AM Yunze Xu wrote:
>
> Hi Penghui,
>
> It's caused by the relative path a
89 ms)
> > [--] 1 test from LookupServiceTest (89 ms total)
> >
> > [--] Global test environment tear-down
> > [==] 1 test from 1 test suite ran. (89 ms total)
> > [ PASSED ] 0 tests.
> > [ FAILED ] 1 test, listed below:
> >
Closing this vote by 3 binding +1s:
- Penghui
- Yunze
- Mattison
Thanks,
Yunze
On Mon, Nov 13, 2023 at 11:14 AM Yunze Xu wrote:
>
> In addition to Mattison's failure. The
> `LookupServiceTest.testMultiAddresses` failed because the HTTP proxy
> is enabled. See https://github.
+1 (binding)
Thanks,
Yunze
On Mon, Nov 13, 2023 at 3:28 PM mattison chao wrote:
>
> +1(binding)
>
> Best,
> Mattison
>
> > On Nov 10, 2023, at 12:12, Cong Zhao wrote:
> >
> > Hi Community,
> >
> > This thread is to start a vote for PIP-318.
> >
> > PIP: https://github.com/apache/pulsar/pull/215
Congrats!
Thanks,
Yunze
On Mon, Nov 13, 2023 at 6:15 PM Zixuan Liu wrote:
>
> Congrats!
>
> Thanks,
> Zixuan
>
> Cong Zhao 于2023年11月13日周一 18:01写道：
>
> > Congrats! Yubiao
> >
> > Thanks,
> > Cong
> >
> > On 2023/11/13 07:36:27 mattison chao wrote:
> > > Dear Community,
> > >
> > > We are thrille
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.4.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
In the latest C++ Client 3.4.0 release, we observed a regression
https://github.com/apache/pulsar-client-cpp/issues/346. It's a
critical bug that a crash could happen for each reconnection.
I pushed a fix (https://github.com/apache/pulsar-client-cpp/pull/347).
After it's merged, I will start the r
+1 (binding)
Thanks,
Yunze
On Thu, Nov 16, 2023 at 11:01 AM Jie crossover wrote:
>
> Hi All, This thread is to start a vote for PIP-303. PIP:
> https://github.com/apache/pulsar/pull/21228 Discussion thread:
> https://lists.apache.org/thread/c92043zq6lyrsd5z1hnln48mx858n7vj
> --
> Best Regards！
>
There is another critical issue introduced by 3.4.0:
https://github.com/apache/pulsar-client-python/issues/162
I will open another fix for it.
Thanks,
Yunze
On Thu, Nov 16, 2023 at 12:45 PM Yunze Xu wrote:
>
> In the latest C++ Client 3.4.0 release, we observed a regression
&
This is the first release candidate for Apache Pulsar Client C++, version 3.4.1.
It fixes the following issues:
https://github.com/apache/pulsar-client-cpp/milestone/7?closed=1
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we are
callback
> method, they will encounter a segmentation fault.
>
> Refer to: https://github.com/apache/pulsar-client-cpp/issues/352
>
>
> Thanks,
> Baodi Shi
>
>
> On Nov 18, 2023 at 00:02:55, Yunze Xu wrote:
>
> > This is the first release candidate for Apache P
I tried building on my Windows 11 via `mvn clean install -DskipTests
-Pcore-modules,-main` (the `-Pxxx` is to skip some modules like
connectors) and it worked well.
- java version "17.0.4" 2022-07-19 LTS
- Maven 3.8.6
I see your project directory is "C:\pulsar" and the lightproto plugin
will gener
This is the second release candidate for Apache Pulsar Client C++,
version 3.4.1.
It fixes the following issues:
https://github.com/apache/pulsar-client-cpp/milestone/7?closed=1
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we ar
+1 (binding)
- Verified checksum and signatures
- Built from source on macOS m1 and dotnet 8.0.100
- Verified an e2e example with the Nuget package
Thanks,
Yunze
On Mon, Nov 20, 2023 at 9:21 PM tison wrote:
>
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version
- Verified the MacOS arm64 pre-build binaries for produce and consume
>
> Thanks
> Yubiao Feng
>
> On Tue, Nov 21, 2023 at 11:40 PM Yunze Xu wrote:
>
> > This is the second release candidate for Apache Pulsar Client C++,
> > version 3.4.1.
> >
> > It fixes t
Closing this vote by 3 binding +1s
- Penghui
- Yubiao
- Yunze
Thanks,
Yunze
On Sun, Nov 26, 2023 at 5:30 PM Yunze Xu wrote:
>
> +1 (binding)
>
> - Verified the checksum and signatures
> - Built from source
> - Verified the pre-built binaries for arm64 on Ubuntu and macOS
>
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.4.1.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
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
, 2023 at 12:51 AM Yunze Xu wrote:
>
> 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 im
gt;
> Any updates on including transaction support on C++ client ?
>
> Thanks & Regards
> Karthikeyan A
>
> -Original Message-
> From: Yunze Xu
> Sent: 17 May 2023 08:33
> To: dev@pulsar.apache.org
> Subject: Re: [ANNOUNCE] Apache Pulsar Client C++ 3.2.
I prefer the 1st way as well.
Thanks,
Yunze
On Tue, Dec 5, 2023 at 5:11 PM Zike Yang wrote:
>
> Hi, everyone,
>
> There seems to be a gap in our current release process concerning the
> pushing of the latest tag to our Docker images. Specifically, we need
> to decide which version of Pulsar the
Hi all,
There is a regression related to OAuth2 authentication for C++ Client
3.4.0 and 3.4.1:
https://github.com/apache/pulsar-client-cpp/issues/363
Generally, for C++ client users, you won't be affected if you
- don't use OAuth2 authentication
- or build the library from source in your platform
Hi Zike,
I found a regression [1] that would affect the Python or Node.js
client if any of them depends on the C++ Client 3.4.1. So I will
prepare a 3.4.2 release soon. Please wait until the C++ client 3.4.2
is released.
[1] https://lists.apache.org/thread/rjolgrlp4x1lmfj678k3hjco80kcb73c
Thanks
This is the first release candidate for Apache Pulsar Client C++, version 3.4.2.
It fixes the following issues:
https://github.com/apache/pulsar-client-cpp/pulls?q=is%3Apr+is%3Aclosed+label%3Arelease%2F3.4.2
*** Please download, test and vote on this release. This vote will stay open
for at least
+1 (binding)
* Verified checksum and signatures
* Build from source with dotnet 8.0.100 on macOS m1
* Verified producing and consuming for the Nuget package
Thanks,
Yunze
On Fri, Dec 8, 2023 at 3:32 PM tison wrote:
>
> +1 (binding)
>
> + Signature and checksum match
> + Download link valid
> +
+1 (binding)
Thanks,
Yunze
On Mon, Dec 11, 2023 at 3:34 PM Asaf Mesika wrote:
>
> Hi,
>
> I'm starting the vote for PIP-320 (1st sub-PIP of PIP-264)
>
> Link: https://github.com/apache/pulsar/pull/21635
>
> Reminder:
> This PIPs goal is to introduce OpenTelemetry into Apache Pulsar. When this
>
+1 (binding)
Thanks,
Yunze
On Mon, Dec 11, 2023 at 2:18 PM Apurva Telang wrote:
>
> +1 (non-binding)
>
> On Sun, Dec 10, 2023 at 6:12 PM guo jiwei wrote:
>
> > +1 (binding)
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia
> > wrote:
> >
> > > H
+1 to me. The Alpine Linux is much more light-weight than Ubuntu.
Thanks,
Yunze
On Wed, Dec 13, 2023 at 3:00 AM Matteo Merli wrote:
>
> Hello,
>
> I've created a new proposal to switch Pulsar base docker images from Ubuntu
> to Alpine Linux.
>
> Details and motivation in the PIP:
> https://githu
4:30 PM tison wrote:
> >
> > > +1 (binding)
> > >
> > > * Download URL valid
> > > * Checksum and sign match
> > > * Can build from source
> > > * LICENSE and NOTICE present
> > >
> > > nit: Years in NOTICE can be updated.
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.4.2.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
IMO, exposing the ledger id and entry id directly through the API is
not a good idea. For example, what if you want to get a chunked
message? You would have to add another field again and deprecate the
existing method.
I think we should just accept a string like
"bk:ledger:entry:batch_index" that
+1 (binding)
For source code,
* verified signatures and checksums
* built from source on macOS (with C++ client 3.4.2)
For the following wheels, verified end-to-end with OAuth2
authentication on specific platforms.
* the wheel built from source (macOS Ventura 13.6.3)
* pulsar_client-3.4.0-cp312-c
Hi all,
Recently I noticed the Pulsar Python client APIs are not friendly to
Python users [1]. The existing asynchronous APIs are based on
callbacks and they are hard to use. Since the Pulsar Python client is
a wrapper on the Pulsar C++ client, wrapping the existing
callback-based APIs for asyncio
Could you include this fix
(https://github.com/apache/pulsar-client-go/pull/1155), which fixes a
CVE?
Thanks,
Yunze
On Wed, Jan 10, 2024 at 3:21 PM Zike Yang wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the version
> 0.12.0, as follows:
> [ ] +1, Approve the r
+1 (binding)
Thanks,
Yunze
On Mon, Jan 15, 2024 at 10:25 AM guo jiwei wrote:
>
> +1 (binding)
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Mon, Jan 15, 2024 at 9:36 AM PengHui Li wrote:
>
> > +1 (binding)
> >
> > Regards,
> > Penghui
> >
> > On Mon, Jan 8, 2024 at 4:00 PM Enrico Olivelli
> > wrot
+1 (binding)
Thanks,
Yunze
On Wed, Jan 17, 2024 at 6:55 PM guo jiwei wrote:
>
> +1 (binding)
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Wed, Jan 17, 2024 at 5:39 PM 太上玄元道君 wrote:
>
> > +1 nonbinding
> >
> >
> > > 2024年1月17日 17:35，Asaf Mesika 写道：
> > >
> > > +1 (non-binding)
> > >
> > > On Tue,
>From my perspective, it's a serious security issue. The client side
could easily make Pulsar's message expiry mechanism not work. Even if
it's not a malicious change made by users, it would be hard to figure
out what makes the message not expired.
> Users can still have a way to disable it if the
over
> > time.
> >
> > > This change can make sure entry expires when client clock is not right.
> >
> > This solution looks good to me.
> >
> > Regards,
> > Penghui
> >
> >
> > On Wed, Jan 17, 2024 at 10:31 PM Yunze Xu wrote:
>
+1 (binding)
Thanks,
Yunze
On Wed, Jan 17, 2024 at 12:37 PM PengHui Li wrote:
>
> +1 (binding)
>
> Regards,
> Penghui
>
> On Wed, Jan 17, 2024 at 11:05 AM guo jiwei wrote:
>
> > +1 (binding)
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Mon, Jan 15, 2024 at 5:50 PM Zixuan Liu wrote:
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
e files, I'd support their
> removal.
>
> Regarding the current 0.12.0 release, before we make a consensus on
> whether we should remove these files. I can update the current version
> in those files in the next release candidate.
>
> Thanks,
> Zike Yang
>
> On
+1 (binding)
- Verified checksum and signatures
- Built from source
- Verified perf tool against a local 3.1.2 standalone
- Verified produce and consume via OAuth2 authentication against
StreamNative cloud
Thanks,
Yunze
On Wed, Jan 24, 2024 at 8:47 PM PengHui Li wrote:
>
> +1 (binding)
>
> - Bu
+1 (binding)
* Verified checksum and signatures
* Built from source on macOS m1 and run examples
* Install the NPM on macOS m1 and connect to StreamNative cloud via
OAuth2 authentication
Thanks,
Yunze
On Mon, Jan 29, 2024 at 6:11 PM Baodi Shi wrote:
>
> Hi everyone,
>
> This is the first releas
-1 (binding)
I observed a regression for Pulsar 3.1.2 recently because the latest
image was just updated yesterday [1]. It seems related to the SSL
hostname verification because the failed tests come from
https://github.com/apache/pulsar-client-cpp/pull/126. I tested the
`technoboy8/pulsar:3.2.0-8
8:41 PM PengHui Li wrote:
>
> It looks like some tests are missed in the Java client?
> Otherwise, the java client detected this break change.
>
> Thanks,
> Penghui
>
> On Fri, Feb 2, 2024 at 11:40 AM Yunze Xu wrote:
>
> > -1 (binding)
> >
> > I ob
I pushed a fix: https://github.com/apache/pulsar/pull/22014
Thanks,
Yunze
On Fri, Feb 2, 2024 at 9:15 PM Yunze Xu wrote:
>
> Yes. I wrote a unit test in Java [1]. This breaking change is
> introduced by #21445 [2], which requires the topic policies to be
> available in `BrokerTo
Hi Dave,
> This would be a commitment by the Pulsar PMC to support third party code.
Well. I think you mean the third party code from StreamNative is not
as reliable as etcd or RocksDB. I agree. The current problem is that
the MetadataStore is not pluggable. What if a personal contributor
contrib
topic policies can
be loaded or updated. To disable this limitation, we should disable
the system topic policy, while it's enabled by default since 2.11 [1].
[1] https://github.com/apache/pulsar/pull/15619
Thanks,
Yunze
On Fri, Feb 2, 2024 at 9:45 PM Yunze Xu wrote:
>
> I pushed a
I would like to propose releasing the Pulsar C++ Client 3.5.0.
It has been about 2 months since the last release (3.4.2). There have
been many new features and bug fixes since then. It's time to release
a new version. I will start the release once
https://github.com/apache/pulsar-client-cpp/pull/4
This is the first release candidate for Apache Pulsar Client C++, version 3.5.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-cpp/milestone/6?closed=1
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we are
Cancel this vote since I want to include the fix to
https://github.com/apache/pulsar-client-python/issues/199 in this
release.
Thanks,
Yunze
On Fri, Mar 1, 2024 at 2:40 PM Yunze Xu wrote:
>
> This is the first release candidate for Apache Pulsar Client C++, version
> 3.5.0.
>
&g
+1 (binding)
- Verified checksum and signatures
- Run OAuth2 e2e examples with 0.12.1-candidate-1
- Built from source and run perf to produce and consume
Thanks,
Yunze
On Thu, Feb 29, 2024 at 11:05 AM Zike Yang wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the
> Our team has also tried to submit multiple
enhancements and also PIP, but most of them are bogged down by
reviewers who are very new to Pulsar, might not understand messaging
correctly, or don’t find such enhancements useful for their usecases.
If your PRs or PIPs are not taken enough care of,
b.com/apache/pulsar/pull/21399#issuecomment-1857889100
Thanks,
Yunze
On Thu, Mar 7, 2024 at 1:57 PM Yunze Xu wrote:
>
> > Our team has also tried to submit multiple
> enhancements and also PIP, but most of them are bogged down by
> reviewers who are very new to Pulsar, might not
My fault for missing the discussion mails for these PIPs because I
didn't check the archives of previous months.
Thanks,
Yunze
On Thu, Mar 7, 2024 at 3:05 PM Lari Hotari wrote:
>
> On Thu, 7 Mar 2024 at 08:14, Girish Sharma wrote:
> > There is for 310 -
> > https://lists.apache.org/thread/13ncs
+1 (binding)
The proposal overall LGTM. But since the PIP itself and its
implementation are coupled in the same PR, I left minor comments in
that PR directly, which does not affect my +1.
Thanks,
Yunze
On Mon, Mar 11, 2024 at 11:04 AM Yubiao Feng
wrote:
>
> +1 (binding)
>
> Thanks
> Yubiao Feng
This is the second release candidate for Apache Pulsar Client C++,
version 3.5.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-cpp/milestone/6?closed=1
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we ar
ilt binaries to build node.js client
>
>
>
>
> Thanks,
> Baodi Shi
>
>
> On Mar 12, 2024 at 10:25:56, Yunze Xu wrote:
>
> > This is the second release candidate for Apache Pulsar Client C++,
> > version 3.5.0.
> >
> > It fixes the following issue
+1 (binding)
- Verified checksum and signatures
- Built from source on macOS m1
- Upgrade the dependency of the python client and verified the issues
are fixed (https://github.com/apache/pulsar-client-python/pull/202)
Thanks,
Yunze
On Thu, Mar 14, 2024 at 6:13 PM Yunze Xu wrote:
>
> The
>
> On Thu, Mar 14, 2024 at 9:12 PM Yunze Xu wrote:
>
> > +1 (binding)
> >
> > - Verified checksum and signatures
> > - Built from source on macOS m1
> > - Upgrade the dependency of the python client and verified the issues
> > are fixed (https:/
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.5.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
I'm afraid many people don't have patience to read all the contents.
Here is my summary in short (please correct me if I'm wrong):
- For bug fixes, the target branch should be branch-3.0. Once the PR
is merged into branch-3.0, checkout the branch-3.x and run `git merge
branch-3.0` and resolve the c
Hi all,
I would like to propose releasing the Pulsar Python client 3.5.0.
It's over two months since the release of 3.4.0, and there are 16 new
commits: https://github.com/apache/pulsar-client-python/compare/v3.4.0...main.
The dependent C++ client was upgraded to 3.5.0 in
https://github.com/apach
Hi community,
I'd like to bring back the discussion again since a similar discussion
happened long ago [1].
Currently, there is no clear definition for the maintain strategy of
public APIs. To make it more clear, I mean "public interface methods"
and "public class methods" when I mentioned "publi
> I think that this is too broad. It would essentially prevent most
> refactorings and improvements to Pulsar.
It makes sense. I will take some time to learn the use of japicmp.
Thanks,
Yunze
On Wed, Mar 20, 2024 at 8:59 PM Lari Hotari wrote:
>
> On Wed, 20 Mar 2024 at 13:50, Yun
wrote:
>
> Thanks for the comments, Yunze.
>
> On 2024/03/18 05:48:39 Yunze Xu wrote:
> > I'm afraid many people don't have patience to read all the contents.
>
> I agree. However, in async work, people should have more patience to read and
> write. Synchron
+1 (binding)
Thanks,
Yunze
On Wed, Mar 20, 2024 at 9:19 PM PengHui Li wrote:
>
> +1 (binding)
>
> Regards.
> Penghui
>
> On Sat, Mar 16, 2024 at 6:28 AM Yubiao Feng
> wrote:
>
> > Hi All
> >
> > This thread is to start a vote for PIP-344.
> >
> > PIP: https://github.com/apache/pulsar/pull/22182
This is the Nth release candidate for Apache Pulsar Client Python,
version 3.5.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-python/milestone/6?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Python wheel
I will cancel this release since I want to add the same API
(`Consumer.get_name())` that is introduced in
https://github.com/apache/pulsar-client-cpp/pull/360.
Thanks,
Yunze
On Fri, Mar 22, 2024 at 2:28 PM Yunze Xu wrote:
>
> This is the Nth release candidate for Apache Pulsar Client
This is the 2nd release candidate for Apache Pulsar Client Python,
version 3.5.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-python/milestone/6?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Python wheel
inding)
>
> - Checked the signature
> - Installed the wheel on macOS with Python 3.12
> - Run the consume and produce examples
>
> Regards,
> Penghui
>
> On Fri, Mar 22, 2024 at 11:55 PM Yunze Xu wrote:
>
> > This is the 2nd release candidate for Apache Pulsar Cl
Hi all,
Recently I found a regression [1] for the C++ client 3.5.0 (thanks to
the reminder from @shibd). So I will push a fix and then release the
C++ client 3.5.1.
However, this is not the 1st time that a regression was introduced,
see [2] for example. So I suggest when verifying the C++ client,
This is the first release candidate for Apache Pulsar Client C++, version 3.5.1.
It fixes the following issues:
https://github.com/apache/pulsar-client-cpp/labels/release%2F3.5.1
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we a
:
https://github.com/apache/pulsar-client-node/pull/370
Thanks,
Yunze
On Thu, Mar 28, 2024 at 4:42 PM Yunze Xu wrote:
>
> This is the first release candidate for Apache Pulsar Client C++, version
> 3.5.1.
>
> It fixes the following issues:
> https://github.com/apache/pulsar
Regarding the `Close` method, I think it's exceptional. It's designed
to return no error so that users can call `defer client.Close()` [1].
To process errors in `Close()`, we can panic in the implementation and
let users use `recover` to catch the panic.
[1] https://github.com/apache/pulsar-client
> This would lead to inconsistency in API definitions, making them
> appear disorganized.
I agree. Using such suffixes is really ugly and much harder to
maintain IMHO. It only makes people add APIs more casually. They might
think, oh, don't worry, if this API (e.g. doSomething()) does not make
sen
; >
> >
> > On Thu, Mar 28, 2024 at 10:38 PM Baodi Shi wrote:
> >
> > > +1(non-binding)
> > >
> > > - Verified signature and checksums
> > > - build from macOS m1 local and run SampleProducer and SampleConsumer
> > >
> > >
> >
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.5.1.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
This is the 3rd release candidate for Apache Pulsar Client Python,
version 3.5.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-python/milestone/6?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Python wheel
(Tboy)
>
>
> On Tue, Apr 2, 2024 at 5:49 PM Yunze Xu wrote:
>
> > This is the 3rd release candidate for Apache Pulsar Client Python,
> > version 3.5.0.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar-client-python/milestone/
+1 (binding)
- Verified signature and checksums
- Built from source on macOS
- Run e2e tests against a local standalone
- Run e2e tests with OAuth2 authentication against an online cluster
Thanks,
Yunze
On Tue, Apr 9, 2024 at 6:26 PM Baodi Shi wrote:
>
> Hi everyone,
>
> This is the first relea
les
> - Built from source on macOS and ran the example
>
> BR,
> Zike Yang
>
> On Thu, Apr 11, 2024 at 6:40 PM Yunze Xu wrote:
> >
> > +1 (binding)
> >
> > - Verified signatures and checksums
> > - Built from source from source on macOS (with C++ c
The Apache Pulsar team is proud to announce Apache Pulsar Client
Python version 3.5.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor manage
Hi all,
Recently I upgraded my downstream project's dependency to the latest
master branch and found no logs are printed now.
```
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
```
Finally I found it's caused by #223
oned, so I used the `` to exclude the org.slf4j
> or org.apache.logging.log4j, and so on.
>
> Do you think this approach is fair?
>
> Thanks,
> Zixuan
>
> Yunze Xu 于2024年4月26日周五 20:41写道：
>
> > Hi all,
> >
> > Recently I upgraded my downstream proj
so be
included on their other projects.
Thanks,
Yunze
On Sat, Apr 27, 2024 at 11:39 AM Yunze Xu wrote:
>
> > we will encounter them sooner or later.
>
> I don't think so. As a logging facade, there is no convincing reason
> to keep it latest unless some CVEs.
>
>
; 2.x, and when the slf4j version is inconsistent, we still need to use
> ``.
>
> Thanks,
> Zixuan
>
> Yunze Xu 于2024年4月27日周六 11:46写道：
>
> > The point is not related to how I should resolve the dependency issue.
> > It is how you care for the downstream users.
>
Please include https://github.com/apache/pulsar/pull/22665 in 3.3.0
because it fixes a regression introduced by PIP-342
(https://github.com/apache/pulsar/pull/22179).
Thanks,
Yunze
On Mon, May 6, 2024 at 11:52 AM Cong Zhao wrote:
>
> Hello Enrico,
>
> Can you list which PRs are important? I see
Please release 3.5.1 rather than 3.4.1 because 3.5.0 is already
released. It's too heavy to maintain old releases for client libraries
for now.
However, it would be better to remove the `functions` component from
pulsar-client-python because the Python client itself never uses these
dependencies.
python/requirements.txt`.
Here is an example:
```
pulsar-client == 3.5.0
protobuf>=3.6.1,<=3.20.3
grpcio >= 1.60.0
apache-bookkeeper-client>=4.16.1
prometheus_client
ratelimit
```
Thanks,
Yunze
On Sat, May 11, 2024 at 12:19 PM Yunze Xu wrote:
>
> Please release 3.5.1 rather
Hi all,
Currently, the pre-built RPM packages are built on CentOS 7 with GCC
4.8 to keep the binary compatibility with CentOS 7 users. A breaking
ABI change was changed since GCC 5 though users can add the
`-D_GLIBCXX_USE_CXX11_ABI=0` option to keep the compatibility.
In short, for GCC>=5, to lin
;
> Yes, the current Python client will cause a particularly long time(2 hours)
> to build a pulsar ARM image.
>
> > If yes, a quicker way to fix it was to add a `requirements.txt` that
> includes a proper
> version of grpcio and then run `python -m pip install -r
> python/requi
-1 (binding)
There seems something wrong with the docker image, see
https://github.com/BewareMyPower/pulsar-client-cpp/actions/runs/9121814458/job/25082141665?pr=31
After upgrading the dependency, the Pulsar standalone in CI of
pulsar-client-cpp cannot be started (always stuck in waiting for the
+1 (binding)
Thanks,
Yunze
On Sun, May 26, 2024 at 10:14 PM thetumbled wrote:
>
> Hi, Pulsar Community.
> I would like to start the voting thread for PIP-354: apply topK mechanism
> to ModularLoadManagerImpl.
> Proposal PR: https://github.com/apache/pulsar/pull/22765
> Implementation PR:
Hi community,
Recently I found the behavior of seeking a multi-topics consumer is
intuitive. If there are no internal consumers, the `seek` call will
just succeed silently.
If a consumer subscribes with a regex and no topics are found, users
might think the seek operation succeeds while no topics
aodi Shi ha
> scritto:
>
> > +1
> >
> >
> > Thanks,
> > Baodi Shi
> >
> >
> > On May 29, 2024 at 14:50:12, Yunze Xu wrote:
> >
> > > Hi community,
> > >
> > > Recently I found the behavior of seeking a multi-to
er,
> no exception is thrown when a regex consumer subscribes without any
> topics.
>
> I prefer not to break the current behavior as it's probably not a bug.
> Alternatively, we could introduce a new option for users who do not
> want to seek on the consumer without a
+1 (binding)
- Verified signature and checksums
- Verified the docker image with the C++ client
(https://github.com/BewareMyPower/pulsar-client-cpp/pull/31)
- Built from source with JDK 17 on macOS
- Verified standalone with produce and consume
Thanks,
Yunze
On Wed, Jun 5, 2024 at 4:28 AM Andrey
+1 (binding)
Thanks,
Yunze
On Wed, Jun 5, 2024 at 6:25 PM thetumbled wrote:
>
> Hi PengHui,
> The current design is not to remove the old one directly, but deprecate it.
> We are still comptible with the old cluster in following way:
> - If a configuration is not the default configuration, use
101 - 200 of 654 matches
Mail list logo
