I’m curious why the RabbitMQ streams feature flag is required to use delayed delivery. I’ve searched through the code, and the only use of streams I can find is the check to see if the feature flag is enabled. I can’t find any other usage of streams. I created a sample application that uses delayed delivery on a RabbitMQ broker that has the streams feature flag, and all of the delay level queues are quorum queues. It seems that no part of delayed delivery uses streams. I’m curious if I’ve missed something, or if streams are not actually required to use delayed delivery.
The stream_queue feature flag must be enabled because at-least-once dead lettering relies on some implementation details that come with that feature flag. There’s further documentation on the RabbitMQ website.
Ah, now I get it. Thanks so much! I’ll put together a pull request to simplify this check since the stream_queue feature flag is required for all 3.12+ versions. It’s redundant to create the stream to test the feature flag on those versions. Thanks for your help! Stand by for the PR.
Here’s a PR I created to skip creating the stream queue when using RabbitMQ version 3.12 or greater. The stream_queue feature flag is required to be enabled in those versions.
