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-aggregation-page-limitations]]
  == Handling dynamic adjustment of aggregation page size
  
  During the development of {transforms}, control was favoured over performance. 
  In the design considerations, it is preferred for the {transform} to take longer 
  
negative.code: 
  
  [discrete]
  [[transform-ui-limitations]]
  == Limitations in {kib}
  
  [discrete]
  [[transform-space-limitations]]
  === {transforms-cap} are visible in all {kib} spaces
  
  {kibana-ref}/xpack-spaces.html[Spaces] enable you to organize your source and 
  destination indices and other saved objects in {kib} and to see only the objects 
  that belong to your space. However, this limited scope does not apply to 
  {transforms}; they are visible in all spaces.
  
  [discrete]
  [[transform-rolling-upgrade-ui-limitation]]
  === {transforms-cap} UI will not work during a rolling upgrade from 7.2
  
  If your cluster contains mixed version nodes, for example during a rolling 
  upgrade from 7.2 to a newer version, and {transforms} have been created in 7.2, 
  the {transforms} UI (earler {dataframe} UI) will not work. Please wait until all 
  nodes have been upgraded to the newer version before using the {transforms} UI.
  
  [discrete]
  [[transform-kibana-limitations]]
  === Up to 1,000 {transforms} are listed in {kib}
  
  The {transforms} management page in {kib} lists up to 1000 {transforms}.