Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread Prashant Agrawal
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. -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/ANN-Elasticsearch-Mapper-

Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread David Pilato
reindex is not a feature in elasticsearch nowadays. You can read 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? --

Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread Prashant Agrawal
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

Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread David Pilato
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 elastic.co @dadoonet <

Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread Prashant Agrawal
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 return

Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread David Pilato
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": "VGhpcy

Re: [ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2015-04-30 Thread Prashant Agrawal
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 co

[ANN] Elasticsearch Mapper Attachment plugin 2.3.0 released

2014-07-25 Thread Elasticsearch Team
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.. https://github.com/elasticsearch/elasticsearch-mapper-attachments/ Release Notes - elasticse