@@ -117,7 +117,7 @@ You can configure an archive path with the parameter `path`
117
117
118
118
curl -XPOST 'localhost:9200/test/_export?path=/tmp/myarchive.zip'
119
119
120
- If ELasticsearch can not write an archive to the path, an error message will appear
120
+ If Elasticsearch can not write an archive to the path, an error message will appear
121
121
and no export will take place.
122
122
123
123
Renaming indexes and index types
@@ -213,7 +213,7 @@ You can import the file with::
213
213
curl -XPOST 'localhost:9200/test/test/_import'
214
214
215
215
Knapsack does not delete or overwrite data by default.
216
- But ou can use the parameter `createIndex ` with the value `false ` to allow indexing to indexes that exist.
216
+ But you can use the parameter `createIndex ` with the value `false ` to allow indexing to indexes that exist.
217
217
218
218
When importing, you can map your indexes or index/types to your favorite ones.
219
219
@@ -307,7 +307,7 @@ Knapsack is very simple and works without locks or snapshots. This means, if Ela
307
307
allowed to write to the part of your data in the export while it runs, you may lose data in the export.
308
308
So it is up to you to organize the safe export and import with this plugin.
309
309
310
- If you want a snapshot/restore feature, please use the standard napshot /restore in the upcoming
310
+ If you want a snapshot/restore feature, please use the standard snapshot /restore in the upcoming
311
311
Elasticsearch 1.0 release.
312
312
313
313
Credits
0 commit comments