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
I want to be able to subscribe to a topic twice with different routes and routing keys.
the exchange 'topica' should show 2 queues with different names and different routing keys and point to different routes
test-api-event-user-receiver
test-api-data-user-receiver
suggestion: the subscription metadata.name value should be used for the subscription/queue name to avoid naming conflicts on the queues.
Actual Behavior
Only one queue is getting created in the Rabbit-MQ exchange. The second one is missing.
I guess the issue is how subscriptions (= rabbit MQ queue attached to the exchange) get setup by dapr. The first subscription creates a queue with the name 'test-api-topica' (='{consumerID}-{exchangeName}') and the second one would try to setup a queue with the same name '{consumerID}-{exchangeName}' again.
In what area(s)?
What version of Dapr?
Expected Behavior
I want to be able to subscribe to a topic twice with different routes and routing keys.
the exchange 'topica' should show 2 queues with different names and different routing keys and point to different routes
suggestion: the subscription metadata.name value should be used for the subscription/queue name to avoid naming conflicts on the queues.
Actual Behavior
Only one queue is getting created in the Rabbit-MQ exchange. The second one is missing.
I guess the issue is how subscriptions (= rabbit MQ queue attached to the exchange) get setup by dapr. The first subscription creates a queue with the name 'test-api-topica' (='{consumerID}-{exchangeName}') and the second one would try to setup a queue with the same name '{consumerID}-{exchangeName}' again.
Steps to Reproduce the Problem
Release Note
RELEASE NOTE: FIX Multiple subscriptions on one topic with different routes and routingKeys
The text was updated successfully, but these errors were encountered: