anchor.diff:  <2> Each runtime field has its own field type, just like any other field.
   <3> The script defines the evaluation to calculate at search time.
   
  -The `runtime` section supports `boolean`, `date`, `double`, `geo_point`, `ip`,
  -`keyword`, and `long` data types. Runtime fields with a `type` of `date` can
  -accept the <<mapping-date-format,`format`>> parameter exactly as the `date`
  -field type.
  +The `runtime` section can be any of these data types:
  +
  +* `boolean`
  +* `date`
  +* `double`
  +* `geo_point`
  +* `ip`
  +* `keyword`
  +* `long`
  +
  +Runtime fields with a `type` of `date` can accept the
  +<<mapping-date-format,`format`>> parameter exactly as the `date` field type.
   
   [[runtime-updating-scripts]]
   .Updating runtime scripts
  
positive.code: is an indexed field. You have the flexibility to choose which fields to index
  and which ones to keep as runtime fields.
  
  [discrete]
  [[runtime-use-cases]]
  === Use cases
  
negative.code: for each scripted field that is required for the query.
  
  NOTE: You can define a runtime field in the mapping definition without a
  script. At search time, {es} looks in `_source` for a field with the same name
  and returns a value if one exists. If a field with the same name doesn’t
  exist, the response doesn't include any values for that runtime field.
  
  If <<dynamic-field-mapping,dynamic field mapping>> is enabled where the
  `dynamic` parameter is set to `runtime`, new fields are automatically added to
  