momo-jun commented on code in PR #547:
URL: https://github.com/apache/pulsar-site/pull/547#discussion_r1180205691
##########
versioned_docs/version-2.9.x/concepts-messaging.md:
##########
@@ -518,19 +518,19 @@ 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 {@inject:
javadoc:MessageRoutingMode:/client/org/apache/pulsar/client/api/MessageRoutingMode}
available:
+There are three
[MessageRoutingMode](api/client/org/apache/pulsar/client/api/MessageRoutingMode)
available:
Mode | Description
:--------|:------------
`RoundRobinPartition` | If no key is provided, the producer will publish
messages across all partitions in round-robin fashion to achieve maximum
throughput. Please note 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. While if a key is specified on the message, the partitioned producer
will hash the key and assign message to a particular partition. This is the
default mode.
`SinglePartition` | If no key is provided, the producer will randomly pick
one single partition and publish all the messages into that partition. While if
a key is specified on the message, the partitioned producer will hash the key
and assign message to a particular partition.
-`CustomPartition` | Use custom message router implementation that will be
called to determine the partition for a particular message. User can create a
custom routing mode by using the [Java client](client-libraries-java.md) and
implementing the {@inject:
javadoc:MessageRouter:/client/org/apache/pulsar/client/api/MessageRouter}
interface.
+`CustomPartition` | Use custom message router implementation that will be
called to determine the partition for a particular message. User can create a
custom routing mode by using the [Java client](client-libraries-java.md) and
implementing the
[MessageRouter](api/client/org/apache/pulsar/client/api/MessageRouter)
interface.
### Ordering guarantee
The ordering of messages is related to MessageRoutingMode and Message Key.
Usually, user would want an ordering of Per-key-partition guarantee.
-If there is a key attached to message, the messages will be routed to
corresponding partitions based on the hashing scheme specified by
[HashingScheme](/api/client/org/apache/pulsar/client/api/HashingScheme) in
{@inject:
javadoc:ProducerBuilder:/client/org/apache/pulsar/client/api/ProducerBuilder},
when using either `SinglePartition` or `RoundRobinPartition` mode.
+If there is a key attached to message, the messages will be routed to
corresponding partitions based on the hashing scheme specified by
[HashingScheme](/api/client/org/apache/pulsar/client/api/HashingScheme) in
[ProducerBuilder](api/client/org/apache/pulsar/client/api/ProducerBuilder),
when using either `SinglePartition` or `RoundRobinPartition` mode.
Review Comment:
Oops.. Thanks for spotting this. Resolved.
--
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: commits-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
