Skip to content

Support custom routing keys per message #51

@creyke

Description

@creyke

Please can you make it possible to define the routing key per-message. This is a common requirement of RabbitMQ message producers where specific properties of the message are used to determine how the key can be filtered.

A proposal could be to change the generic argument of RabbitMQAsyncCollector from byte[] to a RabbitMQMessage which exposes both a byte[] Body property, and a string RoutingKey.

If the latter is left null, then the routing key would be defaulted to the QueueName when added to the batch, else the message specific routing key would be used.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions