github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-06-28 09:28:55 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Adds new transform limitation item and a note to the tutorial (#79479)

Browse source
This commit is contained in:
István Zoltán Szabó 2021-10-26 10:14:58 +02:00 • committed by GitHub
parent f64b18413a
commit f7eae04e1c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 22 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/reference/transform/ecommerce-tutorial.asciidoc
View file

@ -241,6 +241,11 @@ destination index. In {kib}, if you copied the API request to your
clipboard, paste it into the console, then refer to the `generated_dest_index`
object in the API response.
NOTE: {transforms-cap} might have more configuration options provided by the
APIs than the options available in {kib}. For example, you can set an ingest
pipeline for `dest` by calling the <<put-transform>>. For all the {transform}
configuration options, refer to the <<transform-apis,documentation>>.
.API example
[%collapsible]
====

10
docs/reference/transform/limitations.asciidoc
View file

@ -276,4 +276,12 @@ that belong to your space. However, this limited scope does not apply to
[[transform-kibana-limitations]]
=== Up to 1,000 {transforms} are listed in {kib}
The {transforms} management page in {kib} lists up to 1000 {transforms}.
The {transforms} management page in {kib} lists up to 1000 {transforms}.
[discrete]
[[transform-ui-support]]
=== {kib} might not support every {transform} configuration option
There might be configuration options available via the {transform} APIs that are
not supported in {kib}. For an exhaustive list of configuration options, refer
to the <<transform-apis,documentation>>.

10
docs/reference/transform/overview.asciidoc
View file

@ -8,8 +8,14 @@
You can choose either of the following methods to transform your data:
<<pivot-transform-overview,pivot>> or <<latest-transform-overview,latest>>.
IMPORTANT: All {transforms} leave your source index intact. They create a new
index that is dedicated to the transformed data.
[IMPORTANT]
====
* All {transforms} leave your source index intact. They create a new
index that is dedicated to the transformed data.
* {transforms-cap} might have more configuration options provided by the APIs
than the options available in {kib}. For all the {transform} configuration
options, refer to the <<transform-apis,API documentation>>.
====
{transforms-cap} are persistent tasks; they are stored in cluster state which
makes them resilient for node failures. Refer to <<transform-checkpoints>> and