merlimat commented on a change in pull request #3263: Improve documentation for
message routing mode
URL: https://github.com/apache/pulsar/pull/3263#discussion_r244442690
##########
File path: site2/docs/concepts-messaging.md
##########
@@ -199,15 +199,22 @@ Partitioned topics need to be explicitly created via the
[admin API](admin-api-o
When publishing to partitioned topics, you must specify a *routing mode*. The
routing mode determines which partition---that is, which internal topic---each
message should be published to.
-There are three routing modes available by default:
+There are three {@inject:
javadoc:MessageRoutingMode:/client/org/apache/pulsar/client/api/MessageRoutingMode}
available by default:
-Mode | Description | Ordering guarantee
-:----|:------------|:------------------
-Key hash | If a key property has been specified on the message, the
partitioned producer will hash the key and assign it to a particular partition.
| Per-key-bucket ordering
-Single default partition | If no key is provided, each producer's message will
be routed to a dedicated partition, initially random selected | Per-producer
ordering
-Round robin distribution | If no key is provided, all messages will be routed
to different partitions in round-robin fashion to achieve maximum throughput. |
None
+Mode | Description
+:--------|:------------
+RoundRobinPartition | Publish messages across all partitions in round-robin
fashion to achieve maximum throughput. This is the default mode.
Review comment:
It might be worth specifying that round-robin is not done per individual
message but rather it's set to the same boundary of batching delay, to ensure
batching is effective.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
