> If it only affects standalone. I think it’s ok. Right.
> For standalone, multiple bundles help nothing, right? I'm wondering whether affecting the resource quota. Could you confirm that? Thanks, Zixuan PengHui Li <codelipeng...@gmail.com> 于2022年12月7日周三 12:53写道： > Hi Zixuan, > > If it only affects standalone. I think it’s ok. > For standalone, multiple bundles help nothing, right? > No rebalance will happen for a standalone. > > Thanks, > Penghui > > > On Dec 7, 2022, at 11:23, Yunze Xu <y...@streamnative.io.INVALID> wrote: > > > > The change of a default value is acceptable in a major release. But > > since it's changed back in the next 2.12 release, it could be a little > > confusing. My perspective is to include this PR in the 2.11.0 release. > > > > Thanks, > > Yunze > > > > On Wed, Dec 7, 2022 at 11:00 AM Zixuan Liu <node...@gmail.com> wrote: > >> > >> Pulsar 2.11 standalone breaks the bundle of namespace policy. I'm > wondering > >> whether blocking the Pulsar 2.11 release. > >> > >> See https://github.com/apache/pulsar/pull/18755 > >> > >> Thanks, > >> Zixuan > >> > >> Enrico Olivelli <eolive...@gmail.com> 于2022年12月6日周二 21:26写道： > >> > >>> +1 (binding) > >>> - verified checksums, digests > >>> - built from sources > >>> - tested the docker image built from sources and the docker image > >>> provided as convenience with the VOTE > >>> - run successfully the Jakarta JMS 2.0 TCK against those two docker > images > >>> > >>> My problem with the JMS TCK is that the behaviour of "delete topic" > >>> with "force=true" changed, and now if the topic does not exist we get > >>> a 404 error, in Pulsar 2.10.x the response code was 200 > >>> I think that this behaviour change is acceptable in a major release, > >>> and that actually the new behaviour is more consistent. > >>> > >>> More details here: > >>> https://github.com/datastax/pulsar-jms/pull/101 > >>> > >>> Thank you for driving the release > >>> > >>> Enrico > >>> > >>> Il giorno lun 5 dic 2022 alle ore 16:21 Enrico Olivelli > >>> <eolive...@gmail.com> ha scritto: > >>>> > >>>> FYI I am investigating some errors I see while running the Jakarta JMS > >>>> TCK against a Pulsar 2.11.0rc2 server with the provided docker images. > >>>> > >>>> I still can't understand the problem, so I will keep you posted. > >>>> > >>>> Please hold on > >>>> > >>>> Enrico > >>>> > >>>> Il giorno dom 4 dic 2022 alle ore 19:13 Christophe Bornet > >>>> <bornet.ch...@gmail.com> ha scritto: > >>>>> > >>>>> +1 (non-binding) > >>>>> > >>>>> - Start docker image standalone > >>>>> - Test HTTP Sink > >>>>> - Test Transformation Function > >>>>> > >>>>> Best regards > >>>>> > >>>>> Christophe > >>>>> > >>>>> Le lun. 28 nov. 2022 à 13:57, guo jiwei <techno...@apache.org> a > >>> écrit : > >>>>> > >>>>>> This is the second release candidate for Apache Pulsar, version > >>> 2.11.0. > >>>>>> > >>>>>> This release contains 1574 commits by 64 contributors. > >>>>>> > >>> https://github.com/apache/pulsar/compare/v2.10.2...v2.11.0-candidate-2 > >>>>>> > >>>>>> CI for this release candidate > >>>>>> https://github.com/Technoboy-/pulsar/pull/14 > >>>>>> > >>>>>> *** Please download, test and vote on this release. This vote will > >>> stay > >>>>>> open > >>>>>> for at least 72 hours *** > >>>>>> > >>>>>> Note that we are voting upon the source (tag), binaries are provided > >>> for > >>>>>> convenience. > >>>>>> > >>>>>> Source and binary files: > >>>>>> > >>> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.11.0-candidate-2 > >>>>>> > >>>>>> SHA-512 checksums: > >>>>>> > >>>>>> > >>>>>> > >>> > 199eb731bad0635fbc0388adf090e8c60ce189634e6b1692a12cfdf43f15347371d79c42d040b91dd7b2d0302061ad48bff850638e3bb48540ab24908792dd5e > >>>>>> > >>>>>> ./apache-pulsar-2.11.0-bin.tar.gz > >>>>>> > >>>>>> > >>>>>> > >>> > 035d5a656cdd4c2430ae4f7c4fef952ad05e432219a64474fcfaa097fcc7ad6cd76fd82b77e91d667e0ec8495c35fc08a5bb25a54058ccdfaf4072a22b94f6d7 > >>>>>> > >>>>>> ./apache-pulsar-2.11.0-src.tar.gz > >>>>>> > >>>>>> Maven staging repo: > >>>>>> > >>> > https://repository.apache.org/content/repositories/orgapachepulsar-1192/ > >>>>>> < > >>> > https://repository.apache.org/content/repositories/orgapachepulsar-1190/> > >>>>>> > >>>>>> The tag to be voted upon: > >>>>>> v2.11.0-candidate-2 (c0a823a242a834dac35b9a6fcd6a2064a0e4bfb5) > >>>>>> https://github.com/apache/pulsar/releases/tag/v2.11.0-candidate-2 > >>>>>> > >>>>>> Pulsar's KEYS file containing PGP keys we use to sign the release: > >>>>>> https://dist.apache.org/repos/dist/dev/pulsar/KEYS > >>>>>> > >>>>>> Docker images: > >>>>>> > >>>>>> > >>> > https://hub.docker.com/layers/mattison/pulsar-all/2.11.0-rc2/images/sha256-1b6b04673d62ccefe6fd6eed27a001ef8a9607668fcc5fb79459fed73f07e9e4 > >>>>>> > >>>>>> > >>> > https://hub.docker.com/layers/mattison/pulsar/2.11.0-rc2/images/sha256-21a4afa5a83ed5780c2d4986a3e13bc9d43142614f610434d5d304c1d61a65eb > >>>>>> > >>>>>> Please download the source package, and follow the > >>>>>> release-candidate-validation doc to build > >>>>>> and run the Pulsar standalone service. > >>>>>> https://pulsar.apache.org/contribute/validate-release-candidate > >>>>>> > >>>>>> Since the metadata store is changed from ZK to RocksDB, the > >>> verification of > >>>>>> the `stateful functions` needs to set the parameter "export > >>>>>> PULSAR_STANDALONE_USE_ZOOKEEPER=1" > >>>>>> > >>>>>> > >>>>>> Regards > >>>>>> Jiwei Guo (Tboy) > >>>>>> > >>> > >
