| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152 | --:api: update-transform:request: UpdateTransformRequest:response: UpdateTransformResponse--[role="xpack"][id="{upid}-{api}"]=== Update {transform} APIUpdates an existing {transform}.The API accepts a +{request}+ object as a request and returns a +{response}+.[id="{upid}-{api}-request"]==== Update {transform} requestA +{request}+ requires the following argument:["source","java",subs="attributes,callouts,macros"]--------------------------------------------------include-tagged::{doc-tests-file}[{api}-request]--------------------------------------------------<1> The update configuration with which to update the {transform}.<2> The ID of the configuration to update.<3> Whether or not to wait to run deferrable validations until `_start` is called.This option should be used with care as the created {transform} will runwith the privileges of the user creating it. Meaning, if they do not have privileges,such an error will not be visible until `_start` is called.[id="{upid}-{api}-config"]==== {transform-cap} update configurationThe `TransformConfigUpdate` object contains all the details about updated{transform} configuration and contains the following arguments:["source","java",subs="attributes,callouts,macros"]--------------------------------------------------include-tagged::{doc-tests-file}[{api}-config]--------------------------------------------------<1> The source indices and query from which to gather data.<2> The destination index and optional pipeline.<3> How often to check for updates to the source indices.<4> How to keep the {transform} in sync with incoming data.<5> Optional free text description of the {transform}.include::../execution.asciidoc[][id="{upid}-{api}-response"]==== ResponseThe returned +{response}+ contains the updated {transform} configuration or an error if the update failed or is invalid.
 |