anchor.diff:  | `indexed_chars_field`  | no        | `null`           | Field name from which you can overwrite the number of chars being used for extraction. See `indexed_chars`.
   | `properties`           | no        | all properties   | Array of properties to select to be stored. Can be `content`, `title`, `name`, `author`, `keywords`, `date`, `content_type`, `content_length`, `language`
   | `ignore_missing`       | no        | `false`          | If `true` and `field` does not exist, the processor quietly exits without modifying the document
  +| `resource_name`        | no        |                  | Field containing the name of the resource to decode. If specified, the processor passes this resource name to the underlying Tika library to enable https://tika.apache.org/1.24.1/detection.html#Resource_Name_Based_Detection[Resource Name Based Detection].
   |======
   
   [discrete]
  
positive.code:     'data': f.read()
    }
    requests.put(
      'http://localhost:9200/my-index-000001/_doc/my_id?pipeline=cbor-attachment', 
      data=cbor2.dumps(doc), 
      headers=headers
    )
  ----
  
negative.code: NOTE: Extracting contents from binary data is a resource intensive operation and
        consumes a lot of resources. It is highly recommended to run pipelines
        using this processor in a dedicated ingest node.
  
  [[ingest-attachment-cbor]]
  ==== Use the attachment processor with CBOR
  
  