# ES-to-ES river? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 21, 2014, 1:57pm UTC](https://discuss.elastic.co/t/es-to-es-river/20363 "2014-10-21T13:57:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![raidex](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@raidex](https://discuss.elastic.co/u/raidex)\ **Post date:** [October 21, 2014, 1:57pm UTC](https://discuss.elastic.co/t/es-to-es-river/20363/1 "2014-10-21T13:57:39Z")
Hi all, Is there a reason why a ES-to-ES river hasn't been implemented? I need to implement a fast copy mechanism to move data between indices (same cluster and across clusters) and seems to me like a river is the right mechanism. I am planning to write my own, but I want to check if it is a reasonable approach. -- Thanks. -- 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/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%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:** [October 21, 2014, 2:21pm UTC](https://discuss.elastic.co/t/es-to-es-river/20363/2 "2014-10-21T14:21:51Z")
Have a look at this thread: [https://github.com/elasticsearch/elasticsearch/issues/1077](https://github.com/elasticsearch/elasticsearch/issues/1077) It's related to that. -- David Pilato | Technical Advocate | [elasticsearch.com](http://elasticsearch.com) [david.pilato@elasticsearch.com](mailto:david.pilato@elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 21 octobre 2014 à 15:57:44, raidex ([ralgara@gmail.com](mailto:ralgara@gmail.com)) a écrit: Hi all, ## Is there a reason why a ES-to-ES river hasn't been implemented? I need to implement a fast copy mechanism to move data between indices (same cluster and across clusters) and seems to me like a river is the right mechanism. I am planning to write my own, but I want to check if it is a reasonable approach. -- Thanks. 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/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%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.54466bff.6b8b4567.184e%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.54466bff.6b8b4567.184e%40MacBook-Air-de-David.local). 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:** [October 21, 2014, 2:24pm UTC](https://discuss.elastic.co/t/es-to-es-river/20363/3 "2014-10-21T14:24:43Z")
You can also try the knapsack plugin, where you can archive index data, but also move index data around, between indices and across clusters. > **[GitHub - jprante/elasticsearch-knapsack: Knapsack plugin is an import/export...](https://github.com/jprante/elasticsearch-knapsack)** > > Knapsack plugin is an import/export tool for Elasticsearch - GitHub - jprante/elasticsearch-knapsack: Knapsack plugin is an import/export tool for Elasticsearch Jörg On Tue, Oct 21, 2014 at 3:57 PM, raidex [ralgara@gmail.com](mailto:ralgara@gmail.com) wrote: > Hi all, > > Is there a reason why a ES-to-ES river hasn't been implemented? I need to > implement a fast copy mechanism to move data between indices (same cluster > and across clusters) and seems to me like a river is the right mechanism. I > am planning to write my own, but I want to check if it is a reasonable > approach. -- Thanks. > > -- > 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/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%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/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT\_%2BNUa7NoqE\_iQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT_%2BNUa7NoqE_iQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [October 21, 2014, 3:57pm UTC](https://discuss.elastic.co/t/es-to-es-river/20363/4 "2014-10-21T15:57:45Z")
I personally recommend [GitHub - elastic/stream2es: Stream data into ES (Wikipedia, Twitter, stdin, or other ESes)](https://github.com/elasticsearch/stream2es) -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Tue, Oct 21, 2014 at 3:24 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > You can also try the knapsack plugin, where you can archive index data, > but also move index data around, between indices and across clusters. > > [GitHub - jprante/elasticsearch-knapsack: Knapsack plugin is an import/export tool for Elasticsearch](https://github.com/jprante/elasticsearch-knapsack) > > Jörg > > On Tue, Oct 21, 2014 at 3:57 PM, raidex [ralgara@gmail.com](mailto:ralgara@gmail.com) wrote: > > > Hi all, > > > > Is there a reason why a ES-to-ES river hasn't been implemented? I need to > > implement a fast copy mechanism to move data between indices (same cluster > > and across clusters) and seems to me like a river is the right mechanism. I > > am planning to write my own, but I want to check if it is a reasonable > > approach. -- Thanks. > > > > -- > > 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/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%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/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT\_%2BNUa7NoqE\_iQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT_%2BNUa7NoqE_iQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT\_%2BNUa7NoqE\_iQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT_%2BNUa7NoqE_iQ%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/CAHTr4Zs-8T67tF%3DdBkEnX44Z3jhpgKj0OJD9mPC4HS8bpW3DYQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4Zs-8T67tF%3DdBkEnX44Z3jhpgKj0OJD9mPC4HS8bpW3DYQ%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:54am UTC](https://discuss.elastic.co/t/es-to-es-river/20363/5 "2017-07-06T00:54:41Z")