NPE when get isAllowAutoUploadSchema

[gaozhangmin]

Motivation

there were some potential NPE bug when get null value by pulsar-admin

Caused by: java.lang.NullPointerException
        at org.apache.pulsar.broker.admin.impl.NamespacesBase.internalGetIsAllowAutoUpdateSchema(NamespacesBase.java:2423) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
        at org.apache.pulsar.broker.admin.v2.Namespaces.getIsAllowAutoUpdateSchema(Namespaces.java:1631) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]

Modifications

1、set default value true to is_allow_auto_update_schema in Policies as same as ServiceConfiguration
2、changes from boolean to Boolean, long to Long, prevent potential NPE.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)

[github-actions]

@gaozhangmin:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

[github-actions]

@gaozhangmin:Thanks for providing doc info!

[hezhangjian]

I think that we may make a break change of client API.
before we change: client throws an exception
after we change: client raised an NPE

Am I correct?
cc @codelipenghui @mattisonchao

[gaozhangmin]

I think that we may make a break change of client API. before we change: client throws an exception after we change: client raised an NPE

Am I correct? cc @codelipenghui @mattisonchao

I think print null value by pulsar-admin client has no problem We don't need to make this change.

[hezhangjian]

I think that we may make a break change of client API. before we change: client throws an exception after we change: client raised an NPE
Am I correct? cc @codelipenghui @mattisonchao

I think print null value by pulsar-admin client has no problem We don't need to make this change.

People can use pulsar admin not only in terminal, can use it in code.

[gaozhangmin]

/pulsarbot run-failure-checks

[gaozhangmin]

@codelipenghui PTAL

[codelipenghui]

@gaozhangmin Looks like #12786 not released yet) introduced the problem, but from the stack you have provided, looks like it happens in 2.9.1.