# Elastic Search River and Rabbit MQ integration

**URL:** <https://discuss.elastic.co/t/elastic-search-river-and-rabbit-mq-integration/7860>\
**Category:** Elasticsearch\
**Created:** [May 25, 2012, 10:04am UTC](https://discuss.elastic.co/t/elastic-search-river-and-rabbit-mq-integration/7860 "2012-05-25T10:04:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Prab](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@Prab](https://discuss.elastic.co/u/Prab)\
**Post date:** [May 25, 2012, 10:04am UTC](https://discuss.elastic.co/t/elastic-search-river-and-rabbit-mq-integration/7860/1 "2012-05-25T10:04:16Z")

</div>

Hello,

We are investigating to integrate Rabbit MQ with River.

Our requirement is to index the data which is being pushed to the Rabbit  
MQ. River can be configured to listen for topic/routing key.

I had seen some post that use bulk API/manual indexing instead of river. is  
there any disadvantage using River?

I will be keep posting questions...it's just a kick start!

Thanks  
Prab

---

<div class="post-metadata">

**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, 3:27am UTC](https://discuss.elastic.co/t/elastic-search-river-and-rabbit-mq-integration/7860/2 "2017-07-06T03:27:08Z")

</div>