anchor.diff:  
   [discrete]
   [[transform-consistency-limitations]]
  -== {ctransform-cap} consistency does not account for deleted or updated documents
  +=== {ctransform-cap} consistency does not account for deleted or updated documents
   
   While the process for {transforms} allows the continual recalculation of the 
   {transform} as new data is being ingested, it does also have some limitations.
  
positive.code: 
  
  [discrete]
  [[transform-painless-limitation]]
  == Using scripts in {transforms}
  
  {transforms-cap} support scripting in every case when aggregations support them. 
  However, there are certain factors you might want to consider when using scripts 
  in {transforms}:
  
  * {transforms-cap} cannot deduce index mappings for output fields when the 
    fields are created by a script. In this case, you might want to create the 
    mappings of the destination index yourself prior to creating the transform.
  
  * Scripted fields may increase the runtime of the {transform}.
    
  * {transforms-cap} cannot optimize queries when you use scripts for all the 
    groupings defined in `group_by`, you will receive a warning message when you 
    use scripts this way.
    
  
  [discrete]
  [[transform-runtime-field-limitation]]
  === {transforms-cap} perform better on indexed fields
  
  {transforms-cap} sort data by a user-defined time field, which is frequently 
  accessed. If the time field is a {ref}/runtime.html[runtime field], the 
  performance impact of calculating field values at query time can significantly 
  slow the {transform}. Use an indexed field as a time field when using 
  {transforms}.
  
  
  [discrete]
  [[transforms-ccs-limitation]]
  === {transforms-cap} support {ccs} if the remote cluster is configured properly
  
  If you use <<modules-cross-cluster-search,{ccs}>>, the remote cluster must 
  support the search and aggregations you use in your {transforms}. 
  {transforms-cap} validate their configuration; if you use {ccs} and the validation fails, 
  make sure that the remote cluster supports the query and aggregations you use.
  
negative.code: 
  [discrete]
  [[transform-data-streams-destination]]
  === Data streams as destination indices are not supported
  
  {transforms-cap} update data in the destination index which requires writing 
  into the destination. <<data-streams>> are designed to be append-only, which 
  