You can also try the knapsack plugin, where you can archive index data, but also move index data around, between indices and across clusters.
https://github.com/jprante/elasticsearch-knapsack Jörg On Tue, Oct 21, 2014 at 3:57 PM, raidex <[email protected]> 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 [email protected]. > 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?utm_medium=email&utm_source=footer> > . > For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHLk6A3LUFR6YN%3DDJBdbDOy4QpAXjdzT_%2BNUa7NoqE_iQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
