[Bug] Topic level geo configure, the partitioned topics can not auto created on remote cluster.
- 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
2.10.5
### Minimal reproduce step
1. Create a Topic with partition 2 on cluster1
`bin/pulsar-admin topics create-partitioned-topic -p 2 public/geo-1/test-1`
2. Topic level GEO Configure
`bin/pulsar-admin topics set-replication-clusters -c cluster1,cluster2 public/geo-1/test-1`
3. View the list of partitioned topics and non-partitioned topics in Cluster2.
```
bin/pulsar-admin topics list-partitioned-topics public/geo-1
empty
bin/pulsar-admin topics list public/geo-1
public/geo-1/test-1-partition-0
public/geo-1/test-1-partition-1
```
### What did you expect to see?
View the list of partitioned topics and non-partitioned topics in Cluster2.
```
bin/pulsar-admin topics list-partitioned-topics public/geo-1
public/geo-1/test-1
bin/pulsar-admin topics list public/geo-1
public/geo-1/test-1-partition-0
public/geo-1/test-1-partition-1
```
### What did you see instead?
View the list of partitioned topics and non-partitioned topics in Cluster2.
```
bin/pulsar-admin topics list-partitioned-topics public/geo-1
empty
bin/pulsar-admin topics list public/geo-1
public/geo-1/test-1-partition-0
public/geo-1/test-1-partition-1
```
Partitioned topics are not created in the remote cluster.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Reproduce the issue with the listed pulsar-admin commands for a partitioned topic and topic-level replication between cluster1 and cluster2. Trace the code paths behind set-replication-clusters, list-partitioned-topics, and remote topic creation; done means cluster2 lists the partitioned topic and both partition topics as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100