# \[ANN\] Elasticsearch Twitter River plugin 2.2.0 released **URL:** \ **Category:** Elasticsearch\ **Created:** [July 23, 2014, 12:00pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819 "2014-07-23T12:00:47Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [July 23, 2014, 12:00pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819/1 "2014-07-23T12:00:47Z")
Heya, We are pleased to announce the release of the Elasticsearch Twitter River plugin, version 2.2.0. The Twitter River plugin allows index twitter stream using elasticsearch rivers feature. > **[elastic/elasticsearch-river-twitter](https://github.com/elastic/elasticsearch-river-twitter)** > > elasticsearch-river-twitter - Twitter River Plugin for elasticsearch (STOPPED) Release Notes - elasticsearch-river-twitter - Version 2.2.0 Fix: - [62] - Generate default mapping even if index already exists ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/62](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/62)) - [60] - ignore\_retweets does not ignore RT ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/60](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/60)) Update: - [61] - Update to Twitter4J 4.0.2 ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/61](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/61)) - [58] - Remove old deprecated user and password properties ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/58](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/58)) - [57] - Deprecate usage of camelCase settings ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/57](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/57)) - [54] - Added not\_analyzed to retweet user\_screen\_name ([https://github.com/elasticsearch/elasticsearch-river-twitter/pull/54](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/54)) - [52] - Update to elasticsearch 1.2.0 ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/52](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/52)) New: - [56] - Add oauth credentials in `elasticsearch.yml` file ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/56](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/56)) - [51] - Support geo location array format ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/51](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/51)) - [50] - Add user stream support ([https://github.com/elasticsearch/elasticsearch-river-twitter/pull/50](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/50)) - [37] - Move tests to elasticsearch test framework ([https://github.com/elasticsearch/elasticsearch-river-twitter/issues/37](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/37)) Doc: - [49] - [DOC] Link to rivers documentation is incorrect ([https://github.com/elasticsearch/elasticsearch-river-twitter/pull/49](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/49)) Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-river-twitter project repository: [https://github.com/elasticsearch/elasticsearch-river-twitter/](https://github.com/elasticsearch/elasticsearch-river-twitter/) For questions or comments around this plugin, feel free to use elasticsearch mailing list: [https://groups.google.com/forum/#!forum/elasticsearch](https://groups.google.com/forum/#!forum/elasticsearch) Enjoy, -The Elasticsearch team -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jmkgreen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmkgreen/32/471_2.png) [@jmkgreen](https://discuss.elastic.co/u/jmkgreen)\ **Post date:** [July 23, 2014, 12:08pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819/2 "2014-07-23T12:08:43Z")
I was told a week or two ago on IRC that rivers were deprecated in favour of external data sources like Logstash. Is this not correct? On 23 July 2014 13:00, Elasticsearch Team [david@pilato.fr](mailto:david@pilato.fr) wrote: > Heya, > > We are pleased to announce the release of the _Elasticsearch Twitter > River plugin_, _version 2.2.0_ > > The Twitter River plugin allows index twitter stream using elasticsearch > rivers feature. > > Release Notes - Version 2.2.0 Fix > > - [62 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/62](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/62)] > - Generate default mapping even if index already exists > - [60 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/60](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/60)] > - ignore\_retweets does not ignore RT > > Update > > - [61 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/61](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/61)] > - Update to Twitter4J 4.0.2 > - [58 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/58](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/58)] > - Remove old deprecated user and password properties > - [57 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/57](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/57)] > - Deprecate usage of camelCase settings > - [54 > [https://github.com/elasticsearch/elasticsearch-river-twitter/pull/54](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/54)] > - Added not\_analyzed to retweet user\_screen\_name > - [52 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/52](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/52)] > - Update to elasticsearch 1.2.0 > > New > > - [56 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/56](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/56)] > - Add oauth credentials in `elasticsearch.yml` file > - [51 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/51](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/51)] > - Support geo location array format > - [50 > [https://github.com/elasticsearch/elasticsearch-river-twitter/pull/50](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/50)] > - Add user stream support > - [37 > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/37](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/37)] > - Move tests to elasticsearch test framework > > Doc > > - [49 > [https://github.com/elasticsearch/elasticsearch-river-twitter/pull/49](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/49)] > - [DOC] Link to rivers documentation is incorrect > > Issues, Pull requests, Feature requests are warmly welcome on > elasticsearch-river-twitter > [https://github.com/elasticsearch/elasticsearch-river-twitter/](https://github.com/elasticsearch/elasticsearch-river-twitter/) project > repository! > > For questions or comments around this plugin, feel free to use > elasticsearch mailing list > [https://groups.google.com/forum/#!forum/elasticsearch](https://groups.google.com/forum/#!forum/elasticsearch)! > > Enjoy, > > - The Elasticsearch team [http://www.elasticsearch.com/](http://www.elasticsearch.com/) > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com) > [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm\_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [July 23, 2014, 12:13pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819/3 "2014-07-23T12:13:34Z")
Rivers will be deprecated in favor of logstash inputs. Deprecated does not mean removed yet. So in the meantime we still try to keep up to date official plugins. But yes, you should prefer using if possible logstash twitter input ([http://logstash.net/docs/1.4.2/inputs/twitter](http://logstash.net/docs/1.4.2/inputs/twitter)) -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 23 juillet 2014 à 14:08:49, James Green ([james.mk.green@gmail.com](mailto:james.mk.green@gmail.com)) a écrit: I was told a week or two ago on IRC that rivers were deprecated in favour of external data sources like Logstash. Is this not correct? On 23 July 2014 13:00, Elasticsearch Team [david@pilato.fr](mailto:david@pilato.fr) wrote: Heya, We are pleased to announce the release of the Elasticsearch Twitter River plugin, version 2.2.0 The Twitter River plugin allows index twitter stream using elasticsearch rivers feature. Release Notes - Version 2.2.0 Fix [62] - Generate default mapping even if index already exists [60] - ignore\_retweets does not ignore RT Update [61] - Update to Twitter4J 4.0.2 [58] - Remove old deprecated user and password properties [57] - Deprecate usage of camelCase settings [54] - Added not\_analyzed to retweet user\_screen\_name [52] - Update to elasticsearch 1.2.0 New [56] - Add oauth credentials in `elasticsearch.yml` file [51] - Support geo location array format [50] - Add user stream support [37] - Move tests to elasticsearch test framework Doc [49] - [DOC] Link to rivers documentation is incorrect Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-river-twitter project repository! For questions or comments around this plugin, feel free to use elasticsearch mailing list! Enjoy, - The Elasticsearch team -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm\_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.53cfa6ef.507ed7ab.13e40%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.53cfa6ef.507ed7ab.13e40%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Andrej](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@Andrej](https://discuss.elastic.co/u/Andrej)\ **Post date:** [July 24, 2014, 11:42am UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819/4 "2014-07-24T11:42:21Z")
Hi David, does that mean in conclusion that there will be a rss input for logstash soon as replacement of the river? Same goes for wikipedia? Greets, Andrej Am Mittwoch, 23. Juli 2014 14:13:51 UTC+2 schrieb David Pilato: > Rivers will be deprecated in favor of logstash inputs. > Deprecated does not mean removed yet. > So in the meantime we still try to keep up to date official plugins. > > But yes, you should prefer using if possible logstash twitter input ( > [Twitter input plugin | Logstash Reference [8.11] | Elastic](http://logstash.net/docs/1.4.2/inputs/twitter)) > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) > > Le 23 juillet 2014 à 14:08:49, James Green ([james.m...@gmail.com](mailto:james.m...@gmail.com) > \) a écrit: > > I was told a week or two ago on IRC that rivers were deprecated in favour > of external data sources like Logstash. > > Is this not correct? > > On 23 July 2014 13:00, Elasticsearch Team \<[da...@pilato.fr](mailto:da...@pilato.fr) \\> > wrote: > > > Heya, > > > > We are pleased to announce the release of the _Elasticsearch Twitter > > River plugin_, _version 2.2.0_ > > > > The Twitter River plugin allows index twitter stream using elasticsearch > > rivers feature. > > > > Release Notes - Version 2.2.0 Fix > > > > - [62 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/62](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/62)] > > - Generate default mapping even if index already exists > > - [60 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/60](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/60)] > > - ignore\_retweets does not ignore RT > > > > Update > > > > - [61 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/61](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/61)] > > - Update to Twitter4J 4.0.2 > > - [58 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/58](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/58)] > > - Remove old deprecated user and password properties > > - [57 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/57](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/57)] > > - Deprecate usage of camelCase settings > > - [54 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/pull/54](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/54)] > > - Added not\_analyzed to retweet user\_screen\_name > > - [52 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/52](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/52)] > > - Update to elasticsearch 1.2.0 > > > > New > > > > - [56 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/56](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/56)] > > - Add oauth credentials in `elasticsearch.yml` file > > - [51 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/51](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/51)] > > - Support geo location array format > > - [50 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/pull/50](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/50)] > > - Add user stream support > > - [37 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/issues/37](https://github.com/elasticsearch/elasticsearch-river-twitter/issues/37)] > > - Move tests to elasticsearch test framework > > > > Doc > > > > - [49 > > [https://github.com/elasticsearch/elasticsearch-river-twitter/pull/49](https://github.com/elasticsearch/elasticsearch-river-twitter/pull/49)] > > - [DOC] Link to rivers documentation is incorrect > > > > Issues, Pull requests, Feature requests are warmly welcome on > > elasticsearch-river-twitter > > [https://github.com/elasticsearch/elasticsearch-river-twitter/](https://github.com/elasticsearch/elasticsearch-river-twitter/) project > > repository! > > > > For questions or comments around this plugin, feel free to use > > elasticsearch mailing list > > [https://groups.google.com/forum/#!forum/elasticsearch](https://groups.google.com/forum/#!forum/elasticsearch)! > > > > Enjoy, > > > > - The Elasticsearch team [http://www.elasticsearch.com/](http://www.elasticsearch.com/) > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com) > > [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm\_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm\_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c521027a-16e1-4b3b-85bc-14c370323de7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c521027a-16e1-4b3b-85bc-14c370323de7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [July 24, 2014, 11:46am UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819/5 "2014-07-24T11:46:25Z")
Hi Andrej That's the plan indeed. About "soon", I don't know 🙂 -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 24 juillet 2014 à 13:42:25, Andrej Rosenheinrich (andrej.rosenheinrich@unister.de) a écrit: Hi David, does that mean in conclusion that there will be a rss input for logstash soon as replacement of the river? Same goes for wikipedia? Greets, Andrej Am Mittwoch, 23. Juli 2014 14:13:51 UTC+2 schrieb David Pilato: Rivers will be deprecated in favor of logstash inputs. Deprecated does not mean removed yet. So in the meantime we still try to keep up to date official plugins. But yes, you should prefer using if possible logstash twitter input ([http://logstash.net/docs/1.4.2/inputs/twitter](http://logstash.net/docs/1.4.2/inputs/twitter)) -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr Le 23 juillet 2014 à 14:08:49, James Green ([james.m...@gmail.com](mailto:james.m...@gmail.com)) a écrit: I was told a week or two ago on IRC that rivers were deprecated in favour of external data sources like Logstash. Is this not correct? On 23 July 2014 13:00, Elasticsearch Team [da...@pilato.fr](mailto:da...@pilato.fr) wrote: Heya, We are pleased to announce the release of the Elasticsearch Twitter River plugin, version 2.2.0 The Twitter River plugin allows index twitter stream using elasticsearch rivers feature. Release Notes - Version 2.2.0 Fix [62] - Generate default mapping even if index already exists [60] - ignore\_retweets does not ignore RT Update [61] - Update to Twitter4J 4.0.2 [58] - Remove old deprecated user and password properties [57] - Deprecate usage of camelCase settings [54] - Added not\_analyzed to retweet user\_screen\_name [52] - Update to elasticsearch 1.2.0 New [56] - Add oauth credentials in `elasticsearch.yml` file [51] - Support geo location array format [50] - Add user stream support [37] - Move tests to elasticsearch test framework Doc [49] - [DOC] Link to rivers documentation is incorrect Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-river-twitter project repository! For questions or comments around this plugin, feel free to use elasticsearch mailing list! Enjoy, - The Elasticsearch team -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com](https://groups.google.com/d/msgid/elasticsearch/53cfa3ef.8124b40a.2b81.3571SMTPIN_ADDED_MISSING%40gmr-mx.google.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ## -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm\_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bawb9LYHPnm_5yxVJBr6c6xNkuz200mjES52uyCOPTfK%3Dg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c521027a-16e1-4b3b-85bc-14c370323de7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c521027a-16e1-4b3b-85bc-14c370323de7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.53d0f211.737b8ddc.13e40%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.53d0f211.737b8ddc.13e40%40MacBook-Air-de-David.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:13am UTC](https://discuss.elastic.co/t/ann-elasticsearch-twitter-river-plugin-2-2-0-released/18819/6 "2017-07-06T01:13:31Z")