Skip to content

[DOCS] Adds runtime filed related item to Transforms limitations #68895

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 2 commits into from
Feb 11, 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
15 changes: 13 additions & 2 deletions docs/reference/transform/limitations.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -248,7 +248,7 @@ documents if your {transform} contains a `group_by` based on `date_histogram`.


[discrete]
[[transform-painless-imitation]]
[[transform-painless-limitation]]
== Using scripts in {transforms}

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

* {transforms-cap} cannot optimize queries when you use scripts for all the
groupings defined in `group_by`, you will receive a warning message when you
use scripts this way.
use scripts this way.


[discrete]
[[transform-runtime-field-limitation]]
=== {transforms-cap} perform better on indexed fields

{transforms-cap} sort data by a user-defined time field, which is frequently
accessed. If the time field is a {ref}/runtime.html[runtime field], the
performance impact of calculating field values at query time can significantly
slow the {transform}. Use an indexed field as a time field when using
{transforms}.