131
edits
Army of Awesome/ElasticSearch Prototype: Difference between revisions
Army of Awesome/ElasticSearch Prototype (view source)
Revision as of 16:08, 10 November 2010
, 10 November 2010→Overview: D'oh! Wrong rest client project mentioned
DEinspanjer (talk | contribs) No edit summary |
DEinspanjer (talk | contribs) (→Overview: D'oh! Wrong rest client project mentioned) |
||
| Line 2: | Line 2: | ||
Metrics has created a five node [http://www.elasticsearch.com/ ElasticSearch] cluster on some test machines that is using the [http://www.elasticsearch.com/docs/elasticsearch/river/twitter/ Twitter River] functionality to automatically retrieve a filtered set of documents from Twitter's streaming API and index them. | Metrics has created a five node [http://www.elasticsearch.com/ ElasticSearch] cluster on some test machines that is using the [http://www.elasticsearch.com/docs/elasticsearch/river/twitter/ Twitter River] functionality to automatically retrieve a filtered set of documents from Twitter's streaming API and index them. | ||
A very useful tool I found for playing around with this is [http:// | A very useful tool I found for playing around with this is [http://code.google.com/p/rest-client/ RESTClient], a Java GUI that allows you to edit requests, view responses, and save both. | ||
=Sample 1= | =Sample 1= | ||