EugenDueck commented on a change in pull request #5995: [docs] improve statement on ordering guarantees for multi-topic subscriptions URL: https://github.com/apache/pulsar/pull/5995#discussion_r363932512
########## File path: site2/docs/concepts-messaging.md ########## @@ -226,8 +226,8 @@ When a consumer subscribes to a Pulsar topic, by default it subscribes to one sp When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created. -> #### No ordering guarantees -> When a consumer subscribes to multiple topics, all ordering guarantees normally provided by Pulsar on single topics do not hold. If your use case for Pulsar involves any strict ordering requirements, we would strongly recommend against using this feature. +> #### No cross-topic ordering guarantees +> Ordering guarantees given for single topics do not hold across multiple topics. So users need to make sure that all messages that need to be delivered in order are on the same topic. Review comment: Imo something like "cross-topic ordering" or "ordering across topics" makes it more clear than "multiple topics" that in-topic ordering is not affected by this. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
