Namespaced consumer groups doesn't work with Bulk pubsub on RabbitMQ

[alicejgibbons]

Expected Behavior

Namespaced consumer groups should work as documented here: https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-namespace/#with-namespace-consumer-groups

Actual Behavior

When adding the namespace configuration to rabbitmq component this fails to add the correct namespaced consumer group to the broker but instead does not take the namespace into account on topic or consumer group creation.

  - name: consumerID
    value: "{namespace}"

This works on regular pubsub, eg namespace= default and topic=orders

On bulk pubsub, the publisher is just using orders topic.

This was also tested and works fine on Redis so I believe is just a bug on RabbitMQ.

Steps to Reproduce the Problem

Run the repro sample here: https://github.com/alicejgibbons/dapr-bulk-pubsub-rabbit

Release Note

RELEASE NOTE: FIX Bug in Dapr bulk pubsub with rabbitmq

[eliajbo]

Hello,

Here is how I could go around this issue temporarely when using the .NET SDK.

The issue is located at the use of daprClient.BulkPublishEventAsync specifically.
I could go around the problem by prefixing the topicName value with the required namespace and all the rest then works. Eg: namespaceTopic.

In Rmq management, you can see the exchange as namespaceTopic after the fix too instead of Topic.
In queues and streams section, you will see
namespace.pubsubname-subscribingAppId-namespaceTopic

So the fix is not needed for client.PublishEventAsync that already does this well.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[alicejgibbons]

note stale

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[alicejgibbons]

not stale

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[alicejgibbons]

not stale