[Bug] The data returned by the "/non-persistent/{tenant}/{namespace}" interface does not seem to be correct
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
apache-pulsar-2.11.0
### Minimal reproduce step
```
./pulsar-admin topics create-partitioned-topic \
non-persistent://my-tenant/my-namespace/my-non-topic \
--partitions 4
```
```
./pulsar-admin topics list my-tenant/my-namespace
```
### What did you expect to see?
`./pulsar-admin topics list my-tenant/my-namespace` should return the non-persistent topics just created
### What did you see instead?
`./pulsar-admin topics list my-tenant/my-namespace` returns nothing
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start by reproducing the issue with the shown pulsar-admin topics create-partitioned-topic command, then run pulsar-admin topics list for the same tenant and namespace. Trace the /non-persistent/{tenant}/{namespace} interface and compare its handling with the topic-creation path; done means the list command returns the created non-persistent topics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100