# \[ANN\] Elasticsearch Mapper Attachment plugin 2.3.0 released
**URL:** https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910
**Category:** Elasticsearch
**Created:** [July 25, 2014, 10:47pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910 "2014-07-25T22:47:31Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 25, 2014, 10:47pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/1 "2014-07-25T22:47:31Z")
Heya,
We are pleased to announce the release of the Elasticsearch Mapper Attachment plugin, version 2.3.0.
The mapper attachments plugin adds the attachment type to Elasticsearch using Apache Tika..
> **[elastic/elasticsearch-mapper-attachments](https://github.com/elastic/elasticsearch-mapper-attachments)**
>
> elasticsearch-mapper-attachments - Mapper Attachments Type plugin for Elasticsearch
Release Notes - elasticsearch-mapper-attachments - Version 2.3.0
Update:
- [78] - Log tika exceptions ([https://github.com/elasticsearch/elasticsearch-mapper-attachments/pull/78](https://github.com/elasticsearch/elasticsearch-mapper-attachments/pull/78))
- [76] - Update to Lucene 4.9.0 ([https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/76](https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/76))
- [73] - deprecate `content` by `_content` ([https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/73](https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/73))
- [69] - Remove deprecated `language` forced field ([https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/69](https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/69))
- [67] - Update to elasticsearch 1.3.0 ([https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/67](https://github.com/elasticsearch/elasticsearch-mapper-attachments/issues/67))
Issues, Pull requests, Feature requests are warmly welcome on elasticsearch-mapper-attachments project repository: [https://github.com/elasticsearch/elasticsearch-mapper-attachments/](https://github.com/elasticsearch/elasticsearch-mapper-attachments/)
For questions or comments around this plugin, feel free to use elasticsearch mailing list: [https://groups.google.com/forum/#!forum/elasticsearch](https://groups.google.com/forum/#!forum/elasticsearch)
Enjoy,
-The Elasticsearch team
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/53d2de83.4624b40a.1097.0157SMTPIN\_ADDED\_MISSING%40gmr-mx.google.com](https://groups.google.com/d/msgid/elasticsearch/53d2de83.4624b40a.1097.0157SMTPIN_ADDED_MISSING%40gmr-mx.google.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Prashant\_Pal](https://discuss.elastic.co/u/Prashant_Pal)
#### Post date: [April 30, 2015, 10:12am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/2 "2015-04-30T10:12:17Z")
Hi dadoonet,
Currently we were using Elasticsearch 1.3.0 and supported Mapper Plugin for the same. Now we are moving Elasticsearch 1.5.2 so we need to have the updated mapper att plugin as well.
As in the latest one content is deprecated by \_content, so in our application we need to change the content to \_content while retrieving the document. So here my question is like is there way to re index the Elasticsearch data so that older records can also be returned using \_content instead of content (any way like changing some conf or doing re indexing or something else)
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 30, 2015, 10:24am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/3 "2015-04-30T10:24:37Z")
Just a note before answering, the change is about the document you send to elasticsearch. Instead of sending:
{
"file": {
"content": "VGhpcyBpcyBhbiBlbGFzdGljc2VhcmNoIG1hcHBlciBhdHRhY2htZW50IHRlc3Qu",
"\_name": "myfilename.txt"
}
}
You now send
{
"file": {
"\_content": "VGhpcyBpcyBhbiBlbGFzdGljc2VhcmNoIG1hcHBlciBhdHRhY2htZW50IHRlc3Qu",
"\_name": "myfilename.txt"
}
}
It’s not related to generated field names at index time.
That said, I think you should better handle that on client side unless you have a few docs to reindex.
That answers to your question, yes you have to reindex if you want to use the new format instead of the old one.
Though you can try to work around with script fields: [Request body search | Elasticsearch Guide [8.11] | Elastic](http://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-script-fields.html) [http://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-script-fields.html](http://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-script-fields.html)
Does it help?
--
David Pilato - Developer | Evangelist
> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co/)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.
@dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> Le 30 avr. 2015 à 12:12, Prashant Agrawal [prashant.agrawal@paladion.net](mailto:prashant.agrawal@paladion.net) a écrit :
>
> Hi dadoonet,
>
> Currently we were using Elasticsearch 1.3.0 and supported Mapper Plugin for
> the same. Now we are moving Elasticsearch 1.5.2 so we need to have the
> updated mapper att plugin as well.
>
> As in the latest one content is deprecated by \_content, so in our
> application we need to change the content to \_content while retrieving the
> document. So here my question is like is there way to re index the
> Elasticsearch data so that older records can also be returned using \_content
> instead of content (any way like changing some conf or doing re indexing or
> something else)
>
> --
> View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-Attachment-plugin-2-3-0-released-tp4060656p4074364.html](http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-Attachment-plugin-2-3-0-released-tp4060656p4074364.html)
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
>
> --
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1430388737162-4074364.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1430388737162-4074364.post%40n3.nabble.com).
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2E348C66-DC16-421C-B905-5F6BA3C74332%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2E348C66-DC16-421C-B905-5F6BA3C74332%40pilato.fr).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Prashant\_Pal](https://discuss.elastic.co/u/Prashant_Pal)
#### Post date: [April 30, 2015, 10:33am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/4 "2015-04-30T10:33:46Z")
Hi ,
Thanks for a quick response,
Yes , I am making a change content to \_content as an index request.
Here my worry is like our application is already deployed , so with new changes being done I will not be able to fetch the older records using the same application as older records will be returned with "content" (in source) and new records will be returned with "\_content".
So what could be the best way to handle this using elasticsearch.
~Prashant
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 30, 2015, 10:43am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/5 "2015-04-30T10:43:47Z")
So why not doing that in your application?
If you look into \_source.file.content and \_source.file.\_content, older docs will have BASE64 content in content and null in \_content and the opposite for newer docs.
Do I miss anything?
--
David Pilato - Developer | Evangelist
> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co/)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.
@dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> Le 30 avr. 2015 à 12:33, Prashant Agrawal [prashant.agrawal@paladion.net](mailto:prashant.agrawal@paladion.net) a écrit :
>
> Hi ,
> Thanks for a quick response,
>
> Yes , I am making a change content to \_content as an index request.
>
> Here my worry is like our application is already deployed , so with new
> changes being done I will not be able to fetch the older records using the
> same application as older records will be returned with "content" (in
> source) and new records will be returned with "\_content".
>
> So what could be the best way to handle this using elasticsearch.
>
> ~Prashant
>
> --
> View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-Attachment-plugin-2-3-0-released-tp4060656p4074367.html](http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-Attachment-plugin-2-3-0-released-tp4060656p4074367.html)
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
>
> --
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1430390026413-4074367.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1430390026413-4074367.post%40n3.nabble.com).
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9FA37BF2-A60A-42CF-92BD-01DC5FDA90D0%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/9FA37BF2-A60A-42CF-92BD-01DC5FDA90D0%40pilato.fr).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Prashant\_Pal](https://discuss.elastic.co/u/Prashant_Pal)
#### Post date: [April 30, 2015, 10:47am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/6 "2015-04-30T10:47:40Z")
Yes, Though that can be handled as an exception in our application.
But I was just looking for as if any thing is there in ES which can re index old document in parallel, and make the content present in older records under "\_content" only instead of "content".
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 30, 2015, 10:52am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/7 "2015-04-30T10:52:01Z")
reindex is not a feature in elasticsearch nowadays.
You can read [Reindexing Your Data | Elasticsearch: The Definitive Guide [master] | Elastic](http://www.elastic.co/guide/en/elasticsearch/guide/master/reindex.html) [http://www.elastic.co/guide/en/elasticsearch/guide/master/reindex.html](http://www.elastic.co/guide/en/elasticsearch/guide/master/reindex.html)
How many documents you have to reindex?
IIRC your case you could have a lot, right?
--
David Pilato - Developer | Evangelist
> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co/)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.
@dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> Le 30 avr. 2015 à 12:47, Prashant Agrawal [prashant.agrawal@paladion.net](mailto:prashant.agrawal@paladion.net) a écrit :
>
> Yes, Though that can be handled as an exception in our application.
>
> But I was just looking for as if any thing is there in ES which can re index
> old document in parallel, and make the content present in older records
> under "\_content" only instead of "content".
>
> --
> View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-Attachment-plugin-2-3-0-released-tp4060656p4074370.html](http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-Attachment-plugin-2-3-0-released-tp4060656p4074370.html)
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
>
> --
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1430390860202-4074370.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1430390860202-4074370.post%40n3.nabble.com).
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1500B0C7-4C08-4A28-BD31-BB8C40476600%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/1500B0C7-4C08-4A28-BD31-BB8C40476600%40pilato.fr).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Prashant\_Pal](https://discuss.elastic.co/u/Prashant_Pal)
#### Post date: [April 30, 2015, 11:02am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/8 "2015-04-30T11:02:36Z")
Ok, So handling at the client side would be the best solution for the same.
Yes, we do have records in TB's which may lead to billions of documents to be reindexed or handled differently.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:16am UTC](https://discuss.elastic.co/t/ann-elasticsearch-mapper-attachment-plugin-2-3-0-released/18910/9 "2017-07-06T00:16:47Z")