shulaoh opened a new issue, #22608:
URL: https://github.com/apache/pulsar/issues/22608

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) 
and found nothing similar.
   
   
   ### Read release policy
   
   - [X] I understand that unsupported versions don't get bug fixes. I will 
attempt to reproduce the issue on a supported version of Pulsar client and 
Pulsar broker.
   
   
   ### Version
   
   pulsar 3.0.1
   jdk 8
   
   ### Minimal reproduce step
   
   1. create 2 clusters with local zk.
   2. create tenant, namespace, topic on each cluster.
   3. pulsar-admin topics set-replication-clusters --clusters 
cluster-A,cluster-B to setup topic-level geo replication
   4. create consumer with Schema.STRING.
   client.newConsumer(Schema.STRING).consumerName("a1")
                           .subscriptionName("ca1")
                           .topic("persistent://aa/bb/cc")
                           .replicateSubscriptionState(true)
                           .messageListener((c, m) -> {
                               System.out.println("message: " + m.getValue());
                               try {
                                   c.acknowledge(m);
                               } catch (ClientException e) {
                                   throw new RuntimeException(e);
                               }
                           }).subscribe();
   
   ### What did you expect to see?
   
   consumer can be registered succesfully.
   
   ### What did you see instead?
   
   Topic does not have schema to check
   
   ### Anything else?
   
   btw, namespace-level geo replication works well.
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to