anchor.diff:      }
     ]
   }
  ---------------------------------------------------
  +----
   
   NOTE: Extracting contents from binary data is a resource intensive operation and
         consumes a lot of resources. It is highly recommended to run pipelines
  
positive.code:   "data": "e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0="
  }
  GET my-index-000001/_doc/my_id
  --------------------------------------------------
  
  Returns this:
  
  [source,console-result]
  --------------------------------------------------
  {
    "found": true,
    "_index": "my-index-000001",
  
negative.code: | `ignore_missing`       | no        | `false`          | If `true` and `field` does not exist, the processor quietly exits without modifying the document
  |======
  
  [discrete]
  [[ingest-attachment-json-ex]]
  ==== Example
  
  If attaching files to JSON documents, you must first encode the file as a base64
  string. On Unix-like systems, you can do this using a `base64` command:
  
  [source,shell]
  ----
  base64 -in myfile.rtf
  ----
  
  The command returns the base64-encoded string for the file. The following base64
  string is for an `.rtf` file containing the text `Lorem ipsum dolor sit amet`:
  `e1xydGYxXGFuc2kNCkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBhbWV0DQpccGFyIH0=`.
  
  Use an attachment processor to decode the string and extract the file's
  properties:
  
  [source,console]
  ----
  PUT _ingest/pipeline/attachment
  {
    "description" : "Extract attachment information",
  