| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207 | [role="xpack"][testenv="basic"][[put-transform]]=== Create {transform} API[subs="attributes"]++++<titleabbrev>Create {transform}</titleabbrev>++++Instantiates a {transform}.beta[][[put-transform-request]]==== {api-request-title}`PUT _transform/<transform_id>`[[put-transform-prereqs]]==== {api-prereq-title}* If the {es} {security-features} are enabled, you must have `manage_transform` cluster privileges to use this API. The built-in `transform_admin` role has these privileges. You must also have `read` and `view_index_metadata` privileges on the source index and `read`, `create_index`, and `index` privileges on the destination index. For more information, see <<security-privileges>> and <<built-in-roles>>.[[put-transform-desc]]==== {api-description-title}This API defines a {transform}, which copies data from source indices,transforms it, and persists it into an entity-centric destination index. Theentities are defined by the set of `group_by` fields in the `pivot` object. Youcan also think of the destination index as a two-dimensional tabular datastructure (known as a {dataframe}). The ID for each document in the{dataframe} is generated from a hash of the entity, so there is a unique rowper entity. For more information, see <<transforms>>.When the {transform} is created, a series of validations occur toensure its success. For example, there is a check for the existence of thesource indices and a check that the destination index is not part of the sourceindex pattern. You can use the `defer_validation` parameter to skip thesechecks.Deferred validations are always run when the {transform} is started,with the exception of privilege checks. When {es} {security-features} areenabled, the {transform} remembers which roles the user that createdit had at the time of creation and uses those same roles. If those roles do nothave the required privileges on the source and destination indices, the{transform} fails when it attempts unauthorized operations.IMPORTANT:  You must use {kib} or this API to create a {transform}.            Do not put a {transform} directly into any            `.transform-internal*` indices using the Elasticsearch index API.            If {es} {security-features} are enabled, do not give users any            privileges on `.transform-internal*` indices. If you used transforms            prior 7.5, also do not give users any privileges on            `.data-frame-internal*` indices.[[put-transform-path-parms]]==== {api-path-parms-title}`<transform_id>`::(Required, string)include::{docdir}/rest-api/common-parms.asciidoc[tag=transform-id][[put-transform-query-parms]]==== {api-query-parms-title}`defer_validation`::  (Optional, boolean) When `true`, deferrable validations are not run. This  behavior may be desired if the source index does not exist until after the  {transform} is created.[[put-transform-request-body]]==== {api-request-body-title}`description`::  (Optional, string) Free text description of the {transform}.`dest`::(Required, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=dest]  `dest`.`index`:::(Required, string)include::{docdir}/rest-api/common-parms.asciidoc[tag=dest-index]`dest`.`pipeline`:::(Optional, string)include::{docdir}/rest-api/common-parms.asciidoc[tag=dest-pipeline]`frequency`::(Optional, <<time-units, time units>>)include::{docdir}/rest-api/common-parms.asciidoc[tag=frequency]`pivot`::(Required, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=pivot]`pivot`.`aggregations` or `aggs`:::(Required, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=pivot-aggs]`pivot`.`group_by`:::(Required, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=pivot-group-by]`pivot`.`max_page_search_size`:::(Optional, integer)include::{docdir}/rest-api/common-parms.asciidoc[tag=pivot-max-page-search-size]`source`::(Required, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=source-transforms]`source`.`index`:::(Required, string or array)include::{docdir}/rest-api/common-parms.asciidoc[tag=source-index-transforms]`source`.`query`:::(Optional, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=source-query-transforms]  `sync`::(Optional, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=sync]  `sync`.`time`:::(Required, object)include::{docdir}/rest-api/common-parms.asciidoc[tag=sync-time]`sync`.`time`.`delay`::::(Optional, <<time-units, time units>>)include::{docdir}/rest-api/common-parms.asciidoc[tag=sync-time-delay]    `sync`.`time`.`field`::::(Required, string)include::{docdir}/rest-api/common-parms.asciidoc[tag=sync-time-field]+--TIP: In general, it’s a good idea to use a field that contains the<<accessing-ingest-metadata,ingest timestamp>>. If you use a different field,you might need to set the `delay` such that it accounts for data transmissiondelays.--[[put-transform-example]]==== {api-examples-title}[source,console]--------------------------------------------------PUT _transform/ecommerce_transform{  "source": {    "index": "kibana_sample_data_ecommerce",    "query": {      "term": {        "geoip.continent_name": {          "value": "Asia"        }      }    }  },  "pivot": {    "group_by": {      "customer_id": {        "terms": {          "field": "customer_id"        }      }    },    "aggregations": {      "max_price": {        "max": {          "field": "taxful_total_price"        }      }    }  },  "description": "Maximum priced ecommerce data by customer_id in Asia",  "dest": {    "index": "kibana_sample_data_ecommerce_transform",    "pipeline": "add_timestamp_pipeline"  },  "frequency": "5m",  "sync": {    "time": {      "field": "order_date",      "delay": "60s"    }  }}--------------------------------------------------// TEST[setup:kibana_sample_data_ecommerce,add_timestamp_pipeline]When the {transform} is created, you receive the following results:[source,console-result]----{  "acknowledged" : true}----
 |