Hello community, I'd like to discuss the current behaviour for the auto creation of non persistent topics. Currently, the broker flag "allowAutoTopicCreation" (can be overridden at namespace/topic policy level) controls if persistent and non-persistent topics can be created implicitly.
I believe that flag should only control persistent topics auto creation. Non persistent topics are meant to be volatile. If a producer is connected to a broker and the broker goes down, then the producer has to recreate the topic when the broker eventually comes up again. There are cases when the administrator wants to disable auto topic creation for persistent topics and let non-persistent topics work as expected. Currently the only workaround is to enable auto creation. My proposal is to let the option "enableNonPersistentTopics" to be responsible for auto creation of non persistent topics, as if it's a requirement for non persistent topics to work properly. This would target Pulsar 3.1.0 and it will require a PIP There's already a pretty old issue that might need to be renamed - https://github.com/apache/pulsar/issues/5631 Another slightly related point - which could be addressed in another moment - is that non persistent topics are not configurable at namespace/topic level. Please let me know what you think Thanks, Nicolò Boschi
