| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212 | [role="xpack"][testenv="basic"][[update-transform]]=== Update {transform} API[subs="attributes"]++++<titleabbrev>Update {transform}</titleabbrev>++++Updates certain properties of a {transform}.beta[][[update-transform-request]]==== {api-request-title}`POST _transform/<transform_id>/_update`[[update-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>>.[[update-transform-desc]]==== {api-description-title}This API updates an existing {transform}. The list of properties that you canupdate is a subset of the list that you can define when you create a {transform}.When the {transform} is updated, a series of validations occur to ensure itssuccess. You can use the `defer_validation` parameter to skip these checks.All updated properties except description do not take effect until after the{transform} starts the next checkpoint. This is so there is consistency with thepivoted data in each checkpoint.[IMPORTANT]====* When {es} {security-features} are enabled, your {transform} remembers whichroles the user who updated it had at the time of update and runs with thoseprivileges.* You must use {kib} or this API to update a {transform}. Do not update a{transform} directly via `.transform-internal*` indices using the {es} 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 notgive users any privileges on `.data-frame-internal*` indices.====[[update-transform-path-parms]]==== {api-path-parms-title}`<transform_id>`::(Required, string)include::{docdir}/rest-api/common-parms.asciidoc[tag=transform-id][[update-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 updated.[[update-transform-request-body]]==== {api-request-body-title}`description`::  (Optional, string) Free text description of the {transform}.`dest`::(Optional, 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]`source`::(Optional, 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.--[[update-transform-example]]==== {api-examples-title}[source,console]--------------------------------------------------POST _transform/simple-kibana-ecomm-pivot/_update{  "source": {    "index": "kibana_sample_data_ecommerce",    "query": {      "term": {        "geoip.continent_name": {          "value": "Asia"        }      }    }  },  "description": "Maximum priced ecommerce data by customer_id in Asia",  "dest": {    "index": "kibana_sample_data_ecommerce_transform_v2",    "pipeline": "add_timestamp_pipeline"  },  "frequency": "15m",  "sync": {    "time": {      "field": "order_date",      "delay": "120s"    }  }}--------------------------------------------------// TEST[setup:simple_kibana_continuous_pivot]When the {transform} is updated, you receive the updated configuration:[source,console-result]----{  "id": "simple-kibana-ecomm-pivot",  "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_v2",    "pipeline": "add_timestamp_pipeline"  },  "frequency": "15m",  "sync": {    "time": {      "field": "order_date",      "delay": "120s"    }  },  "version": "7.5.0",  "create_time": 1518808660505}----// TESTRESPONSE[s/"version": "7.5.0"/"version": $body.version/]// TESTRESPONSE[s/"create_time": 1518808660505/"create_time": $body.create_time/]
 |