We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Currently it uses a direct Erlang client operation, which would fail if the queue in question is exclusive.
On the contrary, rabbitmqctl delete_queue can delete exclusive queues just fine because it does not use a client to do so.
rabbitmqctl delete_queue
There is no reason why the HTTP API should not use rabbit_amqqueue:delete/4 directly.
rabbit_amqqueue:delete/4
The text was updated successfully, but these errors were encountered:
This was reverted in #10185
Sorry, something went wrong.
michaelklishin
No branches or pull requests
Currently it uses a direct Erlang client operation, which would fail if the queue in question is exclusive.
On the contrary,
rabbitmqctl delete_queue
can delete exclusive queues just fine because it doesnot use a client to do so.
There is no reason why the HTTP API should not use
rabbit_amqqueue:delete/4
directly.The text was updated successfully, but these errors were encountered: