# \[ANN\] Deprecating Rivers **URL:** \ **Category:** Elasticsearch\ **Created:** [April 1, 2015, 10:30pm UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050 "2015-04-01T22:30:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 1, 2015, 10:30pm UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050/1 "2015-04-01T22:30:20Z")
Hi All, We've recently announced that Rivers in Elasticsearch are actively deprecated as of the 1.5 release, the 2.0 release will still maintain that functionality to ease migration, but we recommend you start to leverage the official clients to replace any Rivers you may have in use. If you have feedback around this process then feel free to add a comment to this Github issue - [https://github.com/elastic/elasticsearch/issues/10345](https://github.com/elastic/elasticsearch/issues/10345) And for more information please see this blog post on our site - > **[Deprecating Rivers | Elastic](https://www.elastic.co/blog/deprecating-rivers)** > > When I added rivers way back in time in the early days of Elasticsearch, the idea was somewhat novel. One of the first tasks that users do when using Elasticsearch is to get data into Elasticsearch to... -- 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/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.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:** [April 2, 2015, 8:00am UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050/2 "2015-04-02T08:00:45Z")
Good luck with this when "Elasticsearch Team" is continuing to email the list with river plugin updates and asking for feature requests to their github projects. On 1 April 2015 at 23:30, Mark Walkom [mark@walkom.id.au](mailto:mark@walkom.id.au) wrote: > Hi All, > We've recently announced that Rivers in Elasticsearch are actively > deprecated as of the 1.5 release, the 2.0 release will still maintain that > functionality to ease migration, but we recommend you start to leverage the > official clients to replace any Rivers you may have in use. > > If you have feedback around this process then feel free to add a comment > to this Github issue - > [Deprecating Rivers · Issue #10345 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/10345) > > And for more information please see this blog post on our site - > [Deprecating Rivers | Elastic Blog](https://www.elastic.co/blog/deprecating_rivers) > > -- > 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/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%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/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh\_GcEfA-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh_GcEfA-Q%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:** [April 2, 2015, 8:13am UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050/3 "2015-04-02T08:13:03Z")
Fair enough. I will remove this part of the « signature » in next emails. -- David Pilato - Developer | Evangelist > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co/)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > Le 2 avr. 2015 à 10:00, James Green [james.mk.green@gmail.com](mailto:james.mk.green@gmail.com) a écrit : > > Good luck with this when "Elasticsearch Team" is continuing to email the list with river plugin updates and asking for feature requests to their github projects. > > On 1 April 2015 at 23:30, Mark Walkom \ wrote: > Hi All, > We've recently announced that Rivers in Elasticsearch are actively deprecated as of the 1.5 release, the 2.0 release will still maintain that functionality to ease migration, but we recommend you start to leverage the official clients to replace any Rivers you may have in use. > > If you have feedback around this process then feel free to add a comment to this Github issue - [Deprecating Rivers · Issue #10345 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/10345) [https://github.com/elastic/elasticsearch/issues/10345](https://github.com/elastic/elasticsearch/issues/10345) > > And for more information please see this blog post on our site - [Deprecating Rivers | Elastic Blog](https://www.elastic.co/blog/deprecating_rivers) [https://www.elastic.co/blog/deprecating\_rivers](https://www.elastic.co/blog/deprecating_rivers) > > -- > 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) [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com) [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%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) [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) [mailto: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%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh\_GcEfA-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh_GcEfA-Q%40mail.gmail.com) [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh\_GcEfA-Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2BaxMe0yPQyRCWB0e8RytsvPt67OFxoH71RBE%3Dh_GcEfA-Q%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) [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/782C3D2A-727C-4B2C-BB3B-78352548CCCD%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/782C3D2A-727C-4B2C-BB3B-78352548CCCD%40pilato.fr). 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:** [April 8, 2015, 8:01am UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050/4 "2015-04-08T08:01:03Z")
Also note that the current documentation lists a load of river plugins without stating that they are officially deprecated as an idea: > **[Plugins | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-plugins.html)** Rather concerned that people are still adopting rivers due to the apparent continued promotion of them. If you have not already, I suggest each time a node fires up and detects a river plugin it issues at least a warning in a log to remove it in favour of alternatives such as logstash. At least the official rivers are marked deprecated in their readme but not everyone will spot this. On 1 April 2015 at 23:30, Mark Walkom [mark@walkom.id.au](mailto:mark@walkom.id.au) wrote: > Hi All, > We've recently announced that Rivers in Elasticsearch are actively > deprecated as of the 1.5 release, the 2.0 release will still maintain that > functionality to ease migration, but we recommend you start to leverage the > official clients to replace any Rivers you may have in use. > > If you have feedback around this process then feel free to add a comment > to this Github issue - > [Deprecating Rivers · Issue #10345 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/10345) > > And for more information please see this blog post on our site - > [Deprecating Rivers | Elastic Blog](https://www.elastic.co/blog/deprecating_rivers) > > -- > 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/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%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/CAMH6%2Bazr1yamseHfSD9HriTqyos6uLJ7zX3qa%2B7oqom24qCeCA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bazr1yamseHfSD9HriTqyos6uLJ7zX3qa%2B7oqom24qCeCA%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:** [April 8, 2015, 8:11am UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050/5 "2015-04-08T08:11:29Z")
I agree James. That's a nice suggestion (warn when running deprecated code). BTW we have a lot of work in the code such as mark some Java classes as deprecated, modify docs... Things will come. IMO it's better to announce the deprecation sooner than later. That's the purpose of this blog post. So community can react as you just did or anticipate on their architecture design decisions. My cents on it. David > Le 8 avr. 2015 à 10:01, James Green [james.mk.green@gmail.com](mailto:james.mk.green@gmail.com) a écrit : > > Also note that the current documentation lists a load of river plugins without stating that they are officially deprecated as an idea: > > [Plugins | Elasticsearch Guide [8.11] | Elastic](http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-plugins.html) > > Rather concerned that people are still adopting rivers due to the apparent continued promotion of them. If you have not already, I suggest each time a node fires up and detects a river plugin it issues at least a warning in a log to remove it in favour of alternatives such as logstash. At least the official rivers are marked deprecated in their readme but not everyone will spot this. > > > On 1 April 2015 at 23:30, Mark Walkom [mark@walkom.id.au](mailto:mark@walkom.id.au) wrote: > > Hi All, > > We've recently announced that Rivers in Elasticsearch are actively deprecated as of the 1.5 release, the 2.0 release will still maintain that functionality to ease migration, but we recommend you start to leverage the official clients to replace any Rivers you may have in use. > > > > If you have feedback around this process then feel free to add a comment to this Github issue - [Deprecating Rivers · Issue #10345 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/10345) > > > > ## And for more information please see this blog post on our site - [Deprecating Rivers | Elastic Blog](https://www.elastic.co/blog/deprecating_rivers) > > > > 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/CAEYi1X90gyaxCnV9ygkdEAJirv\_4p8F3E\_1J9jQU\_axn9MBCGw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X90gyaxCnV9ygkdEAJirv_4p8F3E_1J9jQU_axn9MBCGw%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/CAMH6%2Bazr1yamseHfSD9HriTqyos6uLJ7zX3qa%2B7oqom24qCeCA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Bazr1yamseHfSD9HriTqyos6uLJ7zX3qa%2B7oqom24qCeCA%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/C0038380-367E-457F-B207-775E48E1F0A5%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/C0038380-367E-457F-B207-775E48E1F0A5%40pilato.fr). 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, 12:20am UTC](https://discuss.elastic.co/t/ann-deprecating-rivers/23050/6 "2017-07-06T00:20:56Z")