You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both queues will be bound to the direct exchange without routing key. This could lead to issues and even undesirable outcomes when pipelines process different kinds of messages.
I think amqp queue name should be used as a routing key by default.
This way, both pipelines will correctly process their corresponding queues.
Version
2.10.4
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
No duplicates 🥲.
What happened?
If one specifies a pipeline config like this:
Both queues will be bound to the
direct
exchange without routing key. This could lead to issues and even undesirable outcomes when pipelines process different kinds of messages.I think amqp queue name should be used as a routing key by default.
This way, both pipelines will correctly process their corresponding queues.
Version
2.10.4
Relevant log output
No response
The text was updated successfully, but these errors were encountered: