Skip to content

Commit a9828a4

Browse files
authored
[DOCS] Clone index API doesn't apply index templates or settings (#74138) (#74152)
Changes: * Notes that Elasticsearch doesn't apply index templates to cloned indices. * Notes the clone API doesn't copy index settings.
1 parent 2e585a8 commit a9828a4

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

docs/reference/indices/clone-index.asciidoc

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,10 +56,11 @@ and then the previous write index can be cloned.
5656
Use the clone index API to clone an existing index into a new index, where each
5757
original primary shard is cloned into a new primary shard in the new index.
5858

59-
IMPORTANT: Cloning doesn't copy index metadata. This metadata includes aliases,
60-
{ilm-init} phase definitions, and {ccr-init} follower information. For example,
61-
if you clone a {ccr-init} follower index, the resulting clone won't be a
62-
follower index.
59+
IMPORTANT: {es} doesn't apply index templates to the resulting index. The API
60+
also doesn't copy index settings or metadata from the original index. Index
61+
metadata includes aliases, {ilm-init} phase definitions, and {ccr-init} follower
62+
information. For example, if you clone a {ccr-init} follower index, the
63+
resulting clone won't be a follower index.
6364

6465
[[cloning-works]]
6566
===== How cloning works

0 commit comments

Comments
 (0)