Sorry for the confusion. After checking more details, the fix makes more sense. For more cases, user think it's a bug if you can grant permission to a non-existent topic. I will verify this release today.
Thanks, Penghui On Tue, May 28, 2024 at 4:33 PM PengHui Li <peng...@apache.org> wrote: > Hi Cong, > > Thanks for driving the release. > This PR https://github.com/apache/pulsar/pull/22547 has changed the > behavior of > permission operations on a topic. > > The issue is it will break the user's case which relies on the lazy > auto-creation of the topic. > They can grant permission to the topic but the topic will only be created > if the producer or consumer is connected > The namespace level permission may not work because some topics need to be > closed down further. > > I would like to revert this change first, and then we can find a good > solution in the next release > > Regards, > Penghui > > On Mon, May 27, 2024 at 11:33 AM Cong Zhao <zhaoc...@apache.org> wrote: > >> Thanks Yong, >> >> Yes, we can continue to release 3.3 and fix this issue in later versions. >> >> On 2024/05/27 03:10:18 Yong Zhang wrote: >> > If the snappy in zookeeper is not used very commonly, this might not be >> a >> > blocker for this release. >> > >> > So I would be -0. >> > >> > Thanks, >> > Yong >> > On Fri, 24 May 2024 at 15:17, Yong Zhang <zhangyong1025...@gmail.com> >> wrote: >> > >> > > -1 >> > > >> > > There is an issue with the snappy usage in the amd64-based image. >> > > >> > > It will get the error >> > > >> > > java.lang.UnsatisfiedLinkError: /tmp/ >> > > snappy-1.1.10-b0757287-8557-44b9-9499-afca52f102ec-libsnappyjava.so: >> > > Error relocating /lib/ld-linux-x86-64.so.2: unsupported relocation >> type 37. >> > > >> > > Reproduce steps: >> > > 1. docker run -it -u root --platform=linux/amd64 >> > > czcoder/pulsar:3.3.0-0771f81 bash >> > > 2. export >> > > PULSAR_EXTRA_OPTS="-Dzookeeper.snapshot.compression.method=snappy" >> > > 3. export PULSAR_STANDALONE_USE_ZOOKEEPER=true >> > > 4. bin/pulsar standalone -nss -nfw >> > > >> > > Then you will get the error. More information: >> > > https://github.com/sgerrand/alpine-pkg-glibc/issues/194 >> > > >> > > we need to resolve it before publishing the new release. >> > > >> > > Yong >> > > >> > > On Fri, 24 May 2024 at 13:00, guo jiwei <techno...@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 >> > >> Jiwei Guo (Tboy) >> > >> >> > >> >> > >> On Fri, May 24, 2024 at 10:28 AM Cong Zhao <zhaoc...@apache.org> >> wrote: >> > >> >> > >> > Hello Apache Pulsar Community, >> > >> > >> > >> > This is a call for the vote to release the Apache Pulsar version >> 3.3.0 >> > >> > based on 3.3.0-candidate-3. >> > >> > >> > >> > Included changes since the previous release: >> > >> > https://github.com/apache/pulsar/milestone/38?closed=1 >> > >> > >> > >> > *** Please download, test and vote on this release. This vote will >> stay >> > >> > open >> > >> > for at least 72 hours *** >> > >> > >> > >> > Only votes from PMC members are binding, but members of the >> community >> > >> are >> > >> > encouraged to test the release and vote with "(non-binding)". >> > >> > >> > >> > Note that we are voting upon the source (tag), binaries are >> provided for >> > >> > convenience. >> > >> > >> > >> > The release candidate is available at: >> > >> > >> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.3.0-candidate-3/ >> > >> > >> > >> > SHA-512 checksums: >> > >> > >> > >> > >> > >> >> 59fcf6e77ef47ea88696bc1a0f67dc09f0d3f2d791d23e09ff721678beb5512f58bbfb328bbb2980981243aff1aeda686c332b4d8c57dc0c4bffc0ec0a4dbb4d >> > >> > >> > >> > >> > >> >> b35fb4d9d20111f55b7d9c7016871daab0fe8edb2f09220e013fc51b2d828c482a05a7b19b3b1cd39bd2072162f77c3279722c9fdf3e876f22e90e2aea10c9e3 >> > >> > >> > >> > Maven staging repo: >> > >> > >> https://repository.apache.org/content/repositories/orgapachepulsar-1297 >> > >> > >> > >> > The tag to be voted upon: >> > >> > v3.3.0-candidate-3 (commit >> 0771f818ba74f94b95cd0987997079d0f3e73f94) >> > >> > https://github.com/apache/pulsar/releases/tag/v3.3.0-candidate-3 >> > >> > >> > >> > Pulsar's KEYS file containing PGP keys you use to sign the release: >> > >> > https://downloads.apache.org/pulsar/KEYS >> > >> > >> > >> > Docker images: >> > >> > docker pull czcoder/pulsar:3.3.0-0771f81 >> > >> > >> > >> > >> > >> >> https://hub.docker.com/layers/czcoder/pulsar/3.3.0-0771f81/images/sha256-e34f1e83bb2a1e8233a3429847bb8fc2cdac0f558a0e5c13658c28773287b07c?context=explore >> > >> > docker pull czcoder/pulsar-all:3.3.0-0771f81 >> > >> > >> > >> > >> > >> >> https://hub.docker.com/layers/czcoder/pulsar-all/3.3.0-0771f81/images/sha256-49cf20acab7e71c8916cf594690c86eaaaf8426c8a13013a8c25944338d7be7c?context=explore >> > >> > >> > >> > Please download the source package, and follow the README to build >> > >> > and run the Pulsar standalone service. >> > >> > >> > >> > More advanced release validation instructions can be found at >> > >> > https://pulsar.apache.org/contribute/validate-release-candidate/ >> > >> > >> > >> > Thanks, >> > >> > Cong Zhao >> > >> > >> > >> >> > > >> > >> >
