# Are rivers still being deprecated? **URL:** \ **Category:** Elasticsearch\ **Created:** [November 7, 2014, 2:16am UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623 "2014-11-07T02:16:47Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Alexandre\_Rafalovitc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexandre_rafalovitc/32/1124_2.png) [@Alexandre\_Rafalovitc](https://discuss.elastic.co/u/Alexandre_Rafalovitc)\ **Post date:** [November 7, 2014, 2:16am UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/1 "2014-11-07T02:16:47Z")
ElasticSearch 1.4 is out and I can't see any mentions that Rivers are deprecated. Has that (informal) decision been reversed? Or was the timeline further out? What's the currently recommended approach? Regards, Alex. -- 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/CAEFAe-FJqdk6yzV8i9E4DFrveDhabNDrk5wLeETYrJf1mB2L4g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEFAe-FJqdk6yzV8i9E4DFrveDhabNDrk5wLeETYrJf1mB2L4g%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [November 16, 2014, 8:24pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/2 "2014-11-16T20:24:41Z")
We've seen issues with Rivers in the past and no longer use them in our engagements. ## Otis Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) On Thursday, November 6, 2014 9:17:36 PM UTC-5, Alexandre Rafalovitch wrote: > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > deprecated. > > Has that (informal) decision been reversed? Or was the timeline > further out? What's the currently recommended approach? > > Regards, > Alex. -- 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/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jurgen\_Wagner\_DVT](https://avatars.discourse-cdn.com/v4/letter/j/e0b2c6/32.png) [@Jurgen\_Wagner\_DVT](https://discuss.elastic.co/u/Jurgen_Wagner_DVT)\ **Post date:** [November 16, 2014, 9:14pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/3 "2014-11-16T21:14:32Z")
Hello, we generally don't use rivers as it does not seem to be a good idea to put too much of connector functionality into a search nodes themselves. The scaling of connectors and feeding is entirely different from that of processing and indexing or querying. That's why it is in my opinion clearly advisable to keep such components in an architecture separate and not to interweave them more than necessary. The notorious data import handlers of SolrCloud demonstrate where this leads to. I don't know what stance the Elasticsearch folks take towards rivers, but from an architectural point of view, the clear separation from Elasticsearch seems like a good mid- to long-term goal to go for. My 5 EUR-cents worth of feedback... --Jürgen On 16.11.2014 21:24, Otis Gospodnetic wrote: > We've seen issues with Rivers in the past and no longer use them in > our engagements. > > ## Otis > > Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > On Thursday, November 6, 2014 9:17:36 PM UTC-5, Alexandre Rafalovitch > wrote: > > ``` > ElasticSearch 1.4 is out and I can't see any mentions that Rivers are > deprecated. > > Has that (informal) decision been reversed? Or was the timeline > further out? What's the currently recommended approach? > > Regards, > Alex. > > ``` > > -- > 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/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm_medium=email&utm_source=footer). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С уважением _i.A. Jürgen Wagner_ Head of Competence Center "Intelligence" & Senior Cloud Consultant Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543 E-Mail: [juergen.wagner@devoteam.com](mailto:juergen.wagner@devoteam.com) [mailto:juergen.wagner@devoteam.com](mailto:juergen.wagner@devoteam.com), URL: [www.devoteam.de](http://www.devoteam.de) [http://www.devoteam.de/](http://www.devoteam.de/) * * * Managing Board: Jürgen Hatzipantelis (CEO) Address of Record: 64331 Weiterstadt, Germany; Commercial Register: Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071 -- 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/546913B8.7080409%40devoteam.com](https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [November 16, 2014, 9:49pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/4 "2014-11-16T21:49:40Z")
Can you explain how you compare rivers with SolrCloud data import handlers? Rivers were once designed as a singleton to fetch data very quick for prototyping and demo purpose, not more. With the official ES client families, and with logstash / message queue "push" architecture, they can often be replaced. Thanks, Jörg On Sun, Nov 16, 2014 at 10:14 PM, "Jürgen Wagner (DVT)" \< [juergen.wagner@devoteam.com](mailto:juergen.wagner@devoteam.com)\> wrote: > Hello, > we generally don't use rivers as it does not seem to be a good idea to > put too much of connector functionality into a search nodes themselves. The > scaling of connectors and feeding is entirely different from that of > processing and indexing or querying. That's why it is in my opinion clearly > advisable to keep such components in an architecture separate and not to > interweave them more than necessary. The notorious data import handlers of > SolrCloud demonstrate where this leads to. > > I don't know what stance the Elasticsearch folks take towards rivers, but > from an architectural point of view, the clear separation from > Elasticsearch seems like a good mid- to long-term goal to go for. > > My 5 EUR-cents worth of feedback... > > --Jürgen > > On 16.11.2014 21:24, Otis Gospodnetic wrote: > > We've seen issues with Rivers in the past and no longer use them in our > engagements. > > ## Otis > > Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > On Thursday, November 6, 2014 9:17:36 PM UTC-5, Alexandre Rafalovitch > wrote: > > > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > > deprecated. > > > > Has that (informal) decision been reversed? Or was the timeline > > further out? What's the currently recommended approach? > > > > Regards, > > Alex. > > -- > 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/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > > Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С > уважением > _i.A. Jürgen Wagner_ > Head of Competence Center "Intelligence" > & Senior Cloud Consultant > > ## Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543 E-Mail: [juergen.wagner@devoteam.com](mailto:juergen.wagner@devoteam.com), URL: [www.devoteam.de](http://www.devoteam.de) > > Managing Board: Jürgen Hatzipantelis (CEO) > Address of Record: 64331 Weiterstadt, Germany; Commercial Register: > Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071 > > -- > 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/546913B8.7080409%40devoteam.com](https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com) > [https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.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/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [November 16, 2014, 10:02pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/5 "2014-11-16T22:02:19Z")
Hi, On Sun, Nov 16, 2014 at 4:49 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > Can you explain how you compare rivers with SolrCloud data import handlers? They are similar in the sense that they both run inside their containers (Solr/SolrCloud or ES) and _pull_ data in. Data Import Handler (DIH) in Solr is similarly not the greatest way to index data in Solr even though it was (and still is) super popular. ## Otis Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > Rivers were once designed as a singleton to fetch data very quick for > prototyping and demo purpose, not more. With the official ES client > families, and with logstash / message queue "push" architecture, they can > often be replaced. > > Thanks, > > Jörg > > On Sun, Nov 16, 2014 at 10:14 PM, "Jürgen Wagner (DVT)" \< > [juergen.wagner@devoteam.com](mailto:juergen.wagner@devoteam.com)\> wrote: > > > Hello, > > we generally don't use rivers as it does not seem to be a good idea to > > put too much of connector functionality into a search nodes themselves. The > > scaling of connectors and feeding is entirely different from that of > > processing and indexing or querying. That's why it is in my opinion clearly > > advisable to keep such components in an architecture separate and not to > > interweave them more than necessary. The notorious data import handlers of > > SolrCloud demonstrate where this leads to. > > > > I don't know what stance the Elasticsearch folks take towards rivers, but > > from an architectural point of view, the clear separation from > > Elasticsearch seems like a good mid- to long-term goal to go for. > > > > My 5 EUR-cents worth of feedback... > > > > --Jürgen > > > > On 16.11.2014 21:24, Otis Gospodnetic wrote: > > > > We've seen issues with Rivers in the past and no longer use them in our > > engagements. > > > > ## Otis > > > > Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management > > Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/) > > > > On Thursday, November 6, 2014 9:17:36 PM UTC-5, Alexandre Rafalovitch > > wrote: > > > > > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > > > deprecated. > > > > > > Has that (informal) decision been reversed? Or was the timeline > > > further out? What's the currently recommended approach? > > > > > > Regards, > > > Alex. > > > > -- > > 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/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/a2abf858-c038-4a14-9e8f-ee3af5409fa0%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > > > Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С > > уважением > > _i.A. Jürgen Wagner_ > > Head of Competence Center "Intelligence" > > & Senior Cloud Consultant > > > > ## Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543 E-Mail: [juergen.wagner@devoteam.com](mailto:juergen.wagner@devoteam.com), URL: [www.devoteam.de](http://www.devoteam.de) > > > > Managing Board: Jürgen Hatzipantelis (CEO) > > Address of Record: 64331 Weiterstadt, Germany; Commercial Register: > > Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071 > > > > -- > > 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/546913B8.7080409%40devoteam.com](https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com) > > [https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/546913B8.7080409%40devoteam.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 a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/XW05vCHp\_pY/unsubscribe](https://groups.google.com/d/topic/elasticsearch/XW05vCHp_pY/unsubscribe). > To unsubscribe from this group and all its topics, 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/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEMTZ4HLXccrcQM-S0MP3o2VD0y8pq9Zm3WV9a%3DN2L%3DQw%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/CANNBgPJioLbePbu\_TxOzyz2sxmneY\_07TSvkJwdjp091fNV%2B7A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CANNBgPJioLbePbu_TxOzyz2sxmneY_07TSvkJwdjp091fNV%2B7A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Phil\_Swenson](https://avatars.discourse-cdn.com/v4/letter/p/f17d59/32.png) [@Phil\_Swenson](https://discuss.elastic.co/u/Phil_Swenson)\ **Post date:** [December 10, 2014, 6:44pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/6 "2014-12-10T18:44:20Z")
did you ever find an answer to this question? On Thursday, November 6, 2014 7:17:36 PM UTC-7, Alexandre Rafalovitch wrote: > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > deprecated. > > Has that (informal) decision been reversed? Or was the timeline > further out? What's the currently recommended approach? > > Regards, > Alex. -- 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/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [December 10, 2014, 7:34pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/7 "2014-12-10T19:34:10Z")
They are still planned to be deprecated, but there is no timeline for it as yet. On 10 December 2014 at 19:44, Phil Swenson [pswenson@itriagehealth.com](mailto:pswenson@itriagehealth.com) wrote: > did you ever find an answer to this question? > > On Thursday, November 6, 2014 7:17:36 PM UTC-7, Alexandre Rafalovitch > wrote: > > > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > > deprecated. > > > > Has that (informal) decision been reversed? Or was the timeline > > further out? What's the currently recommended approach? > > > > Regards, > > Alex. > > -- > 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/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/d7638967-0cbc-4ab7-b2ce-2646116423c8%40googlegroups.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/CAEYi1X9vjYZbb9oDm%2B6Z9neS1hKvL\_mjjAM-Rh4bzMKUTqmWQQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9vjYZbb9oDm%2B6Z9neS1hKvL_mjjAM-Rh4bzMKUTqmWQQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![elvarb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elvarb/32/44840_2.png) [@elvarb](https://discuss.elastic.co/u/elvarb)\ **Post date:** [December 10, 2014, 7:53pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/8 "2014-12-10T19:53:29Z")
I know that feeders will replace them, for example the JDBC plugin ships with a early version of a feeder but it only works in Linux at the moment. Are there any project out there that provide a feeder functionality similar to what rivers are now? Also, the bad thing about rivers is that the river is running inside a Elasticsearch JVM. Would that not be mitigated by having a seperate instance of Elasticsearch running the river process that would be a client to the cluster? On Friday, November 7, 2014 2:17:36 AM UTC, Alexandre Rafalovitch wrote: > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > deprecated. > > Has that (informal) decision been reversed? Or was the timeline > further out? What's the currently recommended approach? > > Regards, > Alex. -- 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/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 10, 2014, 10:47pm UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/9 "2014-12-10T22:47:47Z")
Can you elaborate what you mean by JDBC feeder plugin "only works in Linux"? I have running it on Mac OS X and Solaris. BTW you can configure ES to run rivers on specific (dedicated) nodes only. They can be data-less so they do not interfere with search/indexing. Jörg Am 10.12.2014 20:53 schrieb "Elvar Böðvarsson" [elvarb@gmail.com](mailto:elvarb@gmail.com): > I know that feeders will replace them, for example the JDBC plugin ships > with a early version of a feeder but it only works in Linux at the moment. > > Are there any project out there that provide a feeder functionality > similar to what rivers are now? > > Also, the bad thing about rivers is that the river is running inside a > Elasticsearch JVM. Would that not be mitigated by having a seperate > instance of Elasticsearch running the river process that would be a client > to the cluster? > > On Friday, November 7, 2014 2:17:36 AM UTC, Alexandre Rafalovitch wrote: > > > Elasticsearch 1.4 is out and I can't see any mentions that Rivers are > > deprecated. > > > > Has that (informal) decision been reversed? Or was the timeline > > further out? What's the currently recommended approach? > > > > Regards, > > Alex. > > -- > 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/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e853e0cb-7cfb-4f72-a256-08fa74b5e735%40googlegroups.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/CAKdsXoE-%2B2uZpSCFPUXe5efa5fOfG\_5YLhqwi20mLdf0EM313A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE-%2B2uZpSCFPUXe5efa5fOfG_5YLhqwi20mLdf0EM313A%40mail.gmail.com). 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:44am UTC](https://discuss.elastic.co/t/are-rivers-still-being-deprecated/20623/10 "2017-07-06T00:44:20Z")