Consistent Hash doc improvement

Mention in the docs that `hash-header` and `hash-property` are mutually exclusive.
This commit is contained in:
Artem Bilan 2024-07-09 10:47:02 -04:00 committed by GitHub
parent 6a989d3ea1
commit 8b7ba05f32
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions

View File

@ -573,10 +573,11 @@ ok.
### Routing on a Message Property
In addition to a value in the header property, you can also route on the
Instead of a value in the header property, you can route on the
``message_id``, ``correlation_id``, or ``timestamp`` message properties. To do so,
declare the exchange with a string argument called ``"hash-property"`` naming the
property to be used.
The `"hash-header"` and `"hash-property"` are mutually exclusive.
When a `"hash-property"` is specified, the chosen property **must be provided**.
If published messages do not contain the property, they will all get