github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-25 07:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

[Transform][Docs] Delete advise about group_by order (#82886)

Browse source 
Since 7.15 transform automatically optimizes the grouping part of the query. We therefore can delete group_by order advise in the transform at scale documentation so it gets simpler.
This commit is contained in:
Hendrik Muhs 2022-01-25 10:22:33 +01:00 • committed by GitHub
parent 2715db8103
commit f412ce486c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/reference/transform/transforms-at-scale.asciidoc
View file

@ -160,18 +160,12 @@ we do not recommend using a runtime field as the time field that synchronizes a
[discrete]
[[index-sorting-group-by-ordering]]
== 8. Use index sorting and `group_by` ordering (search, process)
If you use more than one `group_by` field in your {transform}, then the order of
the fields in conjunction with the use of <<index-modules-index-sorting>> may
improve runtime.
== 8. Use index sorting (search, process)
Index sorting enables you to store documents on disk in a specific order which
can improve query efficiency. The ideal sorting logic depends on your use case,
but the rule of thumb may be to sort the fields in descending order (high to low
cardinality) starting with the time-based fields. Then put the time-based
components first in the `group_by` if you have any, and then apply the same
order to your `group_by` fields as configured for index sorting. Index sorting
cardinality) starting with the time-based fields. Index sorting
can be defined only once at index creation. If you don't already have index
sorting on the index that you want to use as a source, consider reindexing it to
a new, sorted index.