# Prototype use of ElasticSearch Twitter River

**URL:** <https://discuss.elastic.co/t/prototype-use-of-elasticsearch-twitter-river/3546>\
**Category:** Elasticsearch\
**Created:** [November 10, 2010, 2:56pm UTC](https://discuss.elastic.co/t/prototype-use-of-elasticsearch-twitter-river/3546 "2010-11-10T14:56:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![deinspanjer](https://avatars.discourse-cdn.com/v4/letter/d/cab0a1/32.png) [@deinspanjer](https://discuss.elastic.co/u/deinspanjer)\
**Post date:** [November 10, 2010, 2:56pm UTC](https://discuss.elastic.co/t/prototype-use-of-elasticsearch-twitter-river/3546/1 "2010-11-10T14:56:14Z")

</div>

Mozilla Metrics has created a five node ElasticSearch cluster on some test machines that is using the Twitter River functionality to automatically retrieve a filtered set of documents from Twitter's streaming API and index them.

I've just created this page to document the first sample query:  
[https://wiki.mozilla.org/Army\_of\_Awesome/ElasticSearch\_Prototype](https://wiki.mozilla.org/Army_of_Awesome/ElasticSearch_Prototype)

I would love to get some feedback from the ES community on points/questions made on that page and improvements / ideas for the query.

---

<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:16am UTC](https://discuss.elastic.co/t/prototype-use-of-elasticsearch-twitter-river/3546/2 "2017-07-06T04:16:48Z")

</div>