+1 (binding) - Built from source - Checked the signatures - Run standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function
Regards Jiwei Guo (Tboy) On Sun, Feb 4, 2024 at 3:42 PM Yunze Xu <x...@apache.org> wrote: > I changed my binding -1 to +0 now. > > This behavior change is implicit but acceptable. The previous way of > setting up standalone should be wrong but it just accidentally works. > When system topic policy is enabled, the `brokerClientXxx` arguments > must be configured correctly to ensure the system 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 <x...@apache.org> wrote: > > > > I pushed a fix: https://github.com/apache/pulsar/pull/22014 > > > > Thanks, > > Yunze > > > > On Fri, Feb 2, 2024 at 9:15 PM Yunze Xu <x...@apache.org> 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 `BrokerTopic#getTopic`. > > > > > > However, when the built-in client is not configured correctly, e.g. > > > `brokerClientXxx` authentication arguments are not configured > > > correctly, `BrokerService#getTopicPoliciesBypassSystemTopic` will > > > always fail, which makes `BrokerService#getTopic` fail. > > > > > > [1] > https://github.com/BewareMyPower/pulsar/commit/eab7002299764765ef43f7d6d63a4bd993bba9c0 > > > [2] https://github.com/apache/pulsar/pull/21445 > > > > > > Thanks, > > > Yunze > > > > > > On Fri, Feb 2, 2024 at 8:41 PM PengHui Li <peng...@apache.org> 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 <x...@apache.org> wrote: > > > > > > > > > -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-8025763` image locally and found the tests > > > > > still failed. You can also check the CI test result [2]. > > > > > > > > > > Currently, I'm debugging locally to see why the tests failed. > Before > > > > > figuring it out, we should prevent this release. > > > > > > > > > > [1] > > > > > > https://github.com/apache/pulsar-client-cpp/pull/392#issuecomment-1922698516 > > > > > [2] https://github.com/apache/pulsar-client-cpp/pull/394 > > > > > > > > > > Thanks, > > > > > Yunze > > > > > > > > > > On Thu, Feb 1, 2024 at 8:57 AM PengHui Li <peng...@apache.org> > wrote: > > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > - Built from source > > > > > > - Checked the signatures > > > > > > - Run standalone > > > > > > - Checked producer and consumer > > > > > > - Verified the Cassandra connector > > > > > > - Verified the Stateful function > > > > > > > > > > > > Regards, > > > > > > Penghui > > > > > > > > > > > > On Wed, Jan 31, 2024 at 11:40 PM guo jiwei <techno...@apache.org> > wrote: > > > > > > > > > > > > > This is the fifth release candidate for Apache Pulsar version > 3.2.0. > > > > > > > > > > > > > > It fixes the following issues: > > > > > > > https://github.com/apache/pulsar/milestone/36?closed=1 > > > > > > > > > > > > > > *** Please download, test and verify on this release. This > vote will > > > > > stay > > > > > > > open for at least 72 hours *** > > > > > > > > > > > > > > Note that we are verifying upon the source (tag), binaries are > > > > > provided for > > > > > > > convenience. > > > > > > > > > > > > > > Source and binary files: > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-5/ > > > > > > > > > > > > > > SHA-512 checksums: > > > > > > > > > > > > > > > > > > > > > > > > > > > 194b3a4d51b972ec58c8f2ae4ccaadb3cac229984ea5e7e8a396a1210d4b3adde83ab30ef31c9aa384942f81959da91ab250f5689cd010b4ae71a2b10956af2c > > > > > > > > > > > > > > apache-pulsar-3.2.0-bin.tar.gz > > > > > > > > > > > > > > > > > > > > > > > > > > > 7248f2566627d772093204a61ae2ea87b58dd18f374d2fd624827eb95f4102bfe07b2be87a4e7b6c7c296c5791af623f308885bfbe89069d10620f9da73ded93 > > > > > > > > > > > > > > apache-pulsar-3.2.0-src.tar.gz > > > > > > > > > > > > > > Maven staging repo: > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1265/ > > > > > > > > > > > > > > The tag to verify: > > > > > > > v3.2.0-candidate-5 (802576372132617b5076a44004846f2dbabede08) > > > > > > > https://github.com/apache/pulsar/commits/v3.2.0-candidate-5/ > > > > > > > > > > > > > > Pulsar's KEYS file containing PGP keys you use to sign the > release: > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > > > > > > > > > Docker images: > > > > > > > > > > > > > > pulsar images: > > > > > > > > > > > > > > > > > > > > https://hub.docker.com/layers/technoboy8/pulsar/3.2.0-8025763/images/sha256-4666cc754439a2e6844569bb500365ded382b81d8fc9d4552e3c435702b59d86?context=repo > > > > > > > < > > > > > > > > > > > > > https://hub.docker.com/layers/mattison/pulsar/3.1.0-candidate-1/images/sha256-0efbaad7d893cc5041a46a2d4d56432bda855ae4068a38349777d1be6e98d27d?context=explore > > > > > > > > > > > > > > > pulsar-all images: > > > > > > > > > > > > > > > > > > > > https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-8025763/images/sha256-b308fd819298bb2badc20ecd86547c43a7c8652aebd716816c7f8f24dbb1b34e?context=repo > > > > > > > > > > > > > > Please download the source package, and follow the README to > build > > > > > > > and run the Pulsar standalone service. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > Jiwei Guo (Tboy) > > > > > > > > > > > > >
