anchor.diff:  [[ingest-attachment-extracted-chars]]
   ==== Limit the number of extracted chars
   
  -To prevent extracting too many chars and overload the node memory, the number of chars being used for extraction 
  -is limited by default to `100000`. You can change this value by setting `indexed_chars`. Use `-1` for no limit but 
  +To prevent extracting too many chars and overload the node memory, the number of chars being used for extraction
  +is limited by default to `100000`. You can change this value by setting `indexed_chars`. Use `-1` for no limit but
   ensure when setting this that your node will have enough HEAP to extract the content of very big documents.
   
   You can also define this limit per document by extracting from a given field the limit to set. If the document
  
positive.code: | `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
  |======
  
  [discrete]
  
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
  
  