Skip to content

Commit e44e437

Browse files
authored
[DOCS] Adds runtime filed related item to Transforms limitations (#68895) (#68912)
1 parent c1aa708 commit e44e437

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

docs/reference/transform/limitations.asciidoc

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -248,7 +248,7 @@ documents if your {transform} contains a `group_by` based on `date_histogram`.
248248

249249

250250
[discrete]
251-
[[transform-painless-imitation]]
251+
[[transform-painless-limitation]]
252252
== Using scripts in {transforms}
253253

254254
{transforms-cap} support scripting in every case when aggregations support them.
@@ -263,4 +263,15 @@ in {transforms}:
263263

264264
* {transforms-cap} cannot optimize queries when you use scripts for all the
265265
groupings defined in `group_by`, you will receive a warning message when you
266-
use scripts this way.
266+
use scripts this way.
267+
268+
269+
[discrete]
270+
[[transform-runtime-field-limitation]]
271+
=== {transforms-cap} perform better on indexed fields
272+
273+
{transforms-cap} sort data by a user-defined time field, which is frequently
274+
accessed. If the time field is a {ref}/runtime.html[runtime field], the
275+
performance impact of calculating field values at query time can significantly
276+
slow the {transform}. Use an indexed field as a time field when using
277+
{transforms}.

0 commit comments

Comments
 (0)