Skip to content

Note the storage tradeoff of copy_to and how to avoid it #7790

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.

Sign up for GitHub

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

Open
ash9146 wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Note the storage tradeoff of copy_to and how to avoid it #7790

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3aa0bb1
Note the storage tradeoff of copy_to and how to avoid it
ash9146 Aug 5, 2026
e006b96
Update deploy-manage/production-guidance/optimize-performance/search-…
ash9146 Aug 5, 2026
662fbc7
Merge branch 'main' into copy-to-storage-tradeoff
georgewallace Aug 5, 2026
33dd8d4
Revise note on indexing fields in search performance
georgewallace Aug 5, 2026
93ee21a
Merge branch 'main' into copy-to-storage-tradeoff
georgewallace Aug 5, 2026
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
4 changes: 4 additions & 0 deletions deploy-manage/production-guidance/optimize-performance/search-speed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,10 @@ PUT movies
}
```

:::{note}
In the previous example, `name` and `plot` are still indexed individually alongside `name_and_plot`, which adds storage overhead for each source field. If you don't need to search those fields individually, you can avoid this by setting `"index": false` on them. See [Size your shards](/deploy-manage/production-guidance/optimize-performance/size-shards.md) for more on using `copy_to` to reduce per-field mapping overhead.
:::

## Pre-index data [_pre_index_data]

You should leverage patterns in your queries to optimize the way data is indexed. For instance, if all your documents have a `price` field and most queries run [`range`](elasticsearch://reference/aggregations/search-aggregations-bucket-range-aggregation.md) aggregations on a fixed list of ranges, you could make this aggregation faster by pre-indexing the ranges into the index and using a [`terms`](elasticsearch://reference/aggregations/search-aggregations-bucket-terms-aggregation.md) aggregations.
Expand Down