raidex  
                (raidex)
               
                 
              
                  
                    October 21, 2014,  1:57pm
                   
                   
              1 
               
             
            
              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 . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com . 
For more options, visit https://groups.google.com/d/optout .
             
            
               
               
               
            
            
           
          
            
              
                dadoonet  
                (David Pilato)
               
              
                  
                    October 21, 2014,  2:21pm
                   
                   
              2 
               
             
            
              Have a look at this thread: https://github.com/elasticsearch/elasticsearch/issues/1077 
It's related to that.
-- 
David Pilato | Technical Advocate | elasticsearch.com  
david.pilato@elasticsearch.com  
@dadoonet  | @elasticsearchfr  | @scrutmydocs 
Le 21 octobre 2014 à 15:57:44, raidex (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 . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/564b7d29-677f-4bb2-9ab0-5ca206894621%40googlegroups.com . 
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 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 . 
For more options, visit https://groups.google.com/d/optout .
             
            
               
               
               
            
            
           
          
            
              
                jprante  
                (Jörg Prante)
               
                 
              
                  
                    October 21, 2014,  2:24pm
                   
                   
              3 
               
             
            
              You can also try the knapsack plugin, where you can archive index data, but 
also move index data around, between indices and across clusters.
Jörg
On Tue, Oct 21, 2014 at 3:57 PM, raidex 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 . 
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 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 . 
For more options, visit https://groups.google.com/d/optout .
             
            
               
               
               
            
            
           
          
            
            
              I personally recommend GitHub - elastic/stream2es: Stream data into ES (Wikipedia, Twitter, stdin, or other ESes) 
--
Itamar Syn-Hershko 
http://code972.com  | @synhershko  https://twitter.com/synhershko  
Freelance Developer & Consultant 
Author of RavenDB in Action http://manning.com/synhershko/ 
On Tue, Oct 21, 2014 at 3:24 PM, joergprante@gmail.com  < 
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 
Jörg
On Tue, Oct 21, 2014 at 3:57 PM, raidex 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 . 
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 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?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 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 . 
For more options, visit https://groups.google.com/d/optout .