In order to search binary files, I have two options that I see: Use the Elastic Mapping Plugin and have Elasticsearch handle all the things. Pre-parse and extract content from binary file. Send parsed content to Elasticsearch. Number 2 seems like a perfectly viable solution. What's the adva…

Mapper attachment plugin vs. pre-parsing and extracting content from binary files

dadoonet (David Pilato) February 3, 2017, 4:02pm 10

The main advantage is that you don't write/maintain the code.

If you are using ingest-attachment instead of mapper-attachments (removed in 6.0), another advantage is that you can dedicate some nodes as ingest nodes and then share the load on multiple nodes.

Topic		Replies	Views
Mapper-attachment plugin not parsing binary files Elasticsearch	5	668	July 6, 2017
Mapper-attachment vs Ingest-attachment with OCR Elasticsearch	3	1781	December 13, 2016
Getting the extracted content from the attachment mapper plugin Elasticsearch	6	395	July 6, 2017
Customized attachment mapper plugin for streaming, smile and extra metadata support Elasticsearch	1	466	July 6, 2017
Re: Indexing binary files - how to store the extracted text only Elasticsearch	9	542	July 6, 2017

Mapper attachment plugin vs. pre-parsing and extracting content from binary files

Related topics