@@ -56,11 +56,18 @@ or <<search-aggregations-pipeline-bucket-script-aggregation,`bucket_scripts`>>,
56
56
<<dynamic-mapping,dynamic mappings>> will be used. In some instances the
57
57
deduced mappings may be incompatible with the actual data. For example, numeric
58
58
overflows might occur or dynamically mapped fields might contain both numbers
59
- and strings. Please check {es} logs if you think this may have occurred. As a
60
- workaround, you may define custom mappings prior to starting the
61
- {transform}. For example,
62
- <<indices-create-index,create a custom destination index>> or
63
- <<indices-templates,define an index template>>.
59
+ and strings. Please check {es} logs if you think this may have occurred.
60
+
61
+ You can view the deduced mappings by using the
62
+ https://www.elastic.co/guide/en/elasticsearch/reference/current/preview-transform.html[Preview transform API].
63
+ See the `generated_dest_index` object in the API response.
64
+
65
+ If it's required, you may define custom mappings prior to starting the
66
+ {transform} by creating a custom destination index using the
67
+ https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html[Create index API].
68
+ As deduced mappings cannot be overwritten by an index template, use the Create
69
+ index API to define custom mappings. The index templates only apply to fields
70
+ derived from scripts that use dynamic mappings.
64
71
65
72
[discrete]
66
73
[[transform-batch-limitations]]
0 commit comments