# Improvements in rabbitmq-river-plugin **URL:** \ **Category:** Elasticsearch\ **Created:** [June 3, 2013, 8:31pm UTC](https://discuss.elastic.co/t/improvements-in-rabbitmq-river-plugin/12243 "2013-06-03T20:31:06Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Nicolas\_Blanc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_blanc/32/2030_2.png) [@Nicolas\_Blanc](https://discuss.elastic.co/u/Nicolas_Blanc)\ **Post date:** [June 3, 2013, 8:31pm UTC](https://discuss.elastic.co/t/improvements-in-rabbitmq-river-plugin/12243/1 "2013-06-03T20:31:06Z")
Hi all, We had this afternoon a bug with the rabbitmq river on ES. Our admin team want to be the only interface to create exchange/queue/binding. So we have a user which has only the right to publish messages, or consume it. But on the rabbitmq-river, some part did an exchange creation, or a queue creation or queue binding. A patch remove the need to create some parts of the process, but not all parts! So my fellow colleague odolbeau made a patch to the plugin, and made the PR to the repository. Every thing is here : > Hope this can help someone with the same user right problem! -- Nicolas Blanc. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:33am UTC](https://discuss.elastic.co/t/improvements-in-rabbitmq-river-plugin/12243/2 "2017-07-06T02:33:14Z")
Closed on July 6, 2017, 2:33am UTC