Summary:
Add a new hash-property argument setting that allows for message hasing based upon the correlation_id or message_id.
Changes:
- Validate the exchange upon creation to ensure that hash-header and hash-property are not both set at the same time. Additionally validate the value of hash-property when set is one of correlation_id or message_id
- Change the signature of hash/2 for header to match on {header, Header} instead of {longstr, Header}
- Add a new hash/2 implementation that matches on {property, Value} for returning the hashable string from the message properties
- Implement a new hash_on/1 method for selecting the data the message will be routed on
- Implement a new hash_args/1 method for returning the configuration for both hash-header and hash-property
- Add test coverage for message property based routing
This addresses the proposal I outlined in #7
Alvaro Videla
Gavin M. Roy
Michael Klishin
Simon MacMullen
Emile Joubert
Matthew Sackman