3 ms·
This is a neat tool for moving data around, but for serious stuff I'm not sure why you would use this over the official snapshot / restore API (http://www.elast
by andrewvc 12y ago
This is a neat tool for moving data around, but for serious stuff I'm not sure why you would use this over the official snapshot / restore API (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html http://www.elasticsearch.org/guide/en/elasticsearch/referenc...).
While the API there is a bit more cumbersome, it's one less dependency, and should be more efficient.
For the specific use case of backups, the official API is even less cumbersome, esp. if you're using the cloud plugin and the S3 export option.
- schmichael 12y agosnapshot/restore doesn't allow applying new mappings. Also I use our similar custom tool* for dev purposes where you might want to kill the copy after a while and just work with a subset of the data... or explicitly apply a filter to copy a subset of data. * https://github.com/lytics/escp https://github.com/lytics/escp
- Xylakant 12y agoon top of that you can apply transformations to the data if you use scroll and bulk, but not with dump/restore. On the flip side, dump/restore allows incremental transfer which is a bit of work to do if you're implementing your own copy script.