Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default queue type (DQT): fall back to node-wide default when virtual host has no metadata set #12109

Merged
merged 3 commits into from
Aug 24, 2024

Conversation

michaelklishin
Copy link
Member

@michaelklishin michaelklishin commented Aug 24, 2024

when virtual host does not have any metadata.

With this change, an x-queue-type header will be injected into optional queue arguments
and returned as part of definitions and the HTTP API in virtually all cases.

This also relaxes the assert_list/2 assertion a bit: it
no longer requires the size of an actually returned list element
to be exactly equal to the size of the expected one.

Sometimes it makes perfect sense to not assert on
every single key but only a subset, and with this
change, it now will be possible.

Individual tests may choose to assert on all
keys by listing them explicitly.

References #11541 #11457 #11528

when virtual host does not have any metadata.

References #11541 #11457 #11528
@michaelklishin michaelklishin changed the title DQT: fall back to node-wide default Default queue type (DQT): fall back to node-wide default when virtual host has no metadata set Aug 24, 2024
This relaxes assert_list/2 assertion to
not require the size of an actually returned list element
to be exactly equal to the size of the expected one.

Sometimes it makes perfect sense to not assert on
every single key but only a subset, and with this
change, it now will be possible.

Individual tests may choose to assert on all
keys by listing them explicitly.
@michaelklishin
Copy link
Member Author

I'm adding more redeclaration tests for classic queues just in case:

In particular, the behavior of redeclaration of a classic queue with x-queue-type and without any x-queue-type set does not change according to the above tests and my manual testing.

@michaelklishin michaelklishin merged commit f12919b into main Aug 24, 2024
199 checks passed
@michaelklishin michaelklishin deleted the mk-fix-node-wide-dqt branch August 24, 2024 21:15
michaelklishin added a commit that referenced this pull request Aug 24, 2024
Default queue type (DQT): fall back to node-wide default when virtual host has no metadata set (backport #12109)
@michaelklishin michaelklishin added this to the 4.0.0 milestone Aug 24, 2024
michaelklishin added a commit that referenced this pull request Aug 24, 2024
SimonUnge added a commit to SimonUnge/rabbitmq-server that referenced this pull request Aug 30, 2024
SimonUnge added a commit to SimonUnge/rabbitmq-server that referenced this pull request Sep 5, 2024
@SimonUnge SimonUnge mentioned this pull request Sep 5, 2024
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant