Skip to content

[7.x] [DOCS] Clone index API doesn't apply index templates or settings (#74138) #74152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 15, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/reference/indices/clone-index.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -56,10 +56,11 @@ and then the previous write index can be cloned.
Use the clone index API to clone an existing index into a new index, where each
original primary shard is cloned into a new primary shard in the new index.

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

[[cloning-works]]
===== How cloning works
Expand Down