mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
[DOCS] Adds new transform limitation item and a note to the tutorial (#79479)
This commit is contained in:
parent
f64b18413a
commit
f7eae04e1c
3 changed files with 22 additions and 3 deletions
|
@ -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`
|
clipboard, paste it into the console, then refer to the `generated_dest_index`
|
||||||
object in the API response.
|
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
|
.API example
|
||||||
[%collapsible]
|
[%collapsible]
|
||||||
====
|
====
|
||||||
|
|
|
@ -276,4 +276,12 @@ that belong to your space. However, this limited scope does not apply to
|
||||||
[[transform-kibana-limitations]]
|
[[transform-kibana-limitations]]
|
||||||
=== Up to 1,000 {transforms} are listed in {kib}
|
=== 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>>.
|
|
@ -8,8 +8,14 @@
|
||||||
You can choose either of the following methods to transform your data:
|
You can choose either of the following methods to transform your data:
|
||||||
<<pivot-transform-overview,pivot>> or <<latest-transform-overview,latest>>.
|
<<pivot-transform-overview,pivot>> or <<latest-transform-overview,latest>>.
|
||||||
|
|
||||||
IMPORTANT: All {transforms} leave your source index intact. They create a new
|
[IMPORTANT]
|
||||||
index that is dedicated to the transformed data.
|
====
|
||||||
|
* 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
|
{transforms-cap} are persistent tasks; they are stored in cluster state which
|
||||||
makes them resilient for node failures. Refer to <<transform-checkpoints>> and
|
makes them resilient for node failures. Refer to <<transform-checkpoints>> and
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue