# Just Pushed: Percolator

**URL:** <https://discuss.elastic.co/t/just-pushed-percolator/3771>\
**Category:** Elasticsearch\
**Created:** [January 13, 2011, 2:23pm UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771 "2011-01-13T14:23:32Z")\
**Posts on this page:** 8\
**Page:** 1

<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 13, 2011, 2:23pm UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/1 "2011-01-13T14:23:32Z")

</div>

Hi,

Just pushed a big feature to ES called Percolator. Percolator does the "reverse" of what ES does today. Instead of indexing docs and then running searches against them, one registers queries and percolates a doc among them, getting back which queries matched that doc.

Tons of more features can be built on top of this core feature, would love to hear some feedback.

Note, this feature is still experimental.

Issue: [https://github.com/elasticsearch/elasticsearch/issues/issue/624](https://github.com/elasticsearch/elasticsearch/issues/issue/624)

cheers,  
-shay.banon

---

<div class="post-metadata">

**Author:** ![dbenson](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@dbenson](https://discuss.elastic.co/u/dbenson)\
**Post date:** [January 13, 2011, 4:00pm UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/2 "2011-01-13T16:00:26Z")

</div>

Shay,

Loving the pace of innovation! This looks really cool, exactly the  
type of idea Paul and I were thinking about when we asked about email  
alerts.

Would this work for a query which spans multiple indexes?

We're set to upgrade our production instances next week from 0.13 to  
0.14.2 to take advantage of the substantial reduction in disk space  
needed for full text queries w/ highlighting.

Thanks,

David

---

<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 13, 2011, 4:12pm UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/3 "2011-01-13T16:12:13Z")

</div>

> Would this work for a query which spans multiple indexes?

It works a bit differently then the idea of searching across indices. You register a query under an index, and then you can percolate a doc against those queries.

If you have several indices, you will need to register queries on each one.  
On Thursday, January 13, 2011 at 6:00 PM, dbenson wrote:

> Shay,
> 
> Loving the pace of innovation! This looks really cool, exactly the  
> type of idea Paul and I were thinking about when we asked about email  
> alerts.
> 
> Would this work for a query which spans multiple indexes?
> 
> We're set to upgrade our production instances next week from 0.13 to  
> 0.14.2 to take advantage of the substantial reduction in disk space  
> needed for full text queries w/ highlighting.
> 
> Thanks,
> 
> David

---

<div class="post-metadata">

**Author:** ![dbenson](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@dbenson](https://discuss.elastic.co/u/dbenson)\
**Post date:** [January 13, 2011, 5:22pm UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/4 "2011-01-13T17:22:53Z")

</div>

Thanks. After thinking about it for a bit, I came to the same  
conclusion.

David

---

<div class="post-metadata">

**Author:** ![Berkay\_Mollamustafao](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Berkay\_Mollamustafao](https://discuss.elastic.co/u/Berkay_Mollamustafao)\
**Post date:** [January 14, 2011, 1:23am UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/5 "2011-01-14T01:23:15Z")

</div>

Great!

I can't agree more that this feature opens up a whole new world!

Regards,  
Berkay Mollamustafaoglu  
mberkay on yahoo, google and skype

On Thu, Jan 13, 2011 at 9:23 AM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote:

> Hi,
> 
> Just pushed a big feature to ES called Percolator. Percolator does the  
> "reverse" of what ES does today. Instead of indexing docs and then running  
> searches against them, one registers queries and percolates a doc among  
> them, getting back which queries matched that doc.
> 
> Tons of more features can be built on top of this core feature, would  
> love to hear some feedback.
> 
> ```
> Note, this feature is still experimental.
> 
> Issue: https://github.com/elasticsearch/elasticsearch/issues/issue/624
> 
> ```
> 
> cheers,  
> -shay.banon

---

<div class="post-metadata">

**Author:** ![harryf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harryf/32/3281_2.png) [@harryf](https://discuss.elastic.co/u/harryf)\
**Post date:** [January 14, 2011, 11:29am UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/6 "2011-01-14T11:29:18Z")

</div>

How would perculator play together with something like the twitter  
river? Thinking to make this really useful you'd want some kind of  
callback / webhook - [http://wiki.webhooks.org/](http://wiki.webhooks.org/) - to be fired when  
registered queries match. Or am I missing something?

On Jan 13, 3:23 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:

> Hi,
> 
> Just pushed a big feature to ES called Percolator. Percolator does the "reverse" of what ES does today. Instead of indexing docs and then running searches against them, one registers queries and percolates a doc among them, getting back which queries matched that doc.
> 
> Tons of more features can be built on top of this core feature, would love to hear some feedback.
> 
> Note, this feature is still experimental.
> 
> Issue:[Percolator · Issue #624 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/issue/624)
> 
> cheers,  
> -shay.banon

---

<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, 2011, 1:26pm UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/7 "2011-01-14T13:26:31Z")

</div>

This feature is the core feature to get things going. Doing things like getting matched queries when indexing docs, and possibly publishing them is going to be built on top of it.  
On Friday, January 14, 2011 at 1:29 PM, harryf wrote:

> How would perculator play together with something like the twitter  
> river? Thinking to make this really useful you'd want some kind of  
> callback / webhook - [http://wiki.webhooks.org/](http://wiki.webhooks.org/) - to be fired when  
> registered queries match. Or am I missing something?
> 
> On Jan 13, 3:23 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:
> 
> > Hi,
> > 
> > Just pushed a big feature to ES called Percolator. Percolator does the "reverse" of what ES does today. Instead of indexing docs and then running searches against them, one registers queries and percolates a doc among them, getting back which queries matched that doc.
> > 
> > Tons of more features can be built on top of this core feature, would love to hear some feedback.
> > 
> > Note, this feature is still experimental.
> > 
> > Issue:[Percolator · Issue #624 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/issue/624)
> > 
> > cheers,  
> > -shay.banon

---

<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, 4:13am UTC](https://discuss.elastic.co/t/just-pushed-percolator/3771/8 "2017-07-06T04:13:54Z")

</div>


