Thanks, WangJialing, Penghui Li.
After the PR 14409 merged, I'll start the Pulsar 2.9.2 candidate 4.
On 2022/02/23 04:05:30 PengHui Li wrote:
> Looks it will affect the 2.8.3 and 2.10.0 releases,
>
> > We could add a new interface with `applied` parameter, but this also
> introduce inevitable br
Looks it will affect the 2.8.3 and 2.10.0 releases,
> 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.
htt
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 discusstio
+1 (binding)
- Check signatures/checksums
- Check the license headers
- build sources
- Validate Pub/Sub and Java Functions
- Validate Stateful Functions
Regards,
Hiroyuki
From: Ran Gao
Sent: Thursday, February 17, 2022 03:26
To: dev@pulsar.apache.org
Subj
+1 (binding)
- Checked the signature
- Build from the source
- Start the standalone
- Publish and consume messages
- Check the Cassandra connector
- Check the stateful function
Thanks for the great work,
Penghui
On Thu, Feb 17, 2022 at 2:26 AM Ran Gao wrote:
> This is the third release candida
