Hello, I have a use case in which my application MUST use a non-partitioned topic to work properly, but the topic name is (of course) configurable by the user. If I am not using a non-partitioned topic, I do not have string guarantees on the ordering of the message (because messages will be spread across multiple partitions).
Currently there is no way to require that the topic IS a NON-PARTITIONED topic. Especially when the topic does not exist yet, you configured the namespace to create partitioned topics by default. Using a PulsarAdmin preliminary call is not a good workaround because it is expensive, and ideally I want to be able to create the Producer (or the Consumer) and see that everything works automatically, failing in case of a partitioned topic. Thoughts ? Enrico
