# Percolator with rabbitmq river

**URL:** <https://discuss.elastic.co/t/percolator-with-rabbitmq-river/6380>\
**Category:** Elasticsearch\
**Created:** [January 14, 2012, 7:03am UTC](https://discuss.elastic.co/t/percolator-with-rabbitmq-river/6380 "2012-01-14T07:03:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Casey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_casey/32/3021_2.png) [@Steve\_Casey](https://discuss.elastic.co/u/Steve_Casey)\
**Post date:** [January 14, 2012, 7:03am UTC](https://discuss.elastic.co/t/percolator-with-rabbitmq-river/6380/1 "2012-01-14T07:03:52Z")

</div>

Hi, I'd like some advice/feedback on whether this scenario is something you  
could do with ES & some customization of the rabbitmq river...

Is it possible to get the rabbitmq river to send messages to a percolator?  
(i dont need the docs indexed)

Then when the percolator responds with a set of matching queries, I send  
the matching queries with the initial document onto another rabbitmq queue?  
(eg. if 1 doc matches 5 queries, then 5 msgs are pushed onto queue)

(let me know if an example is needed to better illustrate :))

Basically, using ES as a filtering engine for queue messages.

Is it a really bad idea? would it have severe limitations? (scale? too many  
moving parts?) why?

Or is it awesome and I should get the rabbitmq river code forked now!?! 🙂

Regards,  
Steve

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [January 14, 2012, 4:07pm UTC](https://discuss.elastic.co/t/percolator-with-rabbitmq-river/6380/2 "2012-01-14T16:07:55Z")

</div>

Its possible to do with rabbitmq, but it does not feel like a "river". Just  
write code that does it yourself in your own codebase, why introduce the  
complexity of a river? If you still want to do a "river", I would create a  
different type of river, not one that does both indexing and percolation.

On Sat, Jan 14, 2012 at 9:03 AM, Steve Casey [sa.casey@gmail.com](mailto:sa.casey@gmail.com) wrote:

> Hi, I'd like some advice/feedback on whether this scenario is something  
> you could do with ES & some customization of the rabbitmq river...
> 
> Is it possible to get the rabbitmq river to send messages to a percolator?  
> (i dont need the docs indexed)
> 
> Then when the percolator responds with a set of matching queries, I send  
> the matching queries with the initial document onto another rabbitmq queue?  
> (eg. if 1 doc matches 5 queries, then 5 msgs are pushed onto queue)
> 
> (let me know if an example is needed to better illustrate :))
> 
> Basically, using ES as a filtering engine for queue messages.
> 
> Is it a really bad idea? would it have severe limitations? (scale? too  
> many moving parts?) why?
> 
> Or is it awesome and I should get the rabbitmq river code forked now!?! 🙂
> 
> Regards,  
> Steve

---

<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:42am UTC](https://discuss.elastic.co/t/percolator-with-rabbitmq-river/6380/3 "2017-07-06T03:42:44Z")

</div>

Closed on July 6, 2017, 3:42am UTC