From 0655d9e8ac1d8d359c81682bf2517b964f548754 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Wed, 30 Sep 2020 16:25:48 +0200 Subject: [PATCH] [DOCS] Adds limitation item about using scripts in transforms (#63021) (#63075) --- docs/reference/transform/limitations.asciidoc | 28 ++++++++++++++++--- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index fea844cc216..deb676b7b61 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -23,9 +23,9 @@ nodes have been upgraded to the newer version before using the {transforms} UI. == {transforms-cap} reassignment suspended during a rolling upgrade from 7.2 and 7.3 If your cluster contains mixed version nodes, for example during a rolling -upgrade from 7.2 or 7.3 to a newer version, {transforms} whose nodes are stopped will -not be reassigned until the upgrade is complete. After the upgrade is done, {transforms} -resume automatically; no action is required. +upgrade from 7.2 or 7.3 to a newer version, {transforms} whose nodes are stopped +will not be reassigned until the upgrade is complete. After the upgrade is done, +{transforms} resume automatically; no action is required. [discrete] [[transform-datatype-limitations]] @@ -204,6 +204,7 @@ If your data uses the <>, aggregations are nonetheless on millisecond resolution. This limitation also affects the aggregations in your {transforms}. + [discrete] [[transform-data-streams-destination]] == Data streams as destination indices are not supported @@ -227,4 +228,23 @@ rollover. If you use ILM to have time-based indices, please consider using the <> instead. The processor works without duplicated -documents if your {transform} contains a `group_by` based on `date_histogram`. \ No newline at end of file +documents if your {transform} contains a `group_by` based on `date_histogram`. + + +[discrete] +[[transform-painless-imitation]] +== Using scripts in {transforms} + +{transforms-cap} support scripting in every case when aggregations support them. +However, there are certain factors you might want to consider when using scripts +in {transforms}: + +* {transforms-cap} cannot deduce index mappings for output fields when the + fields are created by a script. In this case, you might want to create the + mappings of the destination index yourself prior to creating the transform. + +* Scripted fields may increase the runtime of the {transform}. + +* {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. \ No newline at end of file