# Implementing Ingest Attachment Processor Plugin

**URL:** <https://discuss.elastic.co/t/implementing-ingest-attachment-processor-plugin/52300>\
**Category:** Elasticsearch\
**Created:** [June 9, 2016, 8:35am UTC](https://discuss.elastic.co/t/implementing-ingest-attachment-processor-plugin/52300 "2016-06-09T08:35:27Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![pnowy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pnowy/32/19868_2.png) [@pnowy](https://discuss.elastic.co/u/pnowy)\
**Post date:** [July 9, 2017, 11:15am UTC](https://discuss.elastic.co/t/implementing-ingest-attachment-processor-plugin/52300/37 "2017-07-09T11:15:03Z")

</div>

Hi @dadoonet . I've created separate question about different case - the support of some kind of dynamic fields for ingest processor.

> [@Ingest question - attachment processor plugin and dynamic fields](https://discuss.elastic.co/t/ingest-question-attachment-processor-plugin-and-dynamic-fields/92389):
>
> I have a question regarding the ingest attachment plugin (I would say it is question in general about ingest processor at all). Let's assume that I have some kind of index: PUT /myindex { "mappings": { "mytype": { "properties": { "#id" : {"type": "long"}, "myfield": { "type": "nested", "properties": { "name": { "type": "text" }, "revision": { "properties": { …

---

_[View the full topic](https://discuss.elastic.co/t/implementing-ingest-attachment-processor-plugin/52300)._