I found a breaking change in version 2.9.2 https://github.com/apache/pulsar/pull/14409
The change is introduced by https://github.com/apache/pulsar/pull/12786 Policies.is_allow_auto_update_schema changed from boolean to Boolean, this may cause user's code get NPE. I'd like to start a discusstion about the solution. We could add a new interface with `applied` parameter, but this also introduce inevitable break change. And I suggest to do this with PIP in the next major version release. For version 2.9.2, we need merge 14409 to avoid return null value. Wangjialing From: Ran Gao Date: 2022-02-17 02:26 To: dev Subject: [VOTE] Pulsar Release 2.9.2 Candidate 3 This is the third release candidate for Apache Pulsar, version 2.9.2. *** 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.9.2-candidate-3/ SHA-512 checksums: 21ab21df057dc181d02806e67a8d85b861fa60a8413a8e4058ffcb738d9ef81d8797c4e7249d50cf2a23c7437cb2880f4240d010a983eda33a2071f5fddf6b01 apache-pulsar-2.9.2-bin.tar.gz f927d77aba32d1112cd009a1d91a8fca27a49fcb20ea215a5792dc16e2b04bd822238c3f29dd81a7853e20062a0454e2abe608626b24e4e25ff06915b7a04785 apache-pulsar-2.9.2-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1141/ The tag to be voted upon: v2.9.2-candidate-3 (5615809ffd68599ae7fec1be0679ee83171f42dc) https://github.com/apache/pulsar/releases/tag/v2.9.2-candidate-3 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source package, and follow the README to build and run the Pulsar standalone service.
