Pulsar allows creating duplicate topics with the same name

[deltasquare4]

Describe the bug
Pulsar 2.5.0 allows creating two topics (one partitioned, and the other non-partitioned) with the same name through Admin API. This behaviour is consistent across both persistent and non-persistent topics.

To Reproduce
Steps to reproduce the behavior:

1. Create a partitioned topic in a tenant/namespace (e.g. persistent://public/test/duplicate-test)
2. Create a non-partitioned topic in tenant/namespace by the same name as above

Expected behavior
Aamin API should return HTTP 409 with the following response, like it does if the order of steps above is reveresed:

{
    "reason": "This topic already exists"
}

Additional context
It does not allow topics with duplicate names as expected when reversing the order of steps above (create non-partitioned topic first, and then try to create partitioned topic by the same name. Response with HTTP 409 as described above)

Additionally, both topics do exist and show up in their respective list API calls. When trying to publish messages to the topic, they always seem to be received by the partitioned topic. If partitioned topic is removed, the publish still succeeds, and the messages go to the non-partitioned topic by the same name.

[sijie]

@deltasquare4 thank you for reporting this. Are you interested in contributing a fix?

[codelipenghui]

This issue is fixed by #5943 and I have double-checked on the master branch. So close this issue first, if the problem is still there, please reopen it.