The twitter streaming API allows you to filter, and you apparently get up
to 1% of the stream total, with our search queries. So, if I were filtering
for "coffee", I'd get "coffee" tweets that I wouldn't get if I was just
capturing the 1% stream passively.
Does the Twitter river use this filter functionality, or does it do its
filtering on the ingestion side, ingesting the normal 1% stream and
discarding anything that doesn't match
Le 7 juillet 2014 à 21:54:02, Josh Harrison (hijakk@gmail.com) a écrit:
Quick question about the ES twitter river at https://github.com/elasticsearch/elasticsearch-river-twitter
The twitter streaming API allows you to filter, and you apparently get up to 1% of the stream total, with our search queries. So, if I were filtering for "coffee", I'd get "coffee" tweets that I wouldn't get if I was just capturing the 1% stream passively.
Does the Twitter river use this filter functionality, or does it do its filtering on the ingestion side, ingesting the normal 1% stream and discarding anything that doesn't match
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.